Yocto 3 1 Features: Difference between revisions
Armin Kuster (talk | contribs) (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...") |
Armin Kuster (talk | contribs) |
||
(4 intermediate revisions by the same user not shown) | |||
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 | 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 == | |||
* 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 | |||
}} |
Latest revision as of 08:16, 30 October 2019
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 3.1 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:
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
ID | Assignee | Summary | E | Milestone | Requester | Status | Severity | P | Whiteboard |
---|---|---|---|---|---|---|---|---|---|
13549 | Ross Burton | Get rid of python2 runtime dependencies for all recipes in oe-core | 3.1 M2 | Chen Qi | RESOLVED | enhancement | High | ||
0 |
Medium+
ID | Assignee | Summary (4 tasks) ⇒ | E | Milestone | Requester | Status | Severity | P | Whiteboard |
---|---|---|---|---|---|---|---|---|---|
11291 | Anuj Mittal | Don't generate live images for x86 | 1 | 3.1 M1 | Ross Burton | RESOLVED | enhancement | Medium+ | |
13736 | Kai Kang | Add automated runtime test for ifupdown | 3.1 M3 | Randy MacLeod | RESOLVED | enhancement | Medium+ | ||
12908 | Paul Knopf | Dead lock with multiple threads, one doing fopen64, other doing close on handles. | 3.1 M1 | Paul Knopf | RESOLVED | enhancement | Medium+ | ||
13830 | Tim Orling | Add buildtools-extended-tarball documentation | 3.1 M4 | Tim Orling | RESOLVED | enhancement | Medium+ | ||
1 |
Medium
ID | Assignee | Summary (3 tasks) ⇒ | E | Milestone | Requester | Status | Severity | P | Whiteboard |
---|---|---|---|---|---|---|---|---|---|
13739 | Alejandro | Enable OE runtime testing infrastructure for non-Linux systems | 4 | 3.1 | Alejandro | RESOLVED | enhancement | Medium | |
13720 | Alexander Kanavin | Should look at COMPATIBLE_HOST when picking machine | 3.1 | Ross Burton | RESOLVED | enhancement | Medium | ||
13630 | Richard Purdie | core-image-full-cmdline uses less from busybox | 3.1 | RESOLVED | enhancement | Medium | |||
4 |
Low
ID | Assignee | Summary | E | Milestone | Requester | Status | Severity | P | Whiteboard |
---|---|---|---|---|---|---|---|---|---|
0 |
Undecided
ID | Assignee | Summary | E | Milestone | Requester | Status | Severity | P | Whiteboard |
---|---|---|---|---|---|---|---|---|---|
0 |