Hi,
I'm afraid I probably made a mistake when laying down the release dates for
GeoServer and GeoTools under the time boxed release model here:
http://geoserver.org/display/GEOS/GeoTools+and+GeoServer+release+schedule

The model was foreseeing 4 months open development, 2 months hardening, and
then the release, with RC starting to get out at the end of the 6-th month and
gettingout every two weeks until we were done.

However the above timetable had only 3 months of open development, and we
missed the first beta in december because of lack of volounteers.

Hum... if we follow the current timetable, next month will be RC, and
if we do a couple
of those, we'll have 2.3.0 final right at the end of the 6 months cycle.
Not bad, ad the cycle repeats itself two times in a year this way.

Or... we can do another beta next month, release the first RC in two months, and
probably have the final in three months

Tangential topic, branching off, the time boxed relase model had a branch off
by the second beta, but I agree with other people that having a trunk
always open
is probably better

Opinions?

Cheers
Andrea

-- 
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to