Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Stable release of oe-core
Date: Mon, 26 Mar 2012 23:16:43 +0100	[thread overview]
Message-ID: <1332800203.28414.142.camel@ted> (raw)
In-Reply-To: <20120326203256.GB3368@denix.org>

On Mon, 2012-03-26 at 16:32 -0400, Denys Dmytriyenko wrote:
> On Mon, Mar 26, 2012 at 04:25:19PM -0400, Brandon Stafford wrote:
> > Hi all,
> > 
> > I don't see an RC branch or anything like that in the git repo. I'm
> > about to make the leap from the oe classic 2011.03-maintenance branch
> > to oe-core, so I'm trying to figure out the right place to land.
> > 
> > In the March 13, 2012, OE TSC minutes, I noticed this text:
> >   c. oe-core release
> >       feature freeze in 1 week
> >       final freeze 2-3 weeks from 18 Mar
> > 
> > Do I just need a little patience?
> 
> Correct, OE-Core (and some other layers) follows the 6-month release schedule of
> the Yocto Project (which is October and April) that is getting ready for v1.2:
> 
> http://www.yoctoproject.org/blogs/davest/2012/progress-yocto-project-v1.2

We're due a -rc1 right around now, the deadline was actually midnight
Sunday but I'm still trying to sort out various patches.

We've also not branched yet as if we do, people tend to start developing
against master and I'd like to focus people on the stabilisation, at
least for a short while :).

Cheers,

Richard





      reply	other threads:[~2012-03-26 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 20:25 Stable release of oe-core Brandon Stafford
2012-03-26 20:32 ` Denys Dmytriyenko
2012-03-26 22:16   ` Richard Purdie [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=1332800203.28414.142.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