Yocto 2.1 Features - Revision history

Stephen K. Jolley: /* Yocto Project 2.1 Themes */

2016-04-14T22:04:27Z

Yocto Project 2.1 Themes

← Older revision		Revision as of 22:04, 14 April 2016
Line 7:		Line 7:
	* Enhancement of eSDK to replace the adt-installer driven approach and supporting infrastructure		* Enhancement of eSDK to replace the adt-installer driven approach and supporting infrastructure
	* Focus on developer driven workflows through tools like recipetool and devtool		* Focus on developer driven workflows through tools like recipetool and devtool
	* Toaster image ~~customisation~~ support		* Toaster image customization support
	* Tooling/workflow improvements (automatic upgrades/upgrade status/error reporting/patchwork)		* Tooling/workflow improvements (automatic upgrades/upgrade status/error reporting/patchwork)
	* Improved ~~autoamted~~ test coverage and accuracy		* Improved automated test coverage and accuracy

	== Process for Entering New Feature Requests ==		== Process for Entering New Feature Requests ==

Rpurdie: /* Yocto Project 2.1 Themes */

2016-03-18T15:27:20Z

Yocto Project 2.1 Themes

← Older revision		Revision as of 15:27, 18 March 2016
Line 4:		Line 4:

	== Yocto Project 2.1 Themes ==		== Yocto Project 2.1 Themes ==
	~~TBD~~
			* 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 customisation support
			* Tooling/workflow improvements (automatic upgrades/upgrade status/error reporting/patchwork)
			* Improved autoamted test coverage and accuracy

	== Process for Entering New Feature Requests ==		== Process for Entering New Feature Requests ==

Stephen K. Jolley: /* 2.2, Future */

2015-10-12T21:57:44Z

2.2, Future

← Older revision		Revision as of 21:57, 12 October 2015
Line 89:		Line 89:
	\|severity=enhancement		\|severity=enhancement
	\|noresultsmessage="None"		\|noresultsmessage="None"
	\|milestone=1.9, 2.0,Future		\|milestone=2.2,Future
	\|sort=to		\|sort=to
	\|total=estimated		\|total=estimated
	\|status=!(resolved, verified, closed)		\|status=!(resolved, verified, closed)
	}}		}}

Stephen K. Jolley: Created page with "== 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 track..."

2015-10-12T21:57:15Z

Created page with "== 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 track..."

New page

== 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 ==
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.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 ===
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|priority=high
|severity=enhancement
|noresultsmessage="None"
|milestone=2.1, 2.1 M1, 2.1 M2, 2.1 M3, 2.1 M4
|sort=to
|total=estimated
|resolution=!DUPLICATE
}}

=== Medium+ ===
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|priority=Medium%2B
|severity=enhancement
|noresultsmessage="None"
|milestone=2.1, 2.1 M1, 2.1 M2, 2.1 M3, 2.1 M4
|sort=to
|total=estimated
|resolution=!DUPLICATE
}}

=== Medium ===
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|priority=medium
|severity=enhancement
|noresultsmessage="None"
|milestone=2.1, 2.1 M1, 2.1 M2, 2.1 M3, 2.1 M4
|sort=to
|total=estimated
|resolution=!DUPLICATE
}}

=== Low ===
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|priority=low
|severity=enhancement
|noresultsmessage="None"
|milestone=2.1, 2.1 M1, 2.1 M2, 2.1 M3, 2.1 M4
|sort=to
|total=estimated
|resolution=!DUPLICATE
}}

=== Undecided ===
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|priority=undecided
|severity=enhancement
|noresultsmessage="None"
|milestone=2.1, 2.1 M1, 2.1 M2, 2.1 M3, 2.1 M4
|sort=to
|total=estimated
}}

== 2.2, Future ==
{{#bugzilla:
|columns=id,to,summary,estimated,milestone,from,status,severity,priority,whiteboard
|severity=enhancement
|noresultsmessage="None"
|milestone=1.9, 2.0,Future
|sort=to
|total=estimated
|status=!(resolved, verified, closed)
}}