nyuuzyou/wikis huggingface dataset:
Yocto 1.2.1 Test Report

This page is to hold the Test Report for Yocto 1.2.1
====Yocto 1.2.1 Fullpass Test Report====
This is the full pass report for 1.2.1. Most of the issues were found in Core Build System (7) and a two bugs for e-menlow and n450. The build performance of the system on a Core i7 for core-image-sato is 112 minutes. FRI2 could not be tested – no sato image was built. Most issues were reported for Core Build System.
More details below:
Test Summary:
File:Fullpass_Yocto1.2.1_TestSummary.JPG
Test detail Summary:
File:Fullpass_Yocto1.2.1_TestDetailSummary.JPG
The Distro Testing targets were:
Fedora 17, OpenSuse 12.1 and Ubuntu 12.04
* You can check the detailed test result in attachment for each target.
* The failed/blocked case number is listed with failed cases’ bug number.
Distribution Test:
File:Fullpass_Yocto1.2.1_DistributionTest.JPG
Commit Information:
Tree/Branch: denzil
Commit id: 73cdebf60df225ee10f2eb215935be3b61e1b831
Yocto 1.2M3 RC1 Fullpass Test Report

====Yocto 1.2M3 RC1 Fullpass Test Report====
This is the current fullpass test status for Yocto 1.2-M3 RC1 build. There are 10 new bugs found and 4 bugs fixed for this build. Crownbay testing is blocked due to build failure. multilib and meta-x32 could not work. build nonGPLv3 image failed for util-linux-native-2.21-r0 (There is fixing patch on master for the issue).
For ADT, Some of ADT test cases blocked due to Glxgears failed, testing is against ubuntux86-64 OS and FC16-x86 OS and 3 bugs found. ADT-installer failed to install PPC Target architectures. Fail to build project based on Clutter with target arch arm/mips/ppc. The version of lttng mismatch between qemu target and eclipse. 
For HOB,the testing is against master(a439d32dd84...).since there are some patches not in master, some bugs still exist. There are 2 new bugs found. Sato build has no X related packages. parsing could not return with Server/Client mode. 
QEMU target and BSPS could work well without issue.
Test Summary:
Test detail Summary:
* You can check the detailed test result in attachment for each target.
* The failed/blocked case number is listed with failed cases’ bug number.
Commit Information:
Tree/Branch:Poky/1.2_M3
Commit id: 320558f494c618f53e0c773db3ea0109476e8359 
Meta branch: 1.2_M3
Commit id:df18b721f86f0737c0f302e49b27ea232c70e683
Issue Summary:
Yocto 1.2 Features ELCE

== Yocto Project 1.2 Features Planning & Discussion Session, ELCE 2011 ==
This page tracks the planning and discussion session for the Yocto Project 1.2 release, targeted for April 2012. The planning session will take place on Saturday, 29 October, 2011 in Prague, Czech Republic, immediately following the Embedded Linux Conference Europe. ELCE attendees are welcome and encouraged to attend this planning session.
Where: TBD (probably in the Clarion Congress hotel, Prague)
When: TBD (probably 9am - 12am)
Attendees:
* Richard Purdie (project architect)
* Dave Stewart (engineering manager, Intel team)
* Jeff Osier-Mixon (community manager)
Agenda Items:
* your agenda item goes here
Yocto 1.2 M3 RC1 Test Report

This page is to hold Fullpass Test Report for Yocto 1.2 M3 RC1
====Yocto 1.2M3 RC1 Fullpass Test Report====
This is the current fullpass test status for Yocto 1.2-M3 RC1 build. There are 10 new bugs found and 4 bugs fixed(bug1908,1909,1976,1982) for this build. Crownbay testing is blocked due to build failure. Build failed when multilib enable.‘linux-korg_3.1.bb’ parsing error to build when meta-x32 layer enable. do_patch task failed for util-linux-native-2.21-r0 (There is fixing patch on master for the issue). bitbake-prserv is not executable. bitbake-prserv-tool import failed with no PRSERV set. 
For ADT, Some of ADT test cases blocked due to bug1927 and bug1886, testing is against ubuntux86-64 OS and FC16-x86 OS and 3 bugs found. ADT-installer failed to install PPC Target architectures. Fail to build project based on Clutter with target arch arm/mips/ppc. The version of lttng mismatch between qemu target and eclipse. 
For HOB,the testing is against master(a439d32dd843d10a9f65cc858b02422fac7deb50).since there are some patches not in master, some bugs still exist. There are 2 new bugs found. Sato build has no X related packages. parsing could not return with Server/Client mode. QEMU target and BSPS could work well without issue.
Test Summary:
Test detail Summary:
* You can check the detailed test result in attachment for each target.
* The failed/blocked case number is listed with failed cases’ bug number.
Commit Information:
Tree/Branch:Poky/1.2_M3
Commit id: 320558f494c618f53e0c773db3ea0109476e8359 
Meta branch: 1.2_M3
Commit id:df18b721f86f0737c0f302e49b27ea232c70e683
Issue Summary:
Yocto 1.2 Schedule

= Yocto Project 1.2 (release date: April 27, 2012) =
----
The detailed milestone map for the 1.2 release of Yocto Project is as below. If you would like to have a real time dynamic view of all scheduled features for 1.2, please click here . 
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. 2, 2011) ===
==== M1 Stabilize schedule ====
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 12/7/11
* RC2: 12/14/11
* M1 Release readiness meeting: 12/21/2011
* M1 release: 12/23/11
== M2 (Dec. 12, 2011 to Feb. 3, 2012 -- 8 weeks: planning done in week 1, development week 1-4, stabilization week 5-6, week 7: Chinese New Year holiday for teams in China, release week 8) ==
=== M2 Feature Development (Dec. 12, 2011 to Jan. 6, 2012) ===
==== M2 Stabilize schedule ====
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/11/12
* RC2: 1/18/12
* M2 Release readiness meeting:1/25/12
* M2 release: 2/3/12
== M3 (Jan. 23 to Mar. 16, 2012 -- 9 weeks: planning done in week 1-2, development week 1-6, stabilization week 7-8, release week 9) ==
=== M3 Feature Development (Jan. 23 to Feb. 24, 2012) ===
==== M3 Stabilize schedule ====
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/29/12
* RC2: 3/7/12
* M3 Release readiness meeting: 3/14/12
* M3 release: 3/16/12
== M4 (Mar. 5 to Apr. 27, 2012 -- 8 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 8) ==
=== M4 Feature Development (Mar. 5 to Mar. 18, 2012) ===
==== M4 Stabilize schedule ====
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/28/12
* RC2: 4/4/12
* RC3: 4/11/12
* RC4: 4/18/12
* RC5: 4/23/12
* M4 Release readiness meeting: 4/30/12
* Yocto Project 1.2 release: 4/30/12
== Yocto Project unscheduled features ==
Please feel free to pick up these features for development whenever you have time. We welcome and appreciate all developers' help from the community.
=== Feature List ===
Please see https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features#Unsorted
Yocto 1.2 Weekly Test Report

This page is to hold Weekly Test Report for Yocto 1.2.
====Yocto 1.2 20111023 Weekly Test Report====
This is the weekly test report for Yocto 1.2 2011023 build. There are 7 new bugs found in this build. All meta-intel BSP builds failed on autobuilder. avahi/connman could not work due to dbus file missing. X86-64 arm toolchain build failed on autobuilder.
Test Summary:
File:Yocto_1.2_20111023_Test_Result_Summary.JPG
Test detail Summary:
File:Yocto_1.2_20111023_Detail_Test_Result.JPG
* You can check the detailed test result in attachment for each target.
* The failed/blocked case number is listed with failed cases’ bug number.
Commit Information:
Tree/Branch: Poky/master_under_test
Poky Commit id: 88d7de9aa239bbb47245afc13d3a3e9689e9ebfb
Issue Summary:
File:Yocto_1.2_20111023_Issue_Summary_Result.JPG
====History Test Report====
Test Report for Yocto 1.2 20111015 build
Yocto 1.3 Features

== Potential Yocto Project 1.3 Features ==
Yocto Project 1.3 - Target release = Oct. 2012
== Yocto Project 1.3 Themes ==
The Yocto Project 1.3 Themes include:
# Continuity / Refresh: 
## The usual keeping up to date with various upstream project, continue to work on the quality of the metadata and keeping up to date with bug fixing.
# Stabilization & Adoption: 
## We've introduced a lot of changes. I think now may be a good time to catch our breath so to speak and ensure everything is complete, functional, well tested and has the right level of polish. 
## We also need to encourage adoption of the project by OSV and Silicon Vendors and look at ways we can advance and integrate Shoeleather-type board labs (from semis and OSVs).
# Usability: 
## Introduce WebHob? (We have been actively working on WebHOB in 1.3, but this one will have to wait until some later release.)
## Continue improving error messages
## Reserve time to jump on usability issues as they come up
== Areas to improve for 1.3 release ==
# SState improvements (file urls, overwriting files checks)
# Init system overhaul (optional systemd support?)
# Performance improvements (postinstall handling, rootfs generation speedups)
# Multilib bug fixes
# Complete multilib recipe enablement and automated sanity tests
# Bitbake test suite
# Build history web UI
# Autobuilder Improvements
# Package Reporting System
# More automated QA
# Smoother/Improved Hob experience (fully bugfixed)
# PR increments handled automatically
== Process for Entering New Feature Requests ==
* Open a bug in the Yocto bugzilla setting the type of bug to be an "enhancement" request. The detail about the request should be included in the bugzilla report.
* Create a new entry in the appropriate feature table below (Poky, SDK, Hardware)
** Suggestion: start by copying an existing request as a template
* Give the feature a short, descriptive name
* Set the priority as appropriate (see the legend below)
* Set the Status to "Review"
* In the Source field, enter your name along with the origination of the request (e.g. OSV, OEM, Community) if applicable; provide as much detail here as you can
* In the Comments / Bugzilla field, provide any additional information for the request includind a link to a bugzilla entry
* Preview your Entry to make sure it looks ok and then save it
Legend
Priority: 1 = Must have, 2 = Nice to have but wouldn't block a release, 3 = Lower priority, desired, defined plan, 4 = Worthwhile ideas, no defined plan
Status: Accept = Engineering agreement to include in release, New = Under Review for Inclusion in this release, Reject = Will not be included in this release
== All P1 features/bugs ==
== Cleanups/Improvements ==
===P1===
===P2===
===P3===
== Usability ==
===P1===
===P2===
===P3===
==Performance==
===P1===
===P2===
==Multilib==
===P1===
===P2===
===P3===
==Autobuilder==
===P1===
===P2===
==QA/Test==
==ADT/SDK/Eclipse==
===P1===
===P2===
===P3===
==Sato issues==
===P3/P4===
==LSB/POSIX/LTP==
===P2/P3===
==Hob v2==
==Web HOB==
==Kernel / BSP ==
Detailed Kernel Team bug queries are available on the Kernel page.
==Documentation==
Yocto 1.3 Schedule

