It looks like 2.0 might be ripe for stabilization?
Actually - I think it is a little too early to stabilize 2.0.1: * 2.0.2 hasn't been released yet and we don't know if there are any significant bugs in 2.0.1. There were a number of significant 2.0 bugs fixed in 2.0.1. * 2.0.1 was the first 2.0.x release that was not package masked within gentoo * Package mask was only removed a few weeks ago. * 2.0.x ebuilds were significantly modified from 1.8.x ebuilds...still waiting to see if we got all of any bugs that might have been introduced by that. * The java jmx monitoring feature in 2.0.1 can probably use a little more work, waiting on fixes to another package we're dependent on. So, I plan to wait at least a few more weeks minimum before putting in a stable bug.
2.0.2 had a number of fixes over 2.0.1, including security....so 2.0.1 is removed from tree....if 2.0.2 has good response - we might look into stabilizing it. Will revisit in 1 month (Sept).
The release candidate for 2.0.3 shows a huge number of fixed bugs in 2.0.2, therefore 2.0.2 will NOT be a candidate for stable....we'll see if 2.0.3 can fit that role when it is finally released.
Just submitted the request to stabilize 2.0.4-r1
