Hi all,
As far as I know the last major development change coming down the pipe
that is planned for 2.2 is the security work. I am just working on a couple
more tutorials to better the user documentation story, but the work is
generally ready to be committed. I hope to have the work committed
by tomorrow (Tuesday western time) unless there are any objections.
After which I would like to propose the first alpha/beta release of the 2.2
series. Part of the motivation is having a release of 2.2 in place before
the foss4gna conference next week. Andrea and myself will be delivering a
talk titled "GeoServer, What's new in 2.2" in which we are going to survey
all new features that will be coming with 2.2. IT would be awesome to have
a release to supplement the talk with.
Any objections? I wouldn't be getting to the release until later this week.
Also, preferences to whether it be an alpha or a beta? I am thinking of
staying on the safe side and calling it alpha just because it will be so
close after the big security commit. But I could go either way. I know we
have released pretty unstable betas in the past so it might not be too
unreasonable. But no strong opinion.
Thoughts?
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
