Justin Deoliveira ha scritto: > I think it is a great idea, crowdsourcing qa to the user community. > However I think one thing that is lacking (or maybe just not emphasized) > are the the benefits to the users. Any issues they find will become > critical priority (i would assume) and fixed before the release (if > within reason). This has the potential to offset a lot of risk of people > upgrading.
I thought about it, but was cautious about adding such point. Why are developers participating? To get a better GeoServer. Do we really need to give users more incentive? I agree regressions should be fixed swiftly, but what if during testing a new bug is spotted, or it's something affecting a minor extension? Do we "stop the presses" for any of those? 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
