On 29/12/2009, at 4:49 PM, Jason van Zyl wrote: > There are 511 issues left if you exclude the documentation fix version. Call > it 30 minutes an issue on average and that's ~250 man hours. If we could get > 10 people in January to do 25 hours (which is a lot for most people) and try > and make it easier for users to validate fixes we might be able to pull it > off in January. > > http://jira.codehaus.org/secure/IssueNavigator.jspa?fixfor=13143&fixfor=14504&fixfor=16088&fixfor=16089&fixfor=14118&fixfor=16090&fixfor=16087&fixfor=15103&fixfor=16094&fixfor=16093&fixfor=15565&fixfor=15472&fixfor=15554&fixfor=13145&fixfor=13142&fixfor=13141&fixfor=15996&fixfor=14593&pid=10500&status=1&status=3&status=4&reset=true&show=View+%26gt%3B%26gt%3B >
I tend to work through the "unscheduled" issues every now and then, since it makes it easier to find the new stuff that comes in. I can focus on starting there. I've liked having a "Backlog" version for things that are reviewed and may be fixed in the future, without committing to a version/series. Could we create that to start pushing valid issues into so they don't get reviewed twice? The goal is then to get rid of the *.x versions. Alternatively we could just unschedule them all and push them to the 3.x bucket. The criteria being: - regressions in 2.1.x/2.2.x -> 2.2.2 - regressions in 3.0-alpha-X -> 3.0-alpha-7 - very select number new features and improvements -> 3.1 - everything else that is still valid -> Backlog Right? Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
