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 ------------------------------------------------------------------------- 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/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
