2011.03-maintenance created

[Stefan Schmidt]

Hello.

On Tue, 2011-03-08 at 08:27, Koen Kooi wrote:
> Op 8 mrt 2011, om 04:55 heeft Tom Rini het volgende geschreven:
> 
> > On 03/07/2011 05:27 AM, Koen Kooi wrote:
> >> 
> >> Op 6 mrt 2011, om 14:43 heeft Richard Purdie het volgende geschreven:
> >> 
> >>> On Fri, 2011-03-04 at 16:22 +0100, Koen Kooi wrote:
> >>>> After talking to Stefan and Tom I created
> >>>> http://cgit.openembedded.org/cgit.cgi/openembedded/log/?h=2011.03-maintenance, but we haven't decided on how to manage it yet. Since this branch will likely be heavily used due to the oe-core transition I wanted to get you opinion on how to manage this branch. The suggestions so far:
> >>>> 
> >>>> * backports only
> >>>> * pull model
> >>>> 
> >>>> I don't really have a strong preference either way. The previous
> >>>> "stable" branches have been victims of FUD, so it would be nice to
> >>>> have a blessing from the TSC this time :)
> >>> 
> >>> My suggestion is to have a clear owner of it. That person decides what
> >>> goes in and what the policy is for patch acceptance.
> >> 
> >> I can be the owner of that if Tom and/or Stefan don't want to do that, but I am worried about what Graeme said: http://www.xora.org.uk/2011/03/03/oe-board-resignation/
> > 
> > I've thought about it a bit and yeah, I'd be happy to run the maintenance branch, on a pull model.
> 
> Awesome!

Great. Just to avoid confusion on my part. With pull model you mean picking up
patches yourself from patchwork in this case? Or should people send real pull
request, with a branch to pull from, additional to the patches?

> > Khem, is it possible to setup patchwork to catch things on oe-devel with a specific subject line?  Or will they have to live in the main patchwork queue?  Thanks!
> 
> You can make a patchwork filter on the webpage, but it might be easier to setup a seperate ml, like oe-core does.

Hmm, I'm not sure that I'm in favour of yet another OE list. It may have some
traffic in the beginning but I expect it to go down heavily over time.

regards
Stefan Schmidt