Just some clarification. The proposal is additions to the catalog interface
itself, which are additive, with no updates to client code. Even though the
github branch does contain changes for client code the idea is to only make
the api changes.
So the desire to get this onto 2.2.x stems from the fact that
these changes without anything out of the catalog changing should be low
risk and not represent instability. But certainly we realize
that changes on any scale represent some amount of risk and that we
previously agreed that geoserver 2.2.x should be striving for a stable
release. Which is why it was originally stated that we are perfectly happy
and willing to wait for 2.2.x to branch before pushing on this. Which if we
are formally agreeing to only bug fixes from here on in should happen soon
imo, but that is another discussion.
-Justin
On Tue, Apr 24, 2012 at 1:38 PM, Gabriel Roldan <grol...@opengeo.org> wrote:
> Hi Simone,
>
> thanks for the quick reply.
> I would like to gather some more feedback on the proposal itself,
> whether it looks good or there's something that's not clear enough or
> directly looks odd.
> I am expecting some resistance to incorporate all changes to 2.2.x,
> that was my initial though as well. But first step would be to
> evaluate the proposal and have 2.2.x split onto its own branch, so
> that we have room on trunk?
> That said the concern is totally valid, and reason why the proposal is
> all about API extensions, purely additive, so _no_ client code _needs_
> to be touched, nor even any internal Catalog data structure or data
> access method.
> Perhaps a middle compromise could be agreed: adding the new methods,
> not changing anything else on 2.2.x, and work on a 2.3.x trunk, so
> that we can backport any Catalog client code on a case by case basis
> once consolidated on trunk?
>
> But even for that it'd be good to have some feedback on the proposal
> itself, letting the 2.2.x discussion off for a while?
>
> Cheers,
> Gabriel
>
> On Tue, Apr 24, 2012 at 2:11 PM, Simone Giannecchini
> <simone.giannecch...@geo-solutions.it> wrote:
> > Ciao Gabriel,
> > I do see the need for the changes you describe but, not to be picky,
> > the security changes were supposed to be the last ones bringing
> > instability for 2.2.x. Changes to the internal look a bit scary with
> > these regards.
> >
> > Baseline is, I am personally against allowing these changes right away
> > for 2.2.x I am ok if we leave them settle a bit and then we backport
> > them later on.
> >
> > Regards,
> > Simone Giannecchini
> > -------------------------------------------------------
> > Ing. Simone Giannecchini
> > GeoSolutions S.A.S.
> > Founder
> >
> > Via Poggio alle Viti 1187
> > 55054 Massarosa (LU)
> > Italy
> >
> > phone: +39 0584 962313
> > fax: +39 0584 962313
> > mob: +39 333 8128928
> >
> > http://www.geo-solutions.it
> > http://geo-solutions.blogspot.com/
> > http://www.youtube.com/user/GeoSolutionsIT
> > http://www.linkedin.com/in/simonegiannecchini
> > http://twitter.com/simogeo
> >
> > -------------------------------------------------------
> >
> >
> > On Tue, Apr 24, 2012 at 6:11 PM, Gabriel Roldan <grol...@opengeo.org>
> wrote:
> >> Hi all,
> >>
> >> I've put together a GSIP to enhance the GeoServer's catalog vertical
> scalability
> >> <
> http://geoserver.org/display/GEOS/GSIP+69+-+Catalog+scalability+enhancements
> >
> >>
> >> At OpenGeo we're hoping to get this proposal implemented on 2.2.x,
> >> since the Catalog API changes are purely additive and no Catalog
> >> client code really needs to be changed to maintain the current
> >> functionality.
> >> Yet it enables to _progressively_ upgrade hungry client code to use
> >> the new access methods in a streaming fashion.
> >> That said, we're also willing to push back to 2.3 if that seems like
> >> too much for the stable 2.2.x branch, although based on your feedback
> >> we'll try to make any amendments that could possibly allow the API
> >> extensions to land on 2.2.x to avoid having to maintain a separate
> >> branch for the OpenGeo Suite.
> >>
> >> So, any feedback will be much appreciated.
> >>
> >> Best regards,
> >> 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
>
>
>
> --
> 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
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
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
