Andrea Aime wrote: > Hi, > looking into jira it's evident we still have a ton of patches > scheduled for 1.6.x and 1.7.x. > > Now, the 1.6.x ones won't be surely addressed in any 1.6.x release, > since that series is long dead, and the 1.7.x ones are unlikely > to be fixed in any real 1.7.x either. > > What we should do? Just blindly mass move all of them to 2.0.x? > A better way would be to scan each of them, see if it's still > applicable, and if not close it. E.g., many UI related ones > might be unapplicable now that we have the Wicket UI, or might > need to be modified in the report a little > > Cheers > Andrea >
My 2 cents: Projects of this size will always have a ton of issues that will never be addressed, if we move them all to 2.0.x we'll only end up drowning issues that have been reported more recently. So I'd definitely not do a mass move. I think it's fine to leave most of them where they are, move up the ones we think are really important. Can also crowd source by sending a request to the -users list to make them bump any issues that they're still waiting to have resolved. -Arne -- Arne Kepp OpenGeo - http://opengeo.org Expert service straight from the developers ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
