nyuuzyou/wikis huggingface dataset:
Yocto 1.5 rc1 meta-intel

=Testing data=
 
 Test type: Full Pass on meta-intel
 Branch: dora
 Milestone: meta-intel 1.5 rc1
 Build name: meta-intel 1.5 rc1
 poky commit: faf8f8660fae26a14578738b642fdeb08bcb9d54
 meta-intel commit: bf3b0601fa45b98ad33a2e4fd048f3616f50d8da
 HW tested: Crownbay-noemgd, eMenlow, Fish River Island 2(FRI2), Jasperforest, n450 on AtomPC, NUC (Next Unit Computing), Sugarbay 
=Summary Report=
	
=Detailed Report=
Yocto 1.6 Features

== Yocto Project 1.6 Feature Planning ==
Yocto Project 1.6 release planning has been underway since Oct. 2013. We are now inviting the community to enter new features and ideas about 1.6 release in our Bugzilla. Yocto Project 1.6 is targeted to release in April, 2014. Detailed schedule of the release will be published around mid-Nov., 2013.
== Yocto Project 1.6 Themes ==
* Enhanced Testing and test automation
 - OE-Selftest
 - Automated Hardware testing
 - ptest integration
 - migration of Sato into hardware test interface
* Developer Experience Improvements
 - Continued development of Webhob including integrating into the core
 - Autobuilder Enhancements (extended coverage, usability improvements, performance improvements)
 - Commandline Bitbake improvements
== 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.6 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.6 Schedule

= Yocto Project 1.6 release milestone structure = 
= Yocto Project 1.6 release schedule (release date: Apr. 25, 2014) =
----
The detailed milestone map for the 1.6 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 (Nov. 11 to Dec. 20, 2013 -- 6 weeks: planning done in week 1, development week 1-3, stabilization week 4-5, release week 6) ==
=== M1 Feature/Tasks Development ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 12/4/13
* RC2: 12/11/13
* M1 release: 12/20/13
== M2 (Dec. 9, 2013 to Jan. 31, 2014 -- 8 weeks: planning done in week 1, development week 1-5, stabilization week 6-8, release: week 8) ==
=== M2 Feature/tasks Development ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/15/14
* RC2: 1/22/14
* M2 release: 1/31/14
== M3 (Jan. 13 to Feb. 28, 2014 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/12/14
* RC2: 2/19/14
* M3 release: 2/28/14
== M4 (Feb. 10 to March 28, 2014 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M4 Feature/tasks Development ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/12/14
* RC2: 3/19/14
* M4 release: 3/28/14
== M5 (March. 24 to April 25, 2014 -- Stabilization miletsone (5 weeks) ==
=== M5 Feature/tasks Development ===
=== M5 Bugs ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/26/14
* RC2: 4/2/14
* RC3: 4/9/14
* RC4: 4/16/14
* Yocto Project 1.6 release: 4/25/14
== Yocto Project 1.6 release unscheduled features/tasks list==
These features/tasks are planned for 1.6, 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.6 meta-intel testing plan

= Objectives =
The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs.
=Test Areas =
The meta-intel testing is being part of the Target System test are within Yocto 1.6 Overall Testing Plan.
The test cases that we run are available on Testopia. There, you can browse to the BSPs component, select the “master branch” testing plan and then access the “Test Cases” panel to view all the test cases available. They are used for testing QEMU, core BSPs and meta-intel BSPs. 
To organize them, we divided them into test runs templates (check the “Test runs” panel and filter by TEMPLATE) and then create new test runs based on them for each build that we need.
As a reminder, the Testopia wiki have all the information needed for working with Testopia.
The target machines tested are: 
* emenlow
* crownbay
* minnowboard
* fri2
* nuc
* jasperforest
* sugarbay
* crystalforest
= Test Cycle =
The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the Yocto 1.6 Schedule. meta-intel BSPs are not covered in the weekly testing.
Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the Yocto Overall 1.6 Test Plan. In the Meta-intel Release Process is detailed the release process of meta-intel.
= Test Automation =
The plan for 1.6 HW automation is detailed in the HW automation bug 1596.
Yocto 1.7 Features

== Yocto Project 1.7 Feature Planning ==
Yocto Project 1.7 release planning has been underway since March, 2014. Most all new features and ideas about 1.7 release are tracked as enhancements in Bugzilla. Yocto Project 1.7 is targeted to release in October, 2014. Detailed schedule is at this link: Yocto 1.7 Schedule
== Yocto Project 1.7 Themes ==
* Developer Experience and Workflows with the Project
* Automation (ptest, hardware, package upgrade)
* Performance
== 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.7 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 ===
== 1.8, 2.0, Future ==
Yocto 1.7 Schedule

= Yocto Project 1.7 release milestone structure = 
= Yocto Project 1.7 release schedule (release date: Oct. 31, 2014) =
----
The detailed milestone map for the 1.7 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 19, 2014 to July 11, 2014 -- 8 weeks: planning done in week 1, development week 2-4, stabilization week 5-8, release week 8) ==
=== M1 Feature/Tasks Development / Cutoff is June 20, 2014===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/25/14
* RC2: 7/2/14
* M1 release: 7/11/14
== M2 (June 30, 2014 to August 15, 2014 -- 7 weeks: planning done in week 1, development week 2-4, stabilization week 5-7, release: week 7) ==
=== M2 Feature/tasks Development / Cutoff is July 25, 2014 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/30/14
* RC2: 8/6/14
* M2 release: 8/15/14
== M3 (August 4, 2014 to Sept. 19, 2014 -- 7 weeks: planning done in week 1, development week 2-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development / Cutoff is August 29, 2014 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 9/3/14
* RC2: 9/10/14
* M3 release: 9/19/14
== M4 (Sept. 8, 2014 to Oct. 31, 2014 -- 8 weeks: planning done in week 1, development week 2-3, stabilization week 4-8, release week 8) ==
=== M4 Feature/tasks Development / Cutoff is Sept. 26, 2014 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 10/1/14
* RC2: 10/8/14
* RC3: 10/15/14
* RC4: 10/22/14
* M4 release: 10/31/14
== Yocto Project 1.7 release unscheduled features/tasks list==
These features/tasks are planned for 1.7, 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.8 Features

== Yocto Project 1.8 Feature Planning ==
Yocto Project 1.8 release planning has been underway since October, 2014. Most all new features and ideas about 1.8 release are tracked as enhancements in Bugzilla. Yocto Project 1.8 is targeted to release in April, 2015. Detailed schedule is at this link: Yocto 1.8 Schedule
== Yocto Project 1.8 Themes ==
Developer Workflow
Toaster enhancements
Autobuilder improvements
Kernel build process
Building using other OS’s (Windows/MAC) with Yocto
Bare Metal Tool Chain
ARM 64 Support
Live log watching in Bitbake
Package reporting system
Error reporting system
oe Layer index (repackage list and make it public)
Machine set up tools 
Testing suite for WIC
Yocto BSP Testing (as automated as possible)
Binary comparison tool for package output
Meta Translator
== 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.8 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 ===
== 1.9, 2.0, Future ==
Yocto 1.8 Schedule

= Yocto Project 1.8 release milestone structure = 
= Yocto Project 1.8 release schedule (release date: April 24, 2015) =
----
The detailed milestone map for the 1.8 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 (Nov. 3, 2014 to Dec. 19, 2014 -- 7 weeks: planning done in week 1, development week 2-4, stabilization week 5-7, release week 7) ==
=== M1 Feature/Tasks Development / Cutoff is 12/2/14===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 12/3/14
* RC2: 12/10/14
* M1 release: 12/19/14
== M2 (Dec. 3, 2014 to Jan. 30, 2015 -- 8 weeks: planning done in week 1, development week 2-5, stabilization week 6-8, release: week 8) ==
=== M2 Feature/tasks Development / Cutoff is 1/13/15 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/14/15
* RC2: 1/21/15
* M2 release: 1/30/15
== M3 (Jan. 14, 2015 to March 6, 2015 -- 7 weeks: planning done in week 1, development week 2-4, stabilization week 5-7, release: week 7) ==
=== M3 Feature/tasks Development / Cutoff is 2/18/15 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/19/15
* RC2: 2/26/15
* M3 release: 3/6/15
== M4 (Feb. 19, 2015 to April 24, 2015 -- 9 weeks: planning done in week 1, development week 2-4, stabilization week 5-9, release week 9) ==
=== M4 Bug/fix Cutoff is 3/24/15 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 3/25/15
* RC2: 4/1/15
* RC3: 4/8/15
* RC4: 4/15/15
* M4 release: 4/24/15
== Yocto Project 1.8 release unscheduled features/tasks list==
These features/tasks are planned for 1.8, 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.9 Features

== Yocto Project 1.9 Feature Planning ==
Yocto Project 1.9 release planning has been underway since March, 2015. Most all new features and ideas about 1.9 release are tracked as enhancements in Bugzilla. Yocto Project 1.9 is targeted to release in October, 2015. Detailed schedule is at this link: Yocto 1.9 Schedule
Yocto Project 1.9 will be released as Yocto Project 2.0
== Yocto Project 1.9 / 2.0 Themes ==
Major focus areas for YP 1.9 / 2.0 include overall UX improvements, support for distro and binary package deployment and early customization. Key features will include an IOT-driven developer flow, cross-development support using Windows/Mac, Toaster and Eclipse plug-in enhancements, and error reporting systems improvements.
Specific target areas are:
* Developer Workflow/Overall UX Improvements
* Development support using other OS’s (Windows/MAC) with Yocto
* Error reporting system improvements
* Distro Recipe Upgrades
* Toaster enhancements
* Eclipse plug-in enhancements 
* Deployment Improvements
* Autobuilder Enhancements
* Meta-intel Improvements
== 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.9 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 ===
== 2.1, Future ==
Yocto 1.9 Schedule

= Yocto Project 1.9/2.0 release milestone structure = 
= Yocto Project 1.9/2.0 release schedule (release date: October 30, 2015) =
----
The detailed milestone map for the 1.9 (and 2.0) 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 (April 27, 2015 to July 10, 2015 -- 11 weeks: planning done in week 1-3, development week 1-8, stabilization week 9-11, release week 11) ==
=== M1 Feature/Tasks Development / Cutoff is June 23, 2015 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: June 24, 2015
* RC2: July 1, 2015
* M1 release: Jul 10, 2015
== M2 (June 22, 2015 to Aug. 14, 2015 -- 8 weeks: planning done in week 1, development week 1-5, stabilization week 6-8, release week 8) ==
=== M2 Feature/tasks Development / Cutoff is July 27, 2015 noon GMT ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: July 29, 2015
* RC2: Aug. 5, 2015
* M2 release: Aug. 14, 2015
== M3 (Jul. 27, 2015 to Sept. 11, 2015 -- 7 weeks: planning done in week 1, development week 1-4, stabilization week 5-7, release week 7) ==
=== M3 Feature/tasks Development / Cutoff is Aug. 24, 2015 noon GMT ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: Aug. 26, 2015
* RC2: Sept. 1, 2015
* M3 release: Sept. 11, 2015
== 2.0 (Aug. 24, 2015 to Oct. 30, 2015 -- 10 weeks: planning done in week 1, stabilization week 1-10, release week 10) ==
=== 2.0 Feature/tasks Development / Cutoff is Sept. 28, 2015 noon GMT ===
=== 2.0 Bugs ===
=== 2.0 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 09/30/15
* RC2: 10/07/15
* RC3: 10/14/15
* RC4: 10/21/15
* 2.0 release: 10/30/15
== Yocto Project 1.9/2.0 release unscheduled features/tasks list==
These features/tasks are planned for 1.9/2.0, 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 2.1 Features

== Yocto Project 2.1 Feature Planning ==
Yocto Project 2.1 release planning has been underway since October, 2014. Most all new features and ideas about 2.1 release are tracked as enhancements in Bugzilla. Yocto Project 2.1 is targeted to release in April, 2015. Detailed schedule is at this link: Yocto 2.1 Schedule
== Yocto Project 2.1 Themes ==
* Enhancement of eSDK to replace the adt-installer driven approach and supporting infrastructure
* Focus on developer driven workflows through tools like recipetool and devtool
* Toaster image customization support
* Tooling/workflow improvements (automatic upgrades/upgrade status/error reporting/patchwork)
* Improved automated test coverage and accuracy
== 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 2.1 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 ===
== 2.2, Future ==