This just comes down to a tradeoff between overhead for those making the release; and those trying to continue work as usual. I do not think it is a bad thing for work as usual to be interrupted during the release candidate cycle; as long as we are clear up front about the timing it is something all concerned parties can plan for.
Andrea would it be prudent to try out the policy change you propose first; and see if we like it? Before making a decision about how to direct the project? Jody Andrea Aime wrote: > Hi all, > here is the change proposal for RC handling procedures: > http://geoserver.org/display/GEOS/GSIP+26+-+Long+freeze+handling+procedures > > Oh, if you can think of a better title, feel free to change, I could > not come up with anything better. > > If you need to discuss this more please do, otherwise let's start voting. > > Cheers > Andrea > > ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
