Proposal: A series of time based releases for 2.2.x

[Nikolaj Hald Nielsen]

Although it has not been discussed in depth yet (as far as I know)
there has been some talk about how to proceed with releases after
2.2.0. Personally I think that feature wise, 2.2.0 has made a huge
leap form 2.1 and I think it would be very worth it to focus on
stabilization and polish for a while to come as there are very few
"must have" features still missing.

So to start a discussion, my proposal would be to not branch off
anything right now, and instead aim to do a series of monthly 2.2.x
releases. I propose that we have 2 weeks where string changes are
allowed, and then 2 weeks for translation. I also propose a partial
lift on the feature freeze, meaning that small new features or
improvements are allowed, but no massive changes, or anything that is
likely to cause regressions or need more than a few weeks to
stabilize.

I am sure we all have great ideas for what we want to add or change
for 2.3, but I think it while be worth it to make what we have no more
robust before setting off on another journey the size of what Amarok
2.2.0 has been.

- Nikolaj