Yocto 1.2 Schedule: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
|||
Line 4: | Line 4: | ||
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]. Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done. | To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]. Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done. | ||
== M1 (Oct. 31 to Dec. 23, 2011 -- 8 weeks: planning done in week 1, development week 1-5, | == M1 (Oct. 31 to Dec. 23, 2011 -- 8 weeks: planning done in week 1, development week 1-5, stabilization week 6-7, release week 8) == | ||
=== M1 Feature Development (Oct. 31 to Dec. 23, 2011) === | === M1 Feature Development (Oct. 31 to Dec. 23, 2011) === | ||
{| border="1" | {| border="1" | ||
Line 65: | Line 65: | ||
* M1 Release readiness meeting: 12/21/2011 | * M1 Release readiness meeting: 12/21/2011 | ||
* M1 release: 12/23/11 | * M1 release: 12/23/11 | ||
== M2 (Dec. 12 to Jan. 27, 2011 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-6, release week 7) == | |||
=== M1 Feature Development (Oct. 31 to Dec. 23, 2011) === | |||
{| border="1" | |||
| align="center" style="background:#f0f0f0;"|'''Featuer #''' | |||
| align="center" style="background:#f0f0f0;"|'''Summary''' | |||
| align="center" style="background:#f0f0f0;"|'''Target Milestone''' | |||
| align="center" style="background:#f0f0f0;"|'''Pirority/Estimate/Status''' | |||
| align="center" style="background:#f0f0f0;"|'''Owner''' | |||
|- | |||
| 1655||Export of source tarball or package||1.2 M2||[P3] [10D]||Xiaofeng.yan@windriver.com | |||
|- | |||
| 1678||kernel usability scripts||1.2 M2||[P2][10D]||tom.zanussi@intel.com | |||
|- | |||
| 1630||Provide a click through license mechanism||1.2 M2||[P2][10D]||tom.zanussi@intel.com | |||
|- | |||
| 1543||Improve error handling and feedback to users||1.2 M2||[P1][D15]||scott.a.garman@intel.com | |||
|- | |||
| 1557||Build Appliance: Pre-configured VM Build image built by Yocto||1.2 M2||[P1][D30] for 2 people||saul.wold@intel.com | |||
|- | |||
| 1654||Layer tooling: Tool to combine layers||1.2 M2||[P3][D1]||paul.eggleton@linux.intel.com | |||
|- | |||
| 1566||Package History: Data Analysis||1.2 M2||[P1][D15]||paul.eggleton@linux.intel.com | |||
|- | |||
| 1651||Incremental image generation||1.2 M2||[P3][D10]||liezhi.yang@windriver.com | |||
|- | |||
| 1682||A scripts to clean obsolote sstate cache files||1.2 M2||[P3][D10]||liezhi.yang@windriver.com | |||
|- | |||
| 1126||pending tasks and discussion about the networked PR service||1.2 M2||[P2][D5] for first 3 tasks in the wiki pages, other tasks pending community feedback||lianhao.lu@intel.com | |||
|- | |||
| 1555||Make BasicHash the default signature generator||1.2 M2||[P1][D1] it wouldn\'t be much workload after we close the bug #1556 and #1126||lianhao.lu@intel.com | |||
|- | |||
| 1556||Handled Releases with the PR server||1.2 M2||[P1][D10] Need community feedback after we have a working code branch||lianhao.lu@intel.com | |||
|- | |||
| 1656||Recipe creation/import script||1.2 M2||[P3][15D]||kai.kang@windriver.com | |||
|- | |||
| 1608||Improve device management||1.2 M2||[P2][1D]||josh@linux.intel.com | |||
|- | |||
| 1610||Eclipse BSP/Kernel Plugin||1.2 M2||[p2][d5]||jessica.zhang@intel.com | |||
|- | |||
| 1612||Build statistics reporting||1.2 M2||[P2][D16]||elizabeth.flanagan@intel.com | |||
|- | |||
| 1628||Autobuilder layer support||1.2 M2||[P2][D4]||elizabeth.flanagan@intel.com | |||
|- | |||
| 1614||Target module build||1.2 M2||[P3][3D]||dvhart@linux.intel.com | |||
|- | |||
| 1642||Minimal Image unique||1.2 M2||[P2][15D]||dvhart@linux.intel.com | |||
|- | |||
| 1647||Upstream config fragments||1.2 M2||[P2][2D]||dvhart@linux.intel.com | |||
|- | |||
| 1649||Define Kernel policy||1.2 M2||[P2][10D]||dvhart@linux.intel.com | |||
|- | |||
| 1621||Running post installs at rootfs gen time||1.2 M2||[P2][D10]||dexuan.cui@intel.com | |||
|- | |||
| 1643||Kernel Tools||1.2 M2||[P2][10D]||bruce.ashfield@windriver.com | |||
|- | |||
| 1638||replace qemuppc||1.2 M2||[P2] [15D]||bruce.ashfield@windriver.com | |||
|} | |||
==== Stabilize schedule ==== | |||
'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)''' | |||
* RC1: 1/4/12 | |||
* RC2: 1/11/12 | |||
* M1 Release readiness meeting: 1/18/12 or 1/25/12 | |||
* M1 release: 1/27/12 |
Revision as of 23:09, 6 November 2011
Yocto Project 1.2 (release date: April 6, 2012)
The detailed milestone map for the 1.2 release of Yocto Project is as below. To view the Yocto schedule-at-a-glance, go to YoctoCalendar. Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done.
M1 (Oct. 31 to Dec. 23, 2011 -- 8 weeks: planning done in week 1, development week 1-5, stabilization week 6-7, release week 8)
M1 Feature Development (Oct. 31 to Dec. 23, 2011)
Featuer # | Summary | Target Milestone | Pirority/Estimate/Status | Owner |
1567 | QA Tests: Add recipe for LSB Tests and automate test | 1.2 M1 | [P2][5D] | yi.zhao@windriver.com |
1674 | run gtk+ over directfb | 1.2 M1 | [P2][D10] | Xiaofeng.yan@windriver.com |
1660 | crownbay: add support for video acceleration | 1.2 M1 | [P2][10D] | tom.zanussi@intel.com |
1661 | meta-intel: streamline and clean up kernel config options and machine conf files | 1.2 M1 | [P2][5D] | tom.zanussi@intel.com |
1008 | New santiy check for userspace packages | 1.2 M1 | [P2][D4] | scott.a.garman@intel.com |
1598 | Add remote layer support | 1.2 M1 | [P3][D5][Design] | paul.eggleton@linux.intel.com |
1565 | Package History: Data Collection | 1.2 M1 | [P1][D4] | paul.eggleton@linux.intel.com |
1589 | Disk space monitoring | 1.2 M1 | [P3][D10] | liezhi.yang@windriver.com |
1603 | Add recipe supporting autoconf-nativesdk and automake-nativesdk | 1.2 M1 | [P2] [D10] | kai.kang@windriver.com |
1582 | Host intrusion prevention/Swabber | 1.2 M1 | [P2][10D][Design] | josh@linux.intel.com |
1568 | QA Tests: Add recipe for ltp/posix tests and automate test | 1.2 M1 | [P2][3D] | jiajun.xu@intel.com |
1580 | Add Valgrind support in remote tools | 1.2 M1 | [P2][d10][Design] | jessica.zhang@intel.com |
1461 | Put a uname and ab name in stdio | 1.2 M1 | [P3][D0] | elizabeth.flanagan@intel.com |
1546 | License file WARNING messages | 1.2 M1 | [P1][D1] | elizabeth.flanagan@intel.com |
1627 | Autobuilder clean sstate option | 1.2 M1 | [P2][D1] | elizabeth.flanagan@intel.com |
1629 | Buildstats memory measurements | 1.2 M1 | [P2][D3] | elizabeth.flanagan@intel.com |
1635 | Drop Grub for Syslinux | 1.2 M1 | [P2][5D] | dvhart@linux.intel.com |
1636 | Upgrade to EFI | 1.2 M1 | [P2][5D] | dvhart@linux.intel.com |
1564 | Multilib: Drop MULTILIB_IMAGE_INSTALL | 1.2 M1 | [P2][D3] | dongxiao.xu@intel.com |
1634 | BSP update/intro | 1.2 M1 | [P2][5D][Design] | bruce.ashfield@windriver.com |
1644 | Use cases | 1.2 M1 | [P1][2D][Design review] | bruce.ashfield@windriver.com |
Stabilize schedule
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
- RC1: 11/30/11
- RC2: 12/7/11
- RC3: 12/14/11
- M1 Release readiness meeting: 12/21/2011
- M1 release: 12/23/11
M2 (Dec. 12 to Jan. 27, 2011 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-6, release week 7)
M1 Feature Development (Oct. 31 to Dec. 23, 2011)
Featuer # | Summary | Target Milestone | Pirority/Estimate/Status | Owner |
1655 | Export of source tarball or package | 1.2 M2 | [P3] [10D] | Xiaofeng.yan@windriver.com |
1678 | kernel usability scripts | 1.2 M2 | [P2][10D] | tom.zanussi@intel.com |
1630 | Provide a click through license mechanism | 1.2 M2 | [P2][10D] | tom.zanussi@intel.com |
1543 | Improve error handling and feedback to users | 1.2 M2 | [P1][D15] | scott.a.garman@intel.com |
1557 | Build Appliance: Pre-configured VM Build image built by Yocto | 1.2 M2 | [P1][D30] for 2 people | saul.wold@intel.com |
1654 | Layer tooling: Tool to combine layers | 1.2 M2 | [P3][D1] | paul.eggleton@linux.intel.com |
1566 | Package History: Data Analysis | 1.2 M2 | [P1][D15] | paul.eggleton@linux.intel.com |
1651 | Incremental image generation | 1.2 M2 | [P3][D10] | liezhi.yang@windriver.com |
1682 | A scripts to clean obsolote sstate cache files | 1.2 M2 | [P3][D10] | liezhi.yang@windriver.com |
1126 | pending tasks and discussion about the networked PR service | 1.2 M2 | [P2][D5] for first 3 tasks in the wiki pages, other tasks pending community feedback | lianhao.lu@intel.com |
1555 | Make BasicHash the default signature generator | 1.2 M2 | [P1][D1] it wouldn\'t be much workload after we close the bug #1556 and #1126 | lianhao.lu@intel.com |
1556 | Handled Releases with the PR server | 1.2 M2 | [P1][D10] Need community feedback after we have a working code branch | lianhao.lu@intel.com |
1656 | Recipe creation/import script | 1.2 M2 | [P3][15D] | kai.kang@windriver.com |
1608 | Improve device management | 1.2 M2 | [P2][1D] | josh@linux.intel.com |
1610 | Eclipse BSP/Kernel Plugin | 1.2 M2 | [p2][d5] | jessica.zhang@intel.com |
1612 | Build statistics reporting | 1.2 M2 | [P2][D16] | elizabeth.flanagan@intel.com |
1628 | Autobuilder layer support | 1.2 M2 | [P2][D4] | elizabeth.flanagan@intel.com |
1614 | Target module build | 1.2 M2 | [P3][3D] | dvhart@linux.intel.com |
1642 | Minimal Image unique | 1.2 M2 | [P2][15D] | dvhart@linux.intel.com |
1647 | Upstream config fragments | 1.2 M2 | [P2][2D] | dvhart@linux.intel.com |
1649 | Define Kernel policy | 1.2 M2 | [P2][10D] | dvhart@linux.intel.com |
1621 | Running post installs at rootfs gen time | 1.2 M2 | [P2][D10] | dexuan.cui@intel.com |
1643 | Kernel Tools | 1.2 M2 | [P2][10D] | bruce.ashfield@windriver.com |
1638 | replace qemuppc | 1.2 M2 | [P2] [15D] | bruce.ashfield@windriver.com |
Stabilize schedule
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
- RC1: 1/4/12
- RC2: 1/11/12
- M1 Release readiness meeting: 1/18/12 or 1/25/12
- M1 release: 1/27/12