From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Switch to PR server model for PR bumps - 1 week
Date: Wed, 05 Dec 2012 14:13:59 +0000 [thread overview]
Message-ID: <1354716839.25268.105.camel@ted> (raw)
I've made it clear we want and need to switch to the PR service for
handling PR bumps. I'd now like to put a deadline in place for doing
this, namely that I'm going to stop requiring PR bumps in patches as of
1 week's time. The TSC did discuss this and our conclusion was that we
need to switch early in this release cycle to give time for any issues
to get resolved. Now is a good time to do this as I think we're ready.
There were a number of open bugs related to the PR service[1]. We've
looked through them and they are now resolved with the exception of one
related to the incremental git PV issue for which we have a plan in
place and patches ready.
We've taken on board feedback about documentation and the following wiki
page has been setup which details the current situation:
https://wiki.yoctoproject.org/wiki/PR_Service
I appreciate this is going to be a disruptive change for some but I
believe it is in the best interests of the project longer term and that
we will have a better system as an end result of this. If people do run
into problems, please send email or file bugs. I'm trying to ensure
there are some people with time available to look into these issues as a
priority so we can make a smooth transition.
Cheers,
Richard
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=3310
next reply other threads:[~2012-12-05 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 14:13 Richard Purdie [this message]
2012-12-05 14:45 ` Switch to PR server model for PR bumps - 1 week Martin Jansa
2012-12-05 15:19 ` Richard Purdie
2012-12-05 15:24 ` Martin Jansa
2012-12-05 15:37 ` Richard Purdie
2012-12-06 4:20 ` Martin Jansa
2012-12-06 10:15 ` Richard Purdie
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=1354716839.25268.105.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