Jody Garnett ha scritto: > 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, the thing is, 1.7.x has been basically in freeze for well over a month. David has already opened his branch and I did not do that only by accident, I have commits for 1.7.x that are more than one week overdue, and that's only because I had to work for FOSS4G, otherwise I would have had to wait longer. So I can say the current way of doing thing does not work. The new way we'll know in 6 months (guesstimate) when we'll deal with 2.0.0, there are no RC between here and there. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- 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
