So the OpenGeo team has been talking things over, and it looks like we're going to back away from trying to get 2.0 out real soon, instead focus our energy on documentation and demos and what not for foss4g. And after foss4g we won't have guaranteed resources to put in to it, and in light of Rob A's recent comments on wanting clarity of release schedule let's go ahead and say that the goal for 2.0.0 will be six months after 1.7.0. I'd ideally like a complete feature freeze and branching a couple months before that, so we get the release super solid. Thoughts from others? This potentially leaves time to try to get things like Rest API and the published resource stuff in for 2.0, if anyone has funding or developer time for it. Thoughts? Does this time frame sound good to people?
Also, OpenGeo will try to kick out 1.6.5 sometime next week, as there have been a number of bugs fixed there. If anyone wants to help out in the release process let us know. I think our policy now requires a geotools release, so if anyone could even just help out there that would be great. This will be the last release of 1.6.x series, there is no more development work happening on that branch.
Chris
So we're going to try to get out 1.7.0-RC2 this week, the last candidate wasn't quite release quality. So our team isn't spending the whole week doing releases, I think we'll defer 1.6.5 release till next week, unless anyone wants to step up and put it out this week.
Chris
Chris Holmes wrote:
So the OpenGeo team has been talking things over, and it looks like we're going to back away from trying to get 2.0 out real soon, instead focus our energy on documentation and demos and what not for foss4g. And after foss4g we won't have guaranteed resources to put in to it, and in light of Rob A's recent comments on wanting clarity of release schedule let's go ahead and say that the goal for 2.0.0 will be six months after 1.7.0. I'd ideally like a complete feature freeze and branching a couple months before that, so we get the release super solid. Thoughts from others? This potentially leaves time to try to get things like Rest API and the published resource stuff in for 2.0, if anyone has funding or developer time for it. Thoughts? Does this time frame sound good to people?
Also, OpenGeo will try to kick out 1.6.5 sometime next week, as there have been a number of bugs fixed there. If anyone wants to help out in the release process let us know. I think our policy now requires a geotools release, so if anyone could even just help out there that would be great. This will be the last release of 1.6.x series, there is no more development work happening on that branch.
Chris
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel