From: Saul Wold <saul.wold@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: update status of M2 sprint tasks
Date: Mon, 13 Dec 2010 10:29:31 -0800 [thread overview]
Message-ID: <4D06660B.30707@intel.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D5A7A1691@shsmsx502.ccr.corp.intel.com>
On 12/13/2010 03:53 AM, Tian, Kevin wrote:
> Hi, owners,
>
> Since M2 code frozen happened last week and now M2 test has been started, could owners
> of each M2 sprint tasks update the latest status on the wiki?
>
> https://wiki.yoctoproject.org/wiki/Yocto_1.0_Schedule
>
> As Saul sent out earlier, we only accept bug fixes on M2 branch now. So if a given task has
> not been done (WIP or on track), could you either move it into M3 or fill an updated date
> when current one is past?
>
> --M2SB--
>
> "Distro Audit: Package Description/Summary completed", "WIP, Done by Dec 08" (Mark)
> "Zypper/RPM (small writeup)", "WIP, Done by Dec 06" (Mark/Qing)
> "oprofileUI", "WIP, done by Dec 10 " (Jessica)
>
> --M2SC--
> "Distro Audit: Licence Checksums ", "WIP, done by Dec 10 " (Saul)
Pending Patch is in distro Stage
> "Zypper/RPM (upgrade to latest version)", "Starting, done by Dec 10" (Mark/Qing)
> "push of all relevant Wind River patchs to Yocto ", "WIP, on track for completion by Dec 03 " (Mark)
> "Tracing: blktrace and sysprof recipes ", "sysprof by Dec 03 " (Tom)
>
> --M2SD--
> "Yocto Installer for SDK Generator Installation functions support ", "WIP, done Dec 09" (Jessica)
> "Yocto Installer support for image-creator ", "WIP" (Jessica)
>
> --M2SE--
> "Zypper/RPM (integration design)", "slipped out from sprint D" (Mark/Qing)
> "Distro Audit: Upgrades Completed (Phase1)", "WIP" (Saul)
Phase one status was best effort on the the update list, and I will have
a summary later this week.
> "Distro Audit: Src Checksums", "WIP, Done by Dec 9" (Saul)
All recipes now have SRC_URI Checksums, the checking work is part of the
Fetch which is pending with Ke and Richard.
> "enable KVM with qemu", "on track" (Saul/Edwin)
Done and in Master
> "Performance Enhancement Completed", "on track being reviewed" (Saul/Dongxiao/Qing)
Code is being review by RP, and I think there is some questions about
the usage of the hard links.
> "User specified qemu config support", "on track for Dec 9" (Saul/Criping)
Not sure what the status of this is currently.
> "SDK Version Control support in SDK generator installer", "on track" (Jessica)
> "Tracing: Initial SystemTap recipe", "on track" (Tom)
> "Documentation for swabber", "on track" (Alex)
> "Defect triage process in public documented and implemented" (Saul)
Bug Triage Process is on the Public website, some images need to be
updated and I now have the source for those, this can be independent
from the release process.
>
> Thanks
> Kevin
next prev parent reply other threads:[~2010-12-13 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 11:53 update status of M2 sprint tasks Tian, Kevin
2010-12-13 11:58 ` Tian, Kevin
2010-12-13 16:31 ` Mark Hatle
2010-12-13 18:32 ` Saul Wold
2010-12-13 19:03 ` Saul Wold
2010-12-13 18:29 ` Saul Wold [this message]
2010-12-14 7:50 ` Tom Zanussi
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=4D06660B.30707@intel.com \
--to=saul.wold@intel.com \
--cc=kevin.tian@intel.com \
--cc=poky@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox