charter for -next

charter for -next

[Stefan Richter]

What should I ask myself before I commit something to the branch which 
Stephen pulls into -next?

     Is this ready to be pulled by Linus right now if he had a merge
     window open today?
or
     Is it likely that I will let Linus pull this when he opens his next
     merge window?  (Assuming I can roughly predict when this will be,
     and what other work will likely be done until then, e.g. pending
     reviewer feedback, or patches for related functionality which should
     be bundled with the work in question...)
-- 
Stefan Richter
-=====-==--- -=-= ---==
http://arcgraph.de/sr/

Re: charter for -next

[Jeff Garzik]

Stefan Richter wrote:
> What should I ask myself before I commit something to the branch which 
> Stephen pulls into -next?
> 
>     Is this ready to be pulled by Linus right now if he had a merge
>     window open today?

I was under the impression it was the above -- anything in linux-next 
should be ready to be pulled by Linus.  The maintainer considers those 
changes "ready for next merge window."

	Jeff

Re: charter for -next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

Hi Stefan,

On Sat, 03 May 2008 12:12:50 +0200 Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>
> What should I ask myself before I commit something to the branch which 
> Stephen pulls into -next?
> 
>      Is this ready to be pulled by Linus right now if he had a merge
>      window open today?

This is what I want ideally.  So as stuff stabilises in subsystem trees,
it can be incorporated into linux-next and we can then figure out the
problems introduced by interactions with other subsystems.

>      Is it likely that I will let Linus pull this when he opens his next
>      merge window?  (Assuming I can roughly predict when this will be,
>      and what other work will likely be done until then, e.g. pending
>      reviewer feedback, or patches for related functionality which should
>      be bundled with the work in question...)

I suspect that this is what I got in some cases during the last
cycle :-) :-(

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]