Resurrecting this old thread a bit... On Mon, Dec 26, 2011 at 3:36 PM, Justin Deoliveira <[email protected]> wrote: > Yeah I like the idea of versioning the rest API since at some point we will > have to undoubetly make non backward compatible changes. So yeah I guess we > could call this api version 1 and then if we want to make breaking changes > on the trunk push it to 2. It would be nice to have at least one release of > a deprecation cycle though. Yeah, by versioning the REST API I mean if GeoServer release N supports rest api version M, GeoServer N+1 should support at least rest api M _and_ M+1. Is that what you mean?
Back to the original topic, if I wanted to upgrade the Jettison version on trunk, would we also need a patch that preserves the old collections encoding behavior, or would you be up to "fixing" it right now? Cheers, Gabriel -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
