Yocto 3 1 Features - Revision history

Armin Kuster: /* Yocto Project 3.1 Feature Planning */

2019-10-30T08:16:30Z

Yocto Project 3.1 Feature Planning

← Older revision		Revision as of 08:16, 30 October 2019
Line 1:		Line 1:
	== Yocto Project 3.1 Feature Planning ==		== Yocto Project 3.1 Feature Planning ==

	Yocto Project 3.1 release planning has been underway since May, 2019. Most all new features and ideas about 2.8 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in Oct. 2019. Detailed schedule is at this link: [[Yocto 2.8 Schedule]]		Yocto Project 3.1 release planning has been underway since May, 2019. Most all new features and ideas about 2.8 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in Oct. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]


	== Yocto Project 3.1 Themes ==		== Yocto Project 3.1 Themes ==

Armin Kuster at 08:15, 30 October 2019

2019-10-30T08:15:55Z

← Older revision	Revision as of 08:15, 30 October 2019
Line 1:	Line 1:
		== Yocto Project 3.1 Feature Planning ==

		Yocto Project 3.1 release planning has been underway since May, 2019. Most all new features and ideas about 2.8 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in Oct. 2019. Detailed schedule is at this link: [[Yocto 2.8 Schedule]]


		== Yocto Project 3.1 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 3.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:''' <br/>
		High = Must have for the target release <br/>
		Medium+ = Very important, needs special attention compared with other medium features <br/>
		Medium = Important <br/>
		Low = Nice to have, no defined plan <br/>


		==Unsorted Features (by priority)==

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

Armin Kuster: /* Yocto Project 3.1 Feature Planning */

2019-10-30T08:14:04Z

Yocto Project 3.1 Feature Planning

← Older revision		Revision as of 08:14, 30 October 2019
Line 1:		Line 1:
	~~== Yocto Project 3.1 Feature Planning ==~~

	Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]

Armin Kuster: /* Process for Entering New Feature Requests */

2019-10-30T08:13:47Z

Process for Entering New Feature Requests

← Older revision		Revision as of 08:13, 30 October 2019
Line 2:		Line 2:

	Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]		Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]


	~~== 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 3.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:''' <br/>~~
	~~High = Must have for the target release <br/>~~
	~~Medium+ = Very important, needs special attention compared with other medium features <br/>~~
	~~Medium = Important <br/>~~
	~~Low = Nice to have, no defined plan <br/>~~

Armin Kuster: /* Yocto Project 3.1 Feature Planning */

2019-10-30T08:12:55Z

Yocto Project 3.1 Feature Planning

← Older revision		Revision as of 08:12, 30 October 2019
Line 2:		Line 2:

	Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]		Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]


			== 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 3.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:''' <br/>
			High = Must have for the target release <br/>
			Medium+ = Very important, needs special attention compared with other medium features <br/>
			Medium = Important <br/>
			Low = Nice to have, no defined plan <br/>

Armin Kuster: Created page with "== Yocto Project 3.1 Feature Planning == Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked a..."

2019-10-30T08:12:12Z

Created page with "== Yocto Project 3.1 Feature Planning == Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked a..."

New page

== Yocto Project 3.1 Feature Planning ==

Yocto Project 3.1 release planning has been underway since Oct, 2019. Most all new features and ideas about 3.1 release are tracked as enhancements in Bugzilla. Yocto Project 3.1 is targeted to release in April. 2019. Detailed schedule is at this link: [[Yocto 3.1 Schedule]]