Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
Where are we at with this? Even if all of Justin's enhancements haven't made it aboard yet it seems like it could be a good idea to get something out for people to start to kick the tires of? As far as I know it's ok for a beta2 to have more features than a beta1. It's only at RC status where we truly need to lock it down. And it'd be good to have a clear plan of what's going to be in each beta so we don't constantly get people wanting to add just one more feature. So I'm thinking a beta1 as soon as possible, and a beta2 when Justin's features are in, at least if there's someone who could do a release in the next week or two. Right now we're telling users to go get nightlies - having a beta I think would make many more comfortable with installing and implicitly helping bug test things. Sounds like OpenGeo, CSIRO and GeoSolutions all have major functionality in this release, so perhaps we can split up the load? On Sun, Jan 29, 2012 at 8:56 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: +1. In app-schema land we have huge memory and performance improvements (joining support), WMS, and GML 3.2. Many bugs fixed. On 26/01/12 15:19, Andrea Aime wrote: Hi, I'm wondering if it's time to start packing up trunk and start releasing betas with an outlook of releasing a stable version of GeoServer 2.2.0 in 2/3 months. The current GeoServer trunk is packing a good amount of functionality that is not available on the stable series (wfs 2.0, time/elevation, rendering transformations and so on) and from personal experience seems to behaving rather well, with a quality that already matches if not exceeds what we'd expect out of a beta. Jody has been waiting to release a GeoTools 8.0 for a while already and I see new GeoServer GSIPs lining up that could shake the current configuration/catalog subsystem from their foundations, potentially delaying the ability to pack up a stable release by a few months. So I'm wondering, is it time to call it done and start harderning it towards a stable release? 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 --- -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Try before you buy = See our experts in action! 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-dev2 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
Hey Chris, For the security work i am hoping to have the proposal out by early next week for people to start digesting. In terms of code things are winding down enough to commit to svn when the proposal is accepted. As for the workspace local styles/layer groups work, i would say things are code complete, really just need to write the proposals at this point. On Thu, Feb 16, 2012 at 2:19 PM, Chris Holmes chol...@opengeo.org wrote: Where are we at with this? Even if all of Justin's enhancements haven't made it aboard yet it seems like it could be a good idea to get something out for people to start to kick the tires of? As far as I know it's ok for a beta2 to have more features than a beta1. It's only at RC status where we truly need to lock it down. And it'd be good to have a clear plan of what's going to be in each beta so we don't constantly get people wanting to add just one more feature. I will have to disagree here. If the security stuff is going to make it into 2.2 I would prefer it be in the very first release since it is such a massive change. Generally I think as we move from beta to rc to official release things should get more stable, not less. And certainly there is going to be a period of instability once the security works lands. I would be ok with this for the workspace local style/layergroup stuff since they are much smaller changes. So I'm thinking a beta1 as soon as possible, and a beta2 when Justin's features are in, at least if there's someone who could do a release in the next week or two. Right now we're telling users to go get nightlies - having a beta I think would make many more comfortable with installing and implicitly helping bug test things. Sounds like OpenGeo, CSIRO and GeoSolutions all have major functionality in this release, so perhaps we can split up the load? On Sun, Jan 29, 2012 at 8:56 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: +1. In app-schema land we have huge memory and performance improvements (joining support), WMS, and GML 3.2. Many bugs fixed. On 26/01/12 15:19, Andrea Aime wrote: Hi, I'm wondering if it's time to start packing up trunk and start releasing betas with an outlook of releasing a stable version of GeoServer 2.2.0 in 2/3 months. The current GeoServer trunk is packing a good amount of functionality that is not available on the stable series (wfs 2.0, time/elevation, rendering transformations and so on) and from personal experience seems to behaving rather well, with a quality that already matches if not exceeds what we'd expect out of a beta. Jody has been waiting to release a GeoTools 8.0 for a while already and I see new GeoServer GSIPs lining up that could shake the current configuration/catalog subsystem from their foundations, potentially delaying the ability to pack up a stable release by a few months. So I'm wondering, is it time to call it done and start harderning it towards a stable release? 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 --- -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Try before you buy = See our experts in action! 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-dev2 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ 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. -- Virtualization Cloud Management Using
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
On Thu, Jan 26, 2012 at 4:19 AM, Andrea Aime andrea.a...@geo-solutions.it wrote: So I'm wondering, is it time to call it done and start harderning it towards a stable release? IMO, it is. -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
+1 with the caveat of getting the security work in. It is a pretty huge amount of work so i imagine it will lead to instability, but it would be pretty show stopping for us to have to wait until 2.3 to include it. THe work is nearing completion, Christian and I are currently wrapping up some loose ends. The new security documentation is proceeding along. I hope to be in a position to have a proposal ready within 2 weeks time. Chris also mentioned the virtual service / workspace local stuff. I would like to be able to say virtual services is complete for 2.2, with the ability to store styles and layer groups within a workspace. The styles work is pretty near completion... the only remaining issue is the moving of styles and its associated resources, which I think I know how to solve. Layer groups per workspace hasn't started yet... and is estimated at about a weeks worth of effort. So all in all I guess I am pushing for one more month to add new features before locking down. -Justin On Thu, Jan 26, 2012 at 7:07 AM, Gabriel Roldan grol...@opengeo.org wrote: On Thu, Jan 26, 2012 at 4:19 AM, Andrea Aime andrea.a...@geo-solutions.it wrote: So I'm wondering, is it time to call it done and start harderning it towards a stable release? IMO, it is. -- 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 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. -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
On Thu, Jan 26, 2012 at 3:52 PM, Justin Deoliveira jdeol...@opengeo.orgwrote: +1 with the caveat of getting the security work in. It is a pretty huge amount of work so i imagine it will lead to instability, but it would be pretty show stopping for us to have to wait until 2.3 to include it. THe work is nearing completion, Christian and I are currently wrapping up some loose ends. The new security documentation is proceeding along. I hope to be in a position to have a proposal ready within 2 weeks time. Wow, I haven't heard about that since quite a bit of time, thought the work on it stalled. That patch has been in the works for... how long? 6 months? Chris also mentioned the virtual service / workspace local stuff. I would like to be able to say virtual services is complete for 2.2, with the ability to store styles and layer groups within a workspace. The styles work is pretty near completion... the only remaining issue is the moving of styles and its associated resources, which I think I know how to solve. Layer groups per workspace hasn't started yet... and is estimated at about a weeks worth of effort. So all in all I guess I am pushing for one more month to add new features before locking down. One month is quite a bit of time, the other two GSIP in line are also from OpenGeo, can they wait that long? I was hoping to cut 2.2.0 towards stable sooner rather than later, but I agree the changes you're proposing are good to make GeoServer more palatable in larger deployments. I can see how different parties will want to add this and that and keep on going, but at some point we have to drop the blade and call it done. Waiting one more month is ok, what I'm worried about is a final rush where everybody tries to commit new eventually large changes and bring us significantly back in terms of stability Not pushing back, I'm ok with security and workspace changes coming in (assuming they are clean, well presented, and well reviewed, but I trust they are going be), just want to express my worry about large amount of changes in the eve of a beta. 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 --- -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
On Thu, Jan 26, 2012 at 12:07 PM, Andrea Aime andrea.a...@geo-solutions.itwrote: On Thu, Jan 26, 2012 at 3:52 PM, Justin Deoliveira jdeol...@opengeo.orgwrote: +1 with the caveat of getting the security work in. It is a pretty huge amount of work so i imagine it will lead to instability, but it would be pretty show stopping for us to have to wait until 2.3 to include it. THe work is nearing completion, Christian and I are currently wrapping up some loose ends. The new security documentation is proceeding along. I hope to be in a position to have a proposal ready within 2 weeks time. Wow, I haven't heard about that since quite a bit of time, thought the work on it stalled. That patch has been in the works for... how long? 6 months? Yeah we have actually been working pretty hard on it :) Things are coming along nicely. Chris also mentioned the virtual service / workspace local stuff. I would like to be able to say virtual services is complete for 2.2, with the ability to store styles and layer groups within a workspace. The styles work is pretty near completion... the only remaining issue is the moving of styles and its associated resources, which I think I know how to solve. Layer groups per workspace hasn't started yet... and is estimated at about a weeks worth of effort. So all in all I guess I am pushing for one more month to add new features before locking down. One month is quite a bit of time, the other two GSIP in line are also from OpenGeo, can they wait that long? I will let Gabriel comment but I believe so. I was hoping to cut 2.2.0 towards stable sooner rather than later, but I agree the changes you're proposing are good to make GeoServer more palatable in larger deployments. I can see how different parties will want to add this and that and keep on going, but at some point we have to drop the blade and call it done. Waiting one more month is ok, what I'm worried about is a final rush where everybody tries to commit new eventually large changes and bring us significantly back in terms of stability Yeah, one of the problems with not having a real road map of any kind. CErtainly if people think one month is excessive that is fine and we can move forward sooner, but we would much rather have these features in the core of 2.2 rather than in some forked version of it. So if people are ok with another month it would be much appreciated. As compensation we would be happy to pony up all the resources to push the release out :) Not pushing back, I'm ok with security and workspace changes coming in (assuming they are clean, well presented, and well reviewed, but I trust they are going be), just want to express my worry about large amount of changes in the eve of a beta. 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 --- -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
On Thu, Jan 26, 2012 at 5:13 PM, Justin Deoliveira jdeol...@opengeo.org wrote: On Thu, Jan 26, 2012 at 12:07 PM, Andrea Aime andrea.a...@geo-solutions.it wrote: On Thu, Jan 26, 2012 at 3:52 PM, Justin Deoliveira jdeol...@opengeo.org wrote: +1 with the caveat of getting the security work in. It is a pretty huge amount of work so i imagine it will lead to instability, but it would be pretty show stopping for us to have to wait until 2.3 to include it. THe work is nearing completion, Christian and I are currently wrapping up some loose ends. The new security documentation is proceeding along. I hope to be in a position to have a proposal ready within 2 weeks time. Wow, I haven't heard about that since quite a bit of time, thought the work on it stalled. That patch has been in the works for... how long? 6 months? Yeah we have actually been working pretty hard on it :) Things are coming along nicely. Chris also mentioned the virtual service / workspace local stuff. I would like to be able to say virtual services is complete for 2.2, with the ability to store styles and layer groups within a workspace. The styles work is pretty near completion... the only remaining issue is the moving of styles and its associated resources, which I think I know how to solve. Layer groups per workspace hasn't started yet... and is estimated at about a weeks worth of effort. So all in all I guess I am pushing for one more month to add new features before locking down. One month is quite a bit of time, the other two GSIP in line are also from OpenGeo, can they wait that long? I will let Gabriel comment but I believe so. GSIP 69 is _meant_ to be incorporated to trunk _after_ 2.2.x becomes a stable branch. That said, it has not been officially presented yet, though I'm planning on doing it like right now (or tomorrow). GSIP 70 is more of a brain dump from 69, and it may end up being discarded before presented, depending on further assessment of its value. So yeah, those two ones can and want to definitely wait for a 2.3.x trunk. If at all, we could consider a backport of the catalog enhancements to the stable 2.2.x branch after they were proved successful on the new trunk. That said, the one thing that I'd need to push onto 2.2.x is the GWC UI enhancements, which I'm planning to merge as soon as I change the metadata encoding from json to xml. Cheers, Gabriel I was hoping to cut 2.2.0 towards stable sooner rather than later, but I agree the changes you're proposing are good to make GeoServer more palatable in larger deployments. I can see how different parties will want to add this and that and keep on going, but at some point we have to drop the blade and call it done. Waiting one more month is ok, what I'm worried about is a final rush where everybody tries to commit new eventually large changes and bring us significantly back in terms of stability Yeah, one of the problems with not having a real road map of any kind. CErtainly if people think one month is excessive that is fine and we can move forward sooner, but we would much rather have these features in the core of 2.2 rather than in some forked version of it. So if people are ok with another month it would be much appreciated. As compensation we would be happy to pony up all the resources to push the release out :) Not pushing back, I'm ok with security and workspace changes coming in (assuming they are clean, well presented, and well reviewed, but I trust they are going be), just want to express my worry about large amount of changes in the eve of a beta. 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 --- -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Time to start the GeoServer 2.2.0 (long) release process?
Hi, I'm wondering if it's time to start packing up trunk and start releasing betas with an outlook of releasing a stable version of GeoServer 2.2.0 in 2/3 months. The current GeoServer trunk is packing a good amount of functionality that is not available on the stable series (wfs 2.0, time/elevation, rendering transformations and so on) and from personal experience seems to behaving rather well, with a quality that already matches if not exceeds what we'd expect out of a beta. Jody has been waiting to release a GeoTools 8.0 for a while already and I see new GeoServer GSIPs lining up that could shake the current configuration/catalog subsystem from their foundations, potentially delaying the ability to pack up a stable release by a few months. So I'm wondering, is it time to call it done and start harderning it towards a stable release? 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 --- -- 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
