From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: OE-Core Release Status
Date: Thu, 27 Sep 2012 22:42:46 +0100 [thread overview]
Message-ID: <1348782166.15753.28.camel@ted> (raw)
We're now at -rc2 for the October release of OE-Core. I've noticed a
sudden surge of patches on the list, several of which are things like
version increments which are no longer really appropriate at this point
in the release cycle.
Why haven't we branched?
The plus side of branching now would be continued patches into master.
The downside is that QA and autobuilder resources are concentrating on
release and hence not on ensuring regressions are being added. I also
really need my energy focused on the release rather than reviewing other
code. I'm out of bandwidth so I'm putting off branching.
There is also the risk that if we branch, people will continue with
master development and ignore the release branch and I'd like to apply a
little pressure against this.
So if patches are getting ignored its likely they've been deemed not
suited to the state of the tree right now. I may start to queue things
on master-next but no guarantees and I would ask people to try and help
make the release a good one.
If there are patches being ignored you think do qualify for -rcX, please
ping me as it is hard to keep track of everything.
Cheers,
Richard
next reply other threads:[~2012-09-27 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 21:42 Richard Purdie [this message]
2012-09-28 18:02 ` OE-Core Release Status Martin Jansa
2012-09-28 21:24 ` Richard Purdie
2012-09-28 22:06 ` Martin Jansa
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=1348782166.15753.28.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox