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 18:02:17 +0100 [thread overview]
Message-ID: <1334768537.24091.156.camel@ted> (raw)
In-Reply-To: <CABcZANkaABCKZ+WmhhGTZEvFnHYwrP7uNSSvNTxxKxfun4JaPA@mail.gmail.com>
On Wed, 2012-04-18 at 09:22 -0700, Chris Larson wrote:
> On Wed, Apr 18, 2012 at 8:20 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 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.
>
> Just because people have things to push or are pushing things which
> aren't bugfixes doesn't mean their time is being taken up by anything
> but stabilization right now. Your statement implies that everything
> being pushed is being currently worked on, which is incorrect. I'm
> sure Mentor isn't the only company with a backlog of already complete
> local changes to get upstream..
So you're saying Mentor has been working on stabilization and has a
queue of bugfixes which they've not shared?
This doesn't help us much with the quality of this release :/ At least
the next one might benefit I guess assuming you can resolve that backlog
problem...
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
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: [OE-core] Yocto Project 1.2 Release Status
Date: Wed, 18 Apr 2012 18:02:17 +0100 [thread overview]
Message-ID: <1334768537.24091.156.camel@ted> (raw)
In-Reply-To: <CABcZANkaABCKZ+WmhhGTZEvFnHYwrP7uNSSvNTxxKxfun4JaPA@mail.gmail.com>
On Wed, 2012-04-18 at 09:22 -0700, Chris Larson wrote:
> On Wed, Apr 18, 2012 at 8:20 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 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.
>
> Just because people have things to push or are pushing things which
> aren't bugfixes doesn't mean their time is being taken up by anything
> but stabilization right now. Your statement implies that everything
> being pushed is being currently worked on, which is incorrect. I'm
> sure Mentor isn't the only company with a backlog of already complete
> local changes to get upstream..
So you're saying Mentor has been working on stabilization and has a
queue of bugfixes which they've not shared?
This doesn't help us much with the quality of this release :/ At least
the next one might benefit I guess assuming you can resolve that backlog
problem...
Cheers,
Richard
next prev parent reply other threads:[~2012-04-18 17:11 UTC|newest]
Thread overview: 20+ 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 14:53 ` [OE-core] " Martin Jansa
2012-04-18 15:20 ` Richard Purdie
2012-04-18 15:20 ` [OE-core] " Richard Purdie
2012-04-18 15:56 ` Darren Hart
2012-04-18 15:56 ` [OE-core] " Darren Hart
2012-04-18 16:22 ` Chris Larson
2012-04-18 16:22 ` [OE-core] " Chris Larson
2012-04-18 17:02 ` Richard Purdie [this message]
2012-04-18 17:02 ` Richard Purdie
2012-04-18 17:06 ` Chris Larson
2012-04-18 17:06 ` [OE-core] " Chris Larson
2012-04-18 17:11 ` Chris Larson
2012-04-18 17:11 ` [OE-core] " Chris Larson
2012-04-18 17:16 ` Otavio Salvador
2012-04-18 17:16 ` [OE-core] " Otavio Salvador
2012-04-18 18:56 ` Richard Purdie
2012-04-18 18:56 ` [OE-core] " 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=1334768537.24091.156.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 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.