At the core developers meeting yesterday, personnel were assigned to the tasks of getting 2.0.17 and 2.2.5 released. (The meeting notes will be published shortly.) These are only bug-fix releases, I think, so there shouldn't be any controversy here.
As the one assigned to handle 2.2.5, I will be asking for feedback from the community on any bugs that I may overlook.
The longer term task of merging the 2.0/2.2/2.3 branches is still being discussed. I think everyone would agree that these branches do need to be merged; the issue is "how". When a plan is decided upon by the team, it will be posted for public feedback.
The core dev team will also be posting periodic status reports.
So I think we're on the same page here.