Justin Deoliveira ha scritto: > <snip> > >> >> Yep, pretty much aware of the issues with long freezes. Then again, >> if you don't call "something" people will keep on merrily committing >> changes to the branches we're using for the release no? :) > > So its a darned if you do, darned if you don't situation... not very > nice for the guy doing the release trying to walk the line.
Indeed you're right, not an easy position, I've been there before keeping a freeze two weeks long with people complaining at me (I had my reasons, they had theirs, and we were both right, so it was indeed a lose/lose situation). The only escape route I know of if you plan to keep a freeze lasting longer than a week is to branch off... which as its own issues as you know, one more place to port changes to :( A solution? Maybe... talk. Ask people to start a freeze, if the freeze takes more than expected or people are getting uncomfortable with it, just branch off to insulate the freeze from other people work. Hopefully most of the time the freeze won't affect people enough to require a real branch, and when it does, well, you know that you have at least tried. 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
