From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded Release 2010.12 --- needs your help!
Date: Fri, 05 Nov 2010 11:03:54 +0100 [thread overview]
Message-ID: <4CD3D68A.9040704@eukrea.com> (raw)
In-Reply-To: <20101105094915.GM3440@jama>
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
next prev parent reply other threads:[~2010-11-05 10:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 20:04 OpenEmbedded Release 2010.12 --- needs your help! Leon Woestenberg
2010-11-04 20:31 ` Khem Raj
2010-11-04 22:06 ` Denys Dmytriyenko
2010-11-04 22:33 ` Eric Bénard
2010-11-04 22:47 ` Graham Gower
2010-11-04 22:47 ` Denys Dmytriyenko
2010-11-05 6:52 ` Martin Jansa
2010-11-05 7:27 ` Stefan Schmidt
2010-11-05 9:22 ` Eric Bénard
2010-11-05 9:49 ` Martin Jansa
2010-11-05 10:03 ` Eric Bénard [this message]
2010-11-05 13:32 ` Paul Menzel
2010-11-05 13:52 ` Martin Jansa
2010-11-04 22:14 ` Denys Dmytriyenko
2010-11-05 0:23 ` Richard Purdie
2010-11-05 9:08 ` Marco Cavallini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD3D68A.9040704@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.