If someone finds a bug and wants to fix it and do a release of 2.1.x
they should be free to do so. Once 2.2 is released and has all the
parts working I doubt anyone will though.
Grzegorz Kossakowski wrote:
Thanks for offer Carsten, I will help with testing (based only on samples,
though).
When we at 2.1.x, I have been wondering about freezing this branch. In a fact,
it's already almost
dead but lots of people are still using 2.1.x. Therefore I would like to hear
your opinions on
calling bug-squash effort. I mean: I would prepare an announcement at our site
and announcement to
the user list calling our users to vote for issues they would love to have
fixed. The rules of the
game would be simple: everyone is free to present favourites on users list and
encourage others to
vote on their issues.
Then, if there is a decent number of volunteers, everyone could pick up an
issue from the top of the
most voted issues list and fix it? Of course issues having a patch already
could go in first.
After 2.1.11 I would like to close 2.1.x branch completely.
WDYT?
