[z3-five] SVN: Products.Five/branches/1.5/ Tag a release branch for the 1.5 line.

[yuppie]

Hi!


Tres Seaver wrote:
> 
> yuppie wrote:
>>
>> Tres Seaver wrote:
>>> Log message for revision 70512:
>>>   Tag a release branch for the 1.5 line.
>>>
>>> Changed:
>>>   A   Products.Five/branches/1.5/
>>>
>>> -=-
>>> Copied: Products.Five/branches/1.5 (from rev 69454, Products.Five/trunk)
>> There are two issues with this checkin:
>>
>> 1.) It is not in line with our current policy:
>> http://codespeak.net/pipermail/z3-five/2006q3/001639.html
> 
> That mail says:
> 
>   As Five 1.2 is now phasing out and we might start development on Five
>   1.6 (see below), a Five 1.5 branch is to be expected soon. Anyone is
>   welcome to create it in order to lift the current feature freeze on
>   the trunk.

You are quoting this out of context. Philipp used the trunk because it 
made maintenance easier - not because creating a branch would have been 
hard work. Lifting the current feature freeze should not be done just 
for fun - it should only be done if someone actually wants to check in a 
new feature.

>> 2.) The branch was copied from a historical revision, the latest bugfix
>> (r69839) is missing on the branch.
> 
> The branch was copied from the same revisiton that the 1.5 tag was made
> from.

That mail also says:

    There currently is no Five 1.5 branch. The trunk is Five 1.5.x.

Until the trunk is needed for new features Five 1.5 maintenance is done 
on the trunk. Delaying branch creation doesn't make any sense if we have 
to backport all fixes at a later point. It *makes* sense if trunk 
bugfixes become automatically part of the 1.5 branch by creating it from 
the *latest* non-feature revision of the trunk.

>> I was planning to backport some bugfixes from Zope3 to Five and I can't
>> see a good reason why I should do that twice (1.5 branch *and* trunk).
> 
> Because we are supporting 2.10, while still allowing feature development
> to go forward?
> 
>> I propose to delete the 1.5 branch. Of course anybody is welcome to
>> create it again from the *latest* trunk revision *if* she wants to add a
>> new feature on the trunk.
> 
> - -1.  1.5 *already shipped* with Zope3, and has known bugs (the one I
> fixed, for instance).  How do you propose that we fix such bugs to
> support 2.10 without leaving the trunk frozen forever?

I think Philipp made clear that new features are welcome at any time - 
you just have to create the 1.5 branch before checking them in.


Cheers,

	Yuppie