Yocto 3.2 Features

From Yocto Project
Revision as of 06:49, 22 October 2020 by Sangeeta Jain (talk | contribs) (Created page with "== Yocto Project 3.2 Feature Planning == Yocto Project 3.2 release planning has been underway since Apr, 2020. Most all new features and ideas about 3.2 release are tracked a...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Yocto Project 3.2 Feature Planning

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

Yocto Project 3.2 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.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

IDAssigneeSummaryEMilestoneRequesterStatusSeverityPWhiteboard
13914Steve SakomanEnhance oe-selftest to preserve build directories of failed builds3.2 M1Richard PurdieRESOLVEDenhancementHighbackport
   0      

Medium+

IDAssigneeSummary (7 tasks) ⇒EMilestoneRequesterStatusSeverityPWhiteboard
13845Alexander KanavinAdd ptest for libinput3.2 M1Alexander KanavinRESOLVEDenhancementMedium+
10690yeoh ee pengImprove wayland QA13.2 M1Jussi KukkonenRESOLVEDenhancementMedium+
12938Martin Jansavirglrenderer+spice support in qemu-native with accelerated GL33.2 M1Martin JansaRESOLVEDenhancementMedium+
13319Matthew ZengAdd SPDX license headers to all source files for matchbox/sato3.2 M3Richard PurdieRESOLVEDenhancementMedium+NEWCOMER
13495Chen QiSupport building out container image without init manager3.2 M3Chen QiRESOLVEDenhancementMedium+
13881Richard PurdieBitdoc broken in latest and prior releases, remove or fix?3.2 M1 RESOLVEDenhancementMedium+
13315UnassignedMigrate poky's WARN_TO_ERROR_QA settings to OE-Core defaults3.2 M1Richard PurdieRESOLVEDenhancementMedium+
   4      

Medium

IDAssigneeSummaryEMilestoneRequesterStatusSeverityPWhiteboard
13514Unassignedreproducible QA: Build RPMs as part of test3.2Joshua WattRESOLVEDenhancementMedium
   0      

Low

IDAssigneeSummaryEMilestoneRequesterStatusSeverityPWhiteboard
   0      

Undecided

IDAssigneeSummaryEMilestoneRequesterStatusSeverityPWhiteboard
   0      
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_3.2_Features&oldid=79573"