All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Liu, Song" <song.liu@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Minutes: Yocto Project 1.4 M4 release readiness discussion
Date: Fri, 1 Mar 2013 22:53:24 +0100	[thread overview]
Message-ID: <20130301215324.GU3279@jama> (raw)
In-Reply-To: <7E680CB2A76BB8438D08CF13C09FC53A70EF1ED1@ORSMSX101.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]

On Fri, Mar 01, 2013 at 08:01:17PM +0000, Liu, Song wrote:
> Attendees:
> AlexG, ThaddeusL, Cristian, Dave, Richard, Jessica, Nitin, Song
> 
> 
> Release criteria review:
> Please see the wiki page:  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status#Milestone_4<https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status>
> 
> 1.      All release criteria has been reviewed. M4 met all the criteria.
> 2.      Highlights:
> a.      12% performance increase on overall build time. Cut the rootfs build time with sstate on by half.
> 3.      Issues:
> a.      The # of bugs seems high. Plan: Bug triage team is doing a round of triage for all medium+ and medium bugs to focus the team on fixing the right set of bugs. The team will focus more on bugs for the rest of the release.
> b.      Dave: not enough CCB members present in this meeting. Cannot approve the release.
> 
> Decision: Song will follow up with Dave and the CCB to get approval for the release.

I think it would be good to finish discussion in thread
[OE-core] RFE: make the init manager an image feature (again)
and resolve systemd situation asap, otherwise we're risking
meta-openembedded release or quality of such release.

meta-systemd is broken for >month so people cannot even test it
with current master and couple of important meta-oe developers are
against changing meta-systemd so it gets compatible with current oe-core
but breaks their use-case and also there is no plan for upgrade path
from danny+meta-systemd to Yocto-Project_v1.4 release.

Stalling that discussion till milestone 5 or 6 won't help resolving it 
to work for everybody.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-03-01 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 20:01 Minutes: Yocto Project 1.4 M4 release readiness discussion Liu, Song
2013-03-01 21:53 ` Martin Jansa [this message]
2013-03-01 23:08   ` Burton, Ross
2013-03-01 23:32     ` Martin Jansa
2013-03-01 23:56       ` Burton, Ross
2013-03-02  0:14         ` Martin Jansa

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=20130301215324.GU3279@jama \
    --to=martin.jansa@gmail.com \
    --cc=song.liu@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.