Bertrand Delacretaz wrote: > > Le Mercredi, 24 sep 2003, � 17:32 Europe/Zurich, Vadim Gritsenko a > �crit : > > ...Personally, I prefer code freeze policy. Moving tags on individual > > files make things messy, and global freeze gives everybody an > > opportunity to stop for a second, take a look at what we are going to > > release, and may be fix a bug or too... > > I'm with Vadim - technically I like Berin's proposal with CVS tags a > lot, but from the team's perspective it might be better to actually > freeze development for a while. Yep, I absolutely agree. If we follow your proposal, Berin, than the release tends to be a "one man show" and noone else than the release manager will care about the release (ok, noone is too pesimistic, I know). Look at the release problems over at Avalon where noone than the release manager really cares about the release which makes releasing something really painfull.
> > And if "code freeze" = "frantically test everything before release", > all the better. > Yes, this is my hope as well. A release must be a team effort. Carsten
