Re: iptables branch management

[Patrick McHardy <kaber@trash.net>]

Am 08.09.2011 13:59, schrieb Jan Engelhardt:
> On Thursday 2011-09-08 12:05, Patrick McHardy wrote:
> 
>> Am 05.09.2011 19:54, schrieb Pablo Neira Ayuso:
>>> Hi Jan,
>>>
>>> On Fri, Sep 02, 2011 at 04:20:13PM +0200, Jan Engelhardt wrote:
>>>> Hei
>>>>
>>>> I would like to propose a "stable" branch that would be rooted 
>>>> in the most recent tag and only receive fixes. Furtheremore, 
>>>> the branch is merged time and again into master, so that the 
>>>> fix is available in both without cherry-pick. 1.4.12.x releases be made 
>>>> from stable, and 1.4.y from master.
>>>> How about it?
>>>
>>> Hm, I remember that we had this discussion before.
>>>
>>> I think it's probably too much overhead for it, looking at how other
>>> similar net-tools are maintained, the amount of contributions that
>>> er receive and amount of changes that get into every version.
>>
>> I also think this is probably overkill, what's wrong with simply
>> creating stable branches on demand if there are important fixes
>> that require a new release?
> 
> Nothing wrong, it just has not been done consistently or at all in the 
> past. I believe it does not hurt to go ahead with this, also since I am 
> statistically taking care of most submissions these days anyway.

What has been done in the past doesn't really matter, we can of course
agree to have a stable branch when needed. But I don't see the point of
having a stable branch as long as it doesn't contain any fixes.