Re: [2.6] Most likely to be merged by Halloween... THE LIST]

[Hans Reiser <reiser@namesys.com>]

What I was advocating was a schedule of:

1) feature submission deadline

2) period of working through feature backlog

3) feature acceptance ending date

Most release management teams in the industry do things this way, 
and.... I'd better say no more, those words will lose me the argument.;-)

I'll admit that in most companies the features to be merged backlog 
period lasts for only a few days, and due to the difference in scale, it 
would probably last a few weeks for Linux, but in my egocentrism I 
really think that providing submitters with certainty as to what they 
need to do to get a patch in is a good thing.

I understand though that maybe the needs of the submitters aren't the 
most important thing for Linux as a whole, and so others will 
legitimately disagree.

Hans

Rik van Riel wrote:

>On Sat, 20 Jul 2002, Hans Reiser wrote:
>
>  
>
>>That could be dealt with by letting people resend feature containing
>>patches that were first submitted by Halloween (forward porting them as
>>things progress) until they get a rejection or Linus announces he has
>>taken all that he wants from the queue.
>>    
>>
>
>I hope the Halloween feature freeze really will be a feature
>freeze.  Nothing is more frustrating than having a "stable
>kernel" broken every second release by yet another feature.
>
>If we all restrain ourselves 2.6 will be stable soon and 2.7
>will be started shortly after. Backporting "essential" features
>from 2.7 into a _stable_ 2.6 will be so much easier than trying
>to stabilise a 2.6-pre that's full to the brim of not-yet-stable
>new features.
>
>regards,
>
>Rik
>  
>


-- 
Hans