Jody Garnett ha scritto: > >> noted. i was trying to make the point that there's a time lag between >> a release of a (really stable) version of GeoServer and a similar one >> for a product that includes that version. in my case the product in >> question does not have a once-a-month release. > > Understood; even if you can kick the tires for a couple of days with a > RnD version of your product it will give you good information to plan > with and help catch any regressions that only your software will notice. > >>> to join us in making the next 1.7.x release come on over and we will >>> buy beer. >> >> cool! moving from 1.5/1.6 to 1.7 sounds less risky for me than to 2.0 >> right now. spending time on testing 1.7 releases in my case is a >> better value proposition. let me know when the next round is about to >> start. > > I suspect that moving to 1.7 is the major risk for your app. New feature > model, new config subsystem etc. 2.0 by comparison is more focused on an > amazing user interface :-)
Err... the new feature model had little or not impact on GeoServer, we basically had no defect reports over it. Most of the new config subsystem issues were sorted out in the first releases of the series. 2.0 is still showing issues in the config subsystem. The risk going there is significantly higher than going 1.7.6 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
