[oe] OpenEmbedded Release 2010.12 --- needs your help!
paulepanter at users.sourceforge.net
Fri Nov 5 14:32:18 CET 2010
Dear OE folks,
Am Freitag, den 05.11.2010, 11:03 +0100 schrieb Eric Bénard:
> 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.
I certainly would encourage to push your changes to the OE repository as
soon as possible to share your work so other can use it or improve it.
Be it `master` or some different branch.
> 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.
I guess both sides have good arguments. I would decide on what the
documentation suggests to beginners and new contributors. If it suggests
that `master` is the development branch new contributions should be
based on, I suggest to create a new branch for the next stable release.
If the documentation suggests something different, then the next stable
release can be based on the master branch.
In either case the documentation has to be correct or needs to be
updated to reflect the changes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the Openembedded-devel