From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: Yocto Project 1.2 Release Status
Date: Wed, 18 Apr 2012 16:20:45 +0100 [thread overview]
Message-ID: <1334762445.24091.110.camel@ted> (raw)
In-Reply-To: <20120418145330.GM3635@jama.jama.net>
On Wed, 2012-04-18 at 16:53 +0200, Martin Jansa wrote:
> On Wed, Apr 18, 2012 at 03:47:47PM +0100, Richard Purdie wrote:
> > I thought I'd update everyone with the current 1.2 status.
> >
> > I'm going to branch master for release at this point. We've fixed a lot
> > of issues, I'm hoping the -rc4 build will be a good one. There are signs
> > there are some more minor issues around and bugs do keep getting opened.
> > These are still being investigated so we'll continue to let that happen.
> > Once we have a QA report for -rc4, we'll be in a better position to make
> > a call on how things are looking.
>
> Does it mean that after creating branch, master will be open for
> postponed patches from ML and master-next or do you want to keep master
> as close to release branch as possible for some time (e.g. for those
> 1.2.1 fixes)?
I have hoped people would work more on the stabilisation and testing but
I don't think I'll be able to hold off the pressure to start master
rolling again at some point relatively soon.
It won't happen immediately as the 1.2 release is building which means I
have no resources to test master right now so I will hold off until
those are available.
To be honest at a personal level, I'm also pretty worn out after the
past couple of weeks of bug fixing, triage and review and would ideally
like to disappear for a couple of weeks. Realistically this isn't going
to happen now but maybe in a few weeks...
Cheers,
Richard
next prev parent reply other threads:[~2012-04-18 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 14:47 Yocto Project 1.2 Release Status Richard Purdie
2012-04-18 14:51 ` Koen Kooi
2012-04-18 14:53 ` Martin Jansa
2012-04-18 15:20 ` Richard Purdie [this message]
2012-04-18 15:56 ` Darren Hart
2012-04-18 16:22 ` Chris Larson
2012-04-18 17:02 ` Richard Purdie
2012-04-18 17:06 ` Chris Larson
2012-04-18 17:11 ` Chris Larson
2012-04-18 17:16 ` Otavio Salvador
2012-04-18 18:56 ` 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=1334762445.24091.110.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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