[Zope-dev] Re: Extend specification of how to maintain the changelog

[yuppie]

Jens Vagelpohl wrote:
> On Jun 19, 2008, at 12:32 , yuppie wrote:
> 
>> There is always *one* well defined current maintenance branch. Version 
>> numbering *does* imply a time line if you ignore old maintenance 
>> branches. It's not hard at all to get this right.
> 
> I don't think that assumption holds true. Again, using the CMF as an 
> example, there were times when we had 3 release branches. I don't want 
> to start a discussion why that was or how to prevent that from 
> happening, I'm just saying it's not correct to say you always have just 
> one maintenance branch. And that's where all those fancy schemes fall down.

You did get me wrong :(

I tried to make a distinction between the current maintenance branch (= 
branch for maintaining the *current* release) and old maintenance 
branches (= branches for maintaining older release). If someone knows 
better terms, please let me know.

The *current* version of CMF is 2.1.1. If you release CMF 1.6.5 with 
some backports from the 2.1 branch, it will not become the *current* CMF 
release. As soon as CMF 2.2.0 is released it will become the current 
release and the 2.2 branch the current maintenance branch. No?

Cheers, Yuppie