Yes, this is a lot of work - and we have to do it on all branches where we expect new releases, so it might be safer to not only change 2.1.x and 2.2.x but also the 2.0.x branch.
2.0.x? Do you really think there will be new releases in this branch?
Yes, I would also like to see a 2.0.5 release as a final step for the 2.0 branch. After this we will only release security patches or similar. But much effort has been put into the 2.0 branch in the more than half year from the 2.0.4 and the 2.1 release. I don't want to see it lost.
But before the release we should solve the one issue with a broken batik JAR in 2.0:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26392
Joerg
