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.
Sounds good to me.
On Tue, May 15, 2012 at 4:29 PM, Gabriel Roldan <groldan@anonymised.com> wrote:
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@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Wed, May 16, 2012 at 12:29 AM, Gabriel Roldan <groldan@anonymised.com> wrote:
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.
+1
Cheers
Andrea
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
+1 from me. This will as a side-effect work around Maven's brokenness with snapshots from some repos (gwc is normally the one that bites me).
On 16/05/12 06:29, Gabriel Roldan wrote:
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
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
+1
Regards,
Alessio.
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
On Wed, May 16, 2012 at 8:01 AM, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:
+1 from me. This will as a side-effect work around Maven’s brokenness
with snapshots from some repos (gwc is normally the one that bites me).
On 16/05/12 06:29, Gabriel Roldan wrote:
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
–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
ok then, thanks for the prompt feedback.
I'll apply the change to the root poms on 2.1.x and 2.2.x right away.
Cheers,
Gabriel
On Wed, May 16, 2012 at 11:14 AM, Alessio Fabiani
<alessio.fabiani@anonymised.com> wrote:
+1
Regards,
Alessio.
-------------------------------------------------------
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
http://www.geo-solutions.it
http://geo-solutions.blogspot.com
http://www.linkedin.com/in/alessiofabiani
https://twitter.com/alfa7961
http://twitter.com/geosolutions_it
-------------------------------------------------------
On Wed, May 16, 2012 at 8:01 AM, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com> wrote:
+1 from me. This will as a side-effect work around Maven's brokenness
with snapshots from some repos (gwc is normally the one that bites me).
On 16/05/12 06:29, Gabriel Roldan wrote:
> 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
>
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
------------------------------------------------------------------------------
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
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.