Hi,
Le 05/11/2010 10:49, Martin Jansa a écrit :
I know it could lower number of people using this future release branch
during testing period before release, but still seems better then pushing 3
weeks of commits from my local branch as soon as release is branched and
master open for new recipes again.
That's the way linux, u-boot& co are running and when the new merge window
opens several thousand of patches can be merged in a few days.
And also why there is linux-next, but I agree that in our scale we can keep new
recipes and features in local checkouts/out-of-tree branches without too
much pain in merging them after 3 weeks.
a temporary next branch could be open to host new big patches and then merged
to master once stable is out.
This way most peoples getting oe during the stabilization period will get
master and will test it and developers will be able to follow their
development in the next branch.
I think that during this stabilization weeks, developers have to do the effort
to checkout the next branch if they want to work on it and user must get the
master branch being stabilized as a default, but not the reverse.
Eric
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
