Hey all,

with gwc / geoserver integration settling down I'd like to adopt the
policy of always pegging geoserver to a released version of gwc,
instead of having it as a SNAPSHOT policy.
In the event that anything needs to change on gwc, it'd be better if
we create a bug fix release or even a simple tag, but for instance
would like the geoserver stable branch to be always on a released gwc
version, although tag/snapshot would be good for trunk.

Opinions? if no objections I'd peg both 2.1.x and trunk to gwc
1.3-RC3, which was released last week.

Cheers,
Gabriel

-- 
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to