All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE 2011.03 release vs. oe-core migration
Date: Mon, 07 Feb 2011 12:50:53 -0700	[thread overview]
Message-ID: <4D504D1D.80206@mentor.com> (raw)
In-Reply-To: <AANLkTiniBzwLJEqpedrY3Kg-yX==g3XXTxsqZCyef=+q@mail.gmail.com>

On 02/07/2011 12:36 PM, Khem Raj wrote:
> On Mon, Feb 7, 2011 at 8:08 AM, Stefan Schmidt
> <stefan@datenfreihafen.org>  wrote:
>> Hello.
>>
>> On Wed, 2011-01-26 at 07:55, Tom Rini wrote:
>>> On 01/26/2011 03:44 AM, Graeme Gregory wrote:
>>>> On 26/01/2011 10:23, Stefan Schmidt wrote:
>>>>>
>>>>> During last OEDEM we set out a timeline for quarterly releases. The first one
>>>>> hit on time in december 2010 (Thanks Khem).
>>>>>
>>>>> The next one would be scheduled for 2011-03. As our plans towards oe-core are
>>>>> getting into shape I wonder if and how these both are going to conflict.
>>>>>
>>>>> Will we go ahead and make the 2011-03 release, maybe the last one before moving
>>>>> over to oe-core? Personally I don't think these two block each other. Syncing
>>>>> would be needed, but people will keep working on the OE repo for a bit longer
>>>>> anyway I would think.
>>>>>
>>>>> If we are going to scratch the release what would be the next target for it?
>>>>> Yocto 1.0 is planned for April 2011. Somehow I doubt we will have oe-core ready
>>>>> for this in time, including yocto movs to it and we base the rest of OE on top
>>>>> of it. Am I wrong here and that is the actual plan?
>>>>>
>>>>>
>>>> My opinion is 2010-03 should be the last release on the old source tree.
>>>> Releases after this should be on the new oe-core layer system. I don't
>>>> think we should scrap the release as its going to take some time to kick
>>>> oe-core into shape and finish the poky merge. Then there is work on
>>>> meta-openembedded and meta-distro to do on top of that.
>>>
>>> I think this depends a little on who is going to run the release
>>> again.  We probably won't have a perfect release, stop committing,
>>> switch.  If we're looking for volunteers again to run the next
>>> release, assuming folks will be busy with the migration work too,
>>> I'd throw my hat in the ring (and defer to Khem if he wants to do it
>>> again, along with all of the fun we'll have in oe-core :))
>>
>> I would welcome if we could make the release manager role rotating. So if Tom
>> would be able to pick this up it would be great if Khem can feed him some of his
>> experience with the last release. Be it only theoretical with some hints or
>> practically with helping to review and apply patches towards. Does this sound
>> good to both of you?
>
> by all means. I would do it if no one else is doing.
>
>>
>> I will do some more testing over the next days/weeks and also trying to help
>> with some patches if needed.
>
> We need more people to sign up for testing the release

Specifically run-testing.  I can queue up a pretty good size matrix of 
build tests (and I'm adding Ubuntu 10.04 for a recent host distribution 
to the matrix) but run testing is much more limited.

-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2011-02-07 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 10:23 OE 2011.03 release vs. oe-core migration Stefan Schmidt
2011-01-26 10:44 ` Graeme Gregory
2011-01-26 11:12   ` Stefan Schmidt
2011-01-26 13:18     ` Frans Meulenbroeks
2011-01-26 14:55   ` Tom Rini
2011-02-07 16:08     ` Stefan Schmidt
2011-02-07 19:36       ` Khem Raj
2011-02-07 19:50         ` Tom Rini [this message]

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=4D504D1D.80206@mentor.com \
    --to=tom_rini@mentor.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.