Justin Deoliveira ha scritto: > 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?
I like that. Wondering how we do divide them thought. Maybe by paging, or by issue number slots? Like, someone all those between GEOS-1 and GEOS-1000, someone else GEOT-1000 -> 1500, and so on. We should list all the open ones assigned to older releases, sort, and assign an equal number of issues to each of those that do volounteer to make the triage Cheers Andrea -- Andrea Aime 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
