I was actually going to propose a jira cleanup / issue triage at foss4g but, but i have heard through the grapevine that their is going to be a geotools sprint, which works ok for me as well.
But yeah, cleanup++. For 1.7.x issues I would say any that are applicable to 2.x, we move forward into the 2.0.x void. For ones that are not applicable to 2.x like UI bug reports, I say we just close as won't fix. That or just keep them in the 1.7.x void. Once we agree shall we divide and conquer? 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 > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ 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