= Yocto Project 1.3 release milestone structure = 
= Yocto Project 1.3 release schedule (release date: Oct. 26, 2012) =
----
The detailed milestone map for the 1.3 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 (May 14 to June 29, 2012 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M1 Feature/Tasks Development (May 14 to June 10, 2012) ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/13/12
* RC2: 6/21/12
* M1 Release readiness meeting: 6/28/12
* M1 release: 6/29/2012
== M2 (June 11, 2012 to July 27, 2012 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M2 Feature/tasks Development (June 11, 2012 to July 8, 2012) ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/11/12
* RC2: 7/19/12
* M2 Release readiness meeting:7/26/12
* M2 release: 7/27/12
== M3 (July 9 to Aug. 24, 2012 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development (July 9 to Aug. 5, 2012) ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 8/8/12
* RC2: 8/16/12
* M3 Release readiness meeting: 8/23/12
* M3 release: 8/24/12
== M4 (Aug. 6 to Sep. 21, 2012 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M4 Feature/tasks Development (Aug. 6 to Sep. 2, 2012) ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 9/5/12
* RC2: 9/13/12
* M3 Release readiness meeting: 9/20/12
* M3 release: 9/21/12
== M5 Stabilization Milestone (9/19/2012 - 10/26/2012) ==
===M5 Bugs===
===M5 Schedule===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 9/19/12
* RC2: 9/26/12
* RC3: 10/3/12
* RC4: 10/10/12
* RC5: 10/17/12
* M4 Release readiness meeting: 10/25/12
* Yocto Project 1.3 release: 10/26/12
== Yocto Project 1.3 release unscheduled features/tasks list==
These features/tasks are planned for 1.3, but have not been scheduled to any specific milestone. As we move forward, more of these will be scheduled into each milestone, especially during milestone planning for each milestone above.
Yocto 1.4 Features

== Yocto Project 1.4 Feature Planning ==
Yocto Project 1.4 release planning has been underway since early Sep. 2012. We are now inviting the community to enter new features and ideas about 1.4 release in our Bugzilla. Yocto Project 1.4 is targeted to release in April, 2013. Detailed schedule of the release will be published around the end of Oct. 2012.
== Yocto Project 1.4 Themes ==
* Usability
* Technology Leadership
* Performance
* Documentation
== Process for Entering New Feature Requests ==
We have been using the same Bugzilla where we manage bugs to manage all features. Features in Bugzilla should have their severity set to 'enhancement'. If you have a feature request or even an idea about something for 1.4 or future releases, please feel free to file an 'enhancement' feature in Bugzilla: 
* Set the severity of bug to be 'enhancement'. Please put as much detail as possible in the 'description' field and give it a concise and meaningful 'summary'. You can always add/edit as you have more thoughts and information about the feature. Others can also use the feature entry to ask questions or provide feedback.
* If you know which functional category the feature belongs to, please put the bug # in appropriate category such as usability, performance, kernel, core build system, etc.
* Set the priority you would like this to be or indicate this in the description field. We may adjust the priority when we have a better view of the whole release later on.
* Preview your Entry to make sure it looks ok and then save it
Note:
Priority: 
High = Must have for the target release 
Medium+ = Very important, needs special attention compared with other medium features 
Medium = Important 
Low = Nice to have, no defined plan 
== Functional Categories ==
Note: If you see bug #1 in any category, it's a place holder. Please feel free to remove it when you add more items.
=== Usability ===
===Performance===
===Technology===
===Autobuilder===
===ADT/SDK/Eclipse===
===Hob===
===Build Appliance===
===Kernel / BSP ===
=== Cleanups/Improvements ===
===QA/Test===
===Documentation===
==Unsorted Features (by priority)==
=== High ===
=== Medium+ ===
=== Medium ===
=== Low ===
=== Future ===
Yocto 1.4 Schedule

= Yocto Project 1.4 release milestone structure = 
= Yocto Project 1.4 release schedule (release date: Apr. 26, 2013) =
----
The detailed milestone map for the 1.4 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. 29 to Dec. 14, 2012 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M1 Feature/Tasks Development (Oct. 29 to Dec. 14, 2012) ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 11/28/12
* RC2: 12/5/12
* M1 release: 12/14/2012
== M2 (Nov. 26, 2012 to Jan. 11, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M2 Feature/tasks Development (Nov. 26, 2012 to Jan. 11, 2013) ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 12/26/12
* RC2: 1/2/13
* M2 release: 1/11/13
== M3 (Dec. 24 to Feb. 8, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development (Dec. 24 to Feb. 8, 2013) ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/23/12
* RC2: 1/30/12
* M3 release: 2/8/12
== M4 (Jan. 21 to Mar. 8, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M4 Feature/tasks Development (Jan. 21 to Mar. 8, 2013) ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/20/13
* RC2: 2/27/13
* M4 release: 3/8/13
== M5 (Feb. 18 to Apr. 5, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M5 Feature/tasks Development (Feb. 18 to Apr. 5, 2013) ===
=== M5 Bugs ===
=== M5 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/20/13
* RC2: 3/27/13
* M5 release: 4/5/13
== Feature Complete: March 17, 2013 ==
== M6 Stabilization Milestone (3/18/2013 - 4/26/2013) ==
===M6 Schedule===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/20/13
* RC2: 3/27/13
* RC3: 4/3/13
* RC4: 4/10/13
* RC5: 4/17/13
* Yocto Project 1.4 release: 4/26/13
===M6 Bugs===
== Yocto Project 1.4 release unscheduled features/tasks list==
These features/tasks are planned for 1.3, but have not been scheduled to any specific milestone. As we move forward, more of these will be scheduled into each milestone, especially during milestone planning for each milestone above.
Yocto 1.5 Features

== Yocto Project 1.5 Feature Planning ==
Yocto Project 1.5 release planning has been underway since March 2013. We are now inviting the community to enter new features and ideas about 1.5 release in our Bugzilla. Yocto Project 1.5 is targeted to release in Oct., 2013. Detailed schedule of the release will be published around the end of April, 2013.
== Yocto Project 1.5 Themes ==
* Developer experience 
 - Webhob 0.9
 - ADT support for Windows/MacOS environments
 - Bitbake commandline rethink/restructure
* Validation automation
 - Automatic ptest support as part of qemu tests
 - Extension of the qemut test to cover many currently manual QA test
 - Much more extensive tests of postinst/multilib
* Performance
 - Continued performance benchmark tracking
 - Extension of current benchmarks
 - Removal of pseudo-native wrapper script special case
== Process for Entering New Feature Requests ==
We have been using the same Bugzilla where we manage bugs to manage all features. Features in Bugzilla should have their severity set to 'enhancement'. If you have a feature request or even an idea about something for 1.5 or future releases, please feel free to file an 'enhancement' feature in Bugzilla: 
* Set the severity of bug to be 'enhancement'. Please put as much detail as possible in the 'description' field and give it a concise and meaningful 'summary'. You can always add/edit as you have more thoughts and information about the feature. Others can also use the feature entry to ask questions or provide feedback.
* If you know which functional category the feature belongs to, please put the bug # in appropriate category such as usability, performance, kernel, core build system, etc.
* Set the priority you would like this to be or indicate this in the description field. We may adjust the priority when we have a better view of the whole release later on.
* Preview your Entry to make sure it looks ok and then save it
Note:
Priority: 
High = Must have for the target release 
Medium+ = Very important, needs special attention compared with other medium features 
Medium = Important 
Low = Nice to have, no defined plan 
==Unsorted Features (by priority)==
=== High ===
=== Medium+ ===
=== Medium ===
=== Low ===
=== Undecided ===
== Future ==
Yocto 1.5 Schedule

= Yocto Project 1.5 release milestone structure = 
= Yocto Project 1.5 release schedule (release date: Oct. 18, 2013) =
----
The detailed milestone map for the 1.5 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 (May 6 to June 21, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M1 Feature/Tasks Development (May 6 to June 2, 2013) ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/5/13
* RC2: 6/12/13
* M1 release: 6/21/13
== M2 (June 3, 2013 to July 19, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M2 Feature/tasks Development (June 3, 2013 to June 30, 2013) ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/3/13
* RC2: 7/10/13
* M2 release: 7/19/13
== M3 (July 1 to Aug. 16, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development (July 1 to July 28, 2013) ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/31/13
* RC2: 8/7/12
* M3 release: 8/16/12
== M4 (July 29 to Sep. 13, 2013 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M4 Feature/tasks Development (July 29 to Aug.25, 2013) ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 8/28/13
* RC2: 9/4/13
* M4 release: 9/13/13
== M5 (Aug. 26 to Oct. 18, 2013 -- Stabilization miletsone (8 weeks) ==
=== M5 Feature/tasks Development ===
=== M5 Bugs ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 9/11/13
* RC2: 9/18/13
* RC3: 9/25/13
* RC4: 10/2/13
* RC5: 10/9/13
* Yocto Project 1.5 release: 10/18/13
== Yocto Project 1.5 release unscheduled features/tasks list==
These features/tasks are planned for 1.5, but have not been scheduled to any specific milestone. As we move forward, more of these will be scheduled into each milestone, especially during milestone planning for each milestone above.