[Zope-Coders] Zope 2.7 branch

[Chris McDonough]

You may want to look at the TODO.txt in the doc directory to get a sense
of what still needs to be done.

- C

On Tue, 2003-07-08 at 10:34, Brian Lloyd wrote:
> > Disabling checkins on a branch could probably be done with a suitably 
> > magic commit script. Or, since there will be a new tag of Zope-2_7-branch
> > at some point when we go to beta of 2.7, just cvs tag -d Zope-2_7-branch
> > and blow away the tag. The branch will still be there, but the chances of
> > someone managing to check stuff into it without a symbolic name 
> > is.. slight.
> > 
> > (If you want to be thorough, tag what's in the 2.7 branch now with some
> > name like Zope-2_7-too-early-branch, before nuking the 
> > Zope-2_7-branch tag).
> 
> I'm not sure this is all worth the effort. I'd like to see a 2.7 
> beta 1 out in the next week and a half - its way late already, so 
> after following up with people on 2 lingering things it will be 
> declared feature-complete and ready for beta.
> 
> A beneficial side-effect of the "slow-cook" method that the 2.7 
> cycle turned into is that most people are finding the alpha to 
> be a lot more stable than some have been in the past, so I 
> don't see any real reason to prolong the alpha period.
> 
> 
> Brian Lloyd        brian@zope.com
> V.P. Engineering   540.361.1716              
> Zope Corporation   http://www.zope.com 
> 
>