[Geoserver-devel] Releases

Hey all, so first I want to apologize for being opaque on the process of when releases have been cut recently, not giving people a chance to get their changes in before putting it out.

We've now got Mike aboard to help us with the mechanical process of cutting releases, so I'm hoping that we can approach a more regular process of releases. We also have more people putting small bug fixes in, and really using the stable branch, so I'm thinking it could make sense to aim for monthly releases. Something like cut the release on the first friday of the month, announce on lists on monday and on blogs, ect. on tuesday.

This would put 1.6.3 on next friday. Would that work for everyone? Watermarking is already in, and Mike's going to work on documenting it. And perhaps we'll also get raster symbolization? So any more bug fixes or smaller features that you want in aim for the middle of next week.

The other release to be done is 1.7.0-beta1. WCS 1.1.1 and WFS 1.1 Xlink are both completed, as part of OWS-5, and we'd like to cut a release. I don't think we need to aim for explicit dates for trunk releases, until we get to stability, it makes more sense to me to do releases after major new features get on, so people can try them out. But yeah, just wanted to give a heads up that we'll cut 1.7.0-beta1 this week, but there can easily be more betas for major features, but do let everyone know soon if you're hoping to get some major changes on. The two major ones on my radar are some core config improvements and perhaps multidimensional WCS.

best regards,

Chris

Chris Holmes ha scritto:

Hey all, so first I want to apologize for being opaque on the process of when releases have been cut recently, not giving people a chance to get their changes in before putting it out.

We've now got Mike aboard to help us with the mechanical process of cutting releases, so I'm hoping that we can approach a more regular process of releases. We also have more people putting small bug fixes in, and really using the stable branch, so I'm thinking it could make sense to aim for monthly releases. Something like cut the release on the first friday of the month, announce on lists on monday and on blogs, ect. on tuesday.

This would put 1.6.3 on next friday. Would that work for everyone? Watermarking is already in, and Mike's going to work on documenting it. And perhaps we'll also get raster symbolization? So any more bug fixes or smaller features that you want in aim for the middle of next week.

Raster symbolization wise, I believe we're still stuck on the proposal,
that required lots of changes in the implementation to be accepted.
The set of classes is not small, so I'd either feel comfortable of merging it right now, to allow some time for testing, or wait for the
next release (thought I know there are people waiting...)

About bug fixes, we still have 38 unresolved issues in this one,
some of which were opened against 1.6.0 and have been moved forward
at each release (like GEOS-1580, which has been opened in December I think):
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10311&fixfor=14102
There are also some like GEOS-1373 that have been marked as critical
since 2 releases, and I don't really know why, or some like
GEOS-1768, which are regressions from the point of view of MapBuilder
users (thought in fact our behaviour is more consistent today than
it was in 1.5.x times).

An issue that seems important but that hasn't been scheduled for
any release is http://jira.codehaus.org/browse/GEOS-1807, thought
to fix it, it seems we'll need to backport from trunk the
improved GridCoverageRenderer (Alessio, Simone, is it something we
can do this week?).

In any case, we'd need to shorten the list quite a bit imho to make
a release and decide what to move to 1.6.4. Oh, we also have some issues
assigned to Ivan Willig, that has ended his internship, so they should
be reassigned.
Cheers
Andrea

Sorry, it just got pointed out to me the ambiguity of 'next friday'. Release will be Friday, April 4th, the first friday of the month.

Chris

Chris Holmes wrote:

Hey all, so first I want to apologize for being opaque on the process of when releases have been cut recently, not giving people a chance to get their changes in before putting it out.

We've now got Mike aboard to help us with the mechanical process of cutting releases, so I'm hoping that we can approach a more regular process of releases. We also have more people putting small bug fixes in, and really using the stable branch, so I'm thinking it could make sense to aim for monthly releases. Something like cut the release on the first friday of the month, announce on lists on monday and on blogs, ect. on tuesday.

This would put 1.6.3 on next friday. Would that work for everyone? Watermarking is already in, and Mike's going to work on documenting it. And perhaps we'll also get raster symbolization? So any more bug fixes or smaller features that you want in aim for the middle of next week.

The other release to be done is 1.7.0-beta1. WCS 1.1.1 and WFS 1.1 Xlink are both completed, as part of OWS-5, and we'd like to cut a release. I don't think we need to aim for explicit dates for trunk releases, until we get to stability, it makes more sense to me to do releases after major new features get on, so people can try them out. But yeah, just wanted to give a heads up that we'll cut 1.7.0-beta1 this week, but there can easily be more betas for major features, but do let everyone know soon if you're hoping to get some major changes on. The two major ones on my radar are some core config improvements and perhaps multidimensional WCS.

best regards,

Chris

!DSPAM:4005,47e9234810271637810514!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

!DSPAM:4005,47e9234810271637810514!

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

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:4005,47e9234810271637810514!