nyuuzyou/wikis huggingface dataset:
Yocto 2.1 Schedule

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

== Yocto Project 2.2 Feature Planning ==
Yocto Project 2.2 release planning has been underway since April, 2016. Most all new features and ideas about 2.2 release are tracked as enhancements in Bugzilla. Yocto Project 2.2 is targeted to release in Oct., 2016. Detailed schedule is at this link: Yocto 2.2 Schedule
== Yocto Project 2.2 Themes ==
* Need to switch to Python 3.x
* Move to do multiple configurations to allow multiple builds which allows for multiple machines and possibly distributed builds. 
* Need to better integrate patchwork, swupd, and error reporting system for a better process.
* Need to better integrate and get user adoption of Toaster, eSDK, and CROPS.
== 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.2 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.3, Future ==
Yocto 2.2 Schedule

= Yocto Project 2.2 release milestone structure = 
= Yocto Project 2.2 release schedule (release date: Oct. 28, 2016) =
----
The detailed milestone map for the 2.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 (May 2, 2016 to 6/24/16-- 8 weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release week 8) ==
=== M1 Feature/Tasks Development / Cutoff is 6/13/2016 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/13/16
* RC2: 6/20/16
* M1 release: 6/24/16
== M2 (6/13/16 to 7/29/16 -- 7 weeks: planning done in week 1, development week 2-4, stabilization week 5-6, release: week 7) ==
=== M2 Feature/tasks Development / Cutoff is 7/18/16 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/18/16
* RC2: 7/25/16
* M2 release: 7/29/16
== M3 (7/18/16 to 9/9/16 -- 8 weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release: week 8) ==
=== M3 Feature/tasks Development / Cutoff is 8/29/16 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 8/29/16
* RC2: 9/2/16
* M3 release: 9/19/16
== M4 (8/29/16 to Oct. 28, 2016 -- 9 weeks: planning done in week 1, bug fixes 2-4, stabilization week 5-8, release week 9) ==
=== M4 Bug/fix Cutoff is 10/3/16 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 10/3/16
* RC2: 10/10/16
* RC3: 10/17/16
* RC4: 10/24/16
* M4 release: 10/29/16
== Yocto Project 2.2 release unscheduled features/tasks list==
These features/tasks are planned for 2.2, 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.3 Features

== Yocto Project 2.3 Feature Planning ==
Yocto Project 2.3 release planning has been underway since Oct., 2016. Most all new features and ideas about 2.3 release are tracked as enhancements in Bugzilla. Yocto Project 2.3 is targeted to release in April 28, 2017. Detailed schedule is at this link: Yocto 2.3 Schedule
== Yocto Project 2.3 Themes ==
* Process/Tooling/Workflow Improvements	(Patchwork, Patchtest, SWAT, Error reporting)
* Improving Testing/QA Automation/Coverage Efficiency	(TRT)
* Creating Leading edge Build Technology (Reproducibility, sharing binaries, git recipe versions)
* Enhancing IoT Application Development	(CROPS, eSDK, devtool)
== 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.3 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.4, Future ==
Yocto 2.3 Schedule

= Yocto Project 2.3 release milestone structure = 
= =
= Yocto Project 2.3 release schedule (release date: April 28, 2017) =
----
The detailed milestone map for the 2.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 (Oct. 31, 2016 to Dec. 23, 2016 -- 9 weeks: planning done in week 1, development week 2-6, stabilization week 7-8, release week 9) ==
=== M1 Feature/Tasks Development / Cutoff is Dec. 12, 2016 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 12/12/16
* M1 release: 12/23/16
== M2 (Dec. 12, 2016 to Feb. 3, 2017 -- 9 weeks: planning done in week 1, development week 2-6, stabilization week 7-8, release: week 9) ==
=== M2 Feature/tasks Development / Cutoff is Jan. 23, 2017 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/23/17
* M2 release: 2/3/17
== M3 (Jan. 23, 2017 to Mar. 10, 2017 -- 8 weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release: week 8) ==
=== M3 Feature/tasks Development / Cutoff is Feb. 27, 2017 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/27/17
* M3 release: 3/10/17
== M4 (Feb. 27, 2017 to May 5, 2017 -- 9 weeks: planning done in week 1, bug fixes 2-5, stabilization week 6-8, release week 9) ==
=== M4 Bug/fix Cutoff is April 10, 2017 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 4/10/17
* RC2: 4/17/17
* RC3: 4/24/17
* M4 release: 5/5/17
== Yocto Project 2.3 release unscheduled features/tasks list==
These features/tasks are planned for 2.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 2.4 Features

== Yocto Project 2.4 Feature Planning ==
Yocto Project 2.4 release planning has been underway since April, 2017. Most all new features and ideas about 2.4 release are tracked as enhancements in Bugzilla. Yocto Project 2.4 is targeted to release in Oct. 20, 2017. Detailed schedule is at this link: Yocto 2.4 Schedule
== Yocto Project 2.4 Themes ==
* Process/Tooling/Workflow Improvements	- Patchwork, Patchtest, SWAT, Error reporting
* Improving Testing/QA Automation/Coverage Efficiency - oeselftest, Test automation, CI/AB - modernization and moving more into YP
* Creating Leading edge Build Technology - Layer setup tool, Delivering prebuilt binaries to customers, Improve Binary/Build Reproducibility
* Enhancing IoT Application Development - CROPS (eclipse support, dev containers), eSDK (team workflow), devtool (team workflow, extend heuristics), juci from openWRT support
== 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.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 
==Unsorted Features (by priority)==
=== High ===
=== Medium+ ===
=== Medium ===
=== Low ===
=== Undecided ===
== 2.5, Future ==
Yocto 2.4 Schedule

= Yocto Project 2.4 release milestone structure = 
=
= Yocto Project 2.4 release schedule (release date: Oct. 20, 2017) =
----
The detailed milestone map for the 2.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 (May 8, 2017 to Jun. 23, 2017 ==
=== M1 Feature/Tasks Development / Cutoff is Jun. 12, 2017 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/12/17
* M1 release: 6/23/17
== M2 (Jun. 12, 2017 to Jul. 28, 2017 ==
=== M2 Feature/tasks Development / Cutoff is July 17, 2017 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/17/17
* M2 release: 7/28/17
== M3 (Jul. 17, 2017 to Sept. 1, 2017 ==
=== M3 Feature/tasks Development / Cutoff is Aug. 21, 2017 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 8/21/17
* M3 release: 9/1/17
== M4 (Aug. 21, 2017 to Oct. 20, 2017 ==
=== M4 Bug/fix Cutoff is Sept. 18, 2017 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 9/18/17
* RC2: 9/25/17
* RC3: 10/1/17
* RC4: 10/8/17
* M4 release: 10/20/17
== Yocto Project 2.4 release unscheduled features/tasks list==
These features/tasks are planned for 2.4, 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.5 Features

== Yocto Project 2.5 Feature Planning ==
Yocto Project 2.5 release planning has been underway since April, 2017. Most all new features and ideas about 2.5 release are tracked as enhancements in Bugzilla. Yocto Project 2.5 is targeted to release in Oct. 20, 2017. Detailed schedule is at this link: Yocto 2.5 Schedule
== Yocto Project 2.5 Themes ==
* Process/Tooling/Workflow Improvements - Allow YP to better scale as it grows, improve efficiency.
* Improving Testing/QA Automation/Coverage - Uncover testing gaps, streamline testing results.
* Creating Leading edge Build Technology - Improve YP and met customer requests.
* Binary/Build Reproducibility - Documentation of what exists and add enhancements as needed.	
* Enhancing IoT Application Development	- Support IoT Application Developers.
== 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.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 ===
== 2.6, Future ==
Yocto 2.5 Schedule

= Yocto Project 2.5 release milestone structure = 
=
= Yocto Project 2.5 release schedule (release date: Apr. 27, 2018) =
----
The detailed milestone map for the 2.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 (Oct. 23, 2017 to Dec. 15, 2017 ==
=== M1 Feature/Tasks Development / Cutoff is Dec. 4, 2017 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 12/4/17
* M1 release: 12/15/17
== M2 (Dec. 5, 2017 to Jan. 26, 2018 ==
=== M2 Feature/tasks Development / Cutoff is Jan. 15, 2018 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 1/15/18
* M2 release: 1/26/18
== M3 (Jan. 16, 2018 to Mar. 2, 2018 ==
=== M3 Feature/tasks Development / Cutoff is Feb. 19, 2018 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 2/19/18
* M3 release: 3/2/18
== M4 (Feb. 20, 2018 to Apr. 27, 2018 ==
=== M4 Bug/fix Cutoff is Apr. 2, 2018 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 4/2/18
* RC2: 4/9/18
* RC3: 4/16/18
* Final M4 release: 4/27/18
== Yocto Project 2.5 release unscheduled features/tasks list==
These features/tasks are planned for 2.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.
Yocto 2.6 Features

== Yocto Project 2.6 Feature Planning ==
Yocto Project 2.6 release planning has been underway since April, 2017. Most all new features and ideas about 2.6 release are tracked as enhancements in Bugzilla. Yocto Project 2.6 is targeted to release in Oct. 20, 2017. Detailed schedule is at this link: Yocto 2.6 Schedule
== Yocto Project 2.6 Themes ==
* Still TBD
== 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.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 ===
== 2.7, 2.99, Future ==
Yocto 2.6 Schedule

= Yocto Project 2.6 release milestone structure = 
=
= Yocto Project 2.6 release schedule (release date: Oct. 26, 2018) =
----
The detailed milestone map for the 2.6 release of Yocto Project is as below. 
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 (Apr. 30, 2018 to June 22, 2018 ==
=== M1 Feature/Tasks Development / Cutoff is June 11, 2018 ===
=== M1 Bugs ===
=== M1 Stabilize schedule ===
Release Candidate and Milestone Release schedule
* RC1: 6/11/18
* M1 release: 6/22/18
== M2 (June 12, 2018 to July 27, 2018 ==
=== M2 Feature/tasks Development / Cutoff is July 16, 2018 ===
=== M2 Bugs ===
=== M2 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 7/16/18
* M2 release: 7/27/18
== M3 (July 17, 2018 to Sept. 7, 2018 ==
=== M3 Feature/tasks Development / Cutoff is Aug. 27, 2018 ===
=== M3 Bugs ===
=== M3 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 8/27/18
* M3 release: 9/7/18
== M4 (Aug. 28, 2018 to Oct. 26, 2018 ==
=== M4 Bug/fix Cutoff is Oct. 1, 2018 ===
=== M4 Bugs ===
=== M4 Stabilize schedule ===
Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)
* RC1: 10/1/18
* RC2: 10/8/18
* RC3: 10/15/18
* Final M4 release: 10/26/18
== Yocto Project 2.6 release unscheduled features/tasks list==
These features/tasks are planned for 2.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.