All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: 1.4_M6.rc2
Date: Thu, 18 Apr 2013 08:35:03 +0100	[thread overview]
Message-ID: <1366270503.10502.23.camel@ted> (raw)
In-Reply-To: <CAPhnLPAqTd39NUkKt0dv_=W1Dooodzdg3WJ_q0An+ZjQNgRtEw@mail.gmail.com>

On Wed, 2013-04-17 at 13:14 -0700, Flanagan, Elizabeth wrote:
> We're delayed slightly for the 1.4_M6.rc2 build. The build should be
> soonish, once RP gives me the thumbs up. Please adjust your schedules
> accordingly, we're hoping to get this started in a few hours.

We do have a 1.6_M6.rc2 candidate build which is revision
87eb70243749e0e2431f98770746fa42002f4441 (dylan branch).

I suggest we start testing this with particular focus and prioritisation
on the systemd and sysvinit testing due to the changes that have gone in
last minute.

If any problems are discovered, please flag them ASAP as the plan would
be to abort this rc and rebuild if any issues in those areas are
discovered.

I should stress that DISTRO_FEATURES should not be changed in existing
build directories (reusing sstate is fine). Several of the init issues
we've see have been tracked down to this. Its never been supported
although is probably something we'll improve in 1.5 since it catches so
many people out. This note needs to be in the release notes as well.

Cheers,

Richard





  parent reply	other threads:[~2013-04-18  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 20:14 1.4_M6.rc2 Flanagan, Elizabeth
2013-04-18  0:13 ` 1.4_M6.rc2 Rifenbark, Scott M
2013-04-18  7:35 ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-18 22:02 1.4_M6.rc2 Flanagan, Elizabeth

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=1366270503.10502.23.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=elizabeth.flanagan@intel.com \
    --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.