Arne Kepp ha scritto: > 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.
2.0.x is really just another black hole, in my experience issues that have not been assigned to a specific release tend to just stay there unloved for a long long time. Usually we move them to a specific release when it's clear they are serious or enough people are complaining about them. > 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. Sounds like a good idea. Actually users cannot move issues around, but they can vote for them. So we could ask people to vote for the issues for some time (maybe all august) and then we move out of the black hole those that have high vote count? 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
