nyuuzyou/wikis huggingface dataset:
Yocto Bug Trend

This page is to show latest Yocto Project bug trend status. 5 main charts and 1 detail chart are included. The first and second charts indicate the total open bug number by importance and severity. The third set of charts show open bugs by product. The fourth chart indicates the new bug submission and bug fixing count every week. The fifth chart is the sum of weights for all open bugs and the sixth one represents the report of the wdd over the total number of bugs.
Chart data is now gathered automatically and displayed using detailed interactive charts. Hover your mouse over various parts of the charts for more detail. The dynamic axis labels will sometimes omit text for readability but the relevant data is displayed in the chart. 
=== Bug status of current WW===
Please click through to view the charts. 
View All in one 
Open Bug Trend by Importance
Importance
Importance - Display by day, filter by range + data table
Open Bug Trend by Severity - Enhancement and Janitors bug not included
Severity
Open Bug Trend by Product
Products of Interest 
Products 	Other Products 	Excluded Components
AutoBuilder 	ADT 	minnowboard-firmware
BitBake 	ADT Manual 	minnowboard-uefi-firmware
BSPs 	Anjuta Plugin 	minnowmax-edk2
Eclipse Plugin	Automated Build Testing 	hw-minnowmax
Hob 	Automated Runtime Testing	hw-minnowmax-jtag
Kernel 	BSP Docs 	hw-minnowmax-calamari
Meta-yocto 	BSP Guide 	hw-minnowmax-seacat
OE-Core 	BitBake User Manual 	
Reference 	Bugzilla 	
Sato 	Build Appliance 	
Toaster 	Build System 	
Website 	Core OS 	
 	CROPS 	
 	Cross-prelink 	
 	Development 	
 	Development Manual 	
 	Documentation 	
 	eSDK 	
 	Firmware 	
 	General Docs 	
 	Installation 	
 	Kernel Development 	
 	Layers 	
 	Maintanence Tools 	
 	Manual Testing 	
 	Matchbox 	
 	Mega Manual 	
 	Meta Recipes 	
 	opkg 	
 	Package Management Issues	
 	Poky 	
 	Pseudo 	
 	Quick Start 	
 	Runtime 	
 	Runtime Distribution 	
 	SDK Anjuta Plugin 	
 	SDK Eclipse Plugin 	
 	SDK Plugin 	
 	SDK Tools 	
 	Security 	
 	Security - Recipe Upgrade	
 	System Startup 	
 	Test Plans/Suite 	
 	Testopia 	
 	Wiki 	
 	Yocto Test Suite 	
Bug Product Triage - List of bugs by Product group
All Products See what Other is made up of.
New Submitted and Fixed Bug number
Detailed Submitted and Fixed
Weighted Defect Density for Opened Bugs - Enhancement and Janitors bug not included Note:
How we calculate the data of "weighted defect density"? We define a weight for each severity. And the sum of these weights for all open bugs are the data we record in chart. The weight we use for each severity: Critical:10, Major:7, Normal:5, Minor:3, Enhancement:0, Janitors:0 
Basic Weighted Defect Density or 
Advanced Weighted Defect Density (requires flash)
Weighted Defect Density for Opened Bugs pondered by the total number of bugs
Basic Weighted Defect Density Plus! or
Advanced Weighted Defect Density Plus! (requires flash)
Experimental Reports
Commit Activity
Daily WDD
Yocto Feature Summary

== Summary (Current and Next)==
This page is intended to fill the gap between the very high level list of features (theme) of a forthcoming Yocto Project release and the Bugzilla entries that represent the work to be done. The table refers to a set of Core Components and via links on the table itself.
Component 	v2.2	v2.3 (subject to change)
Theme 	
* Switch to Python 3.x
* Add multiple configurations to allow multiple builds which allows for multiple machines
* Better integration of patchwork, swupd, and error reporting system for a better process.
* Better integration and user adoption of Toaster, eSDK, and CROPS.	TBD
Core Tools 	
* Move from python 2 to 3 (newer features, performance, be current/relevant)
* Better reporting of task progress to users
* Multi-configuration builds (request from WRS)
* devtool: Support node.js projects (i.e. not in NPM registry)
* devtool: Add 'finish' command to publish recipe updates	
* Distributed build
* devtool: Add ability to import packages from existing Linux distros e.g. Debian, Fedora
BSP 	
* Select next Kernel: 4.8
* Update to Tiny Configuration to support hardware rather than qemu	TBD
Content 	
* Refresh graphical interface, ported to a modern toolkit on X11.
* Drop uclibc, support musl as “lighter” option for micro Linux deployments.	TBD
Toaster & UX 	
* Major focus is bug fixing
* Allow project deletion
* Remove git dependency
* Enable layer configuration via Django fixture	
* Simplify extensible SDK build
* Enable layer configuration via U/I
Extensible SDK	
* Faster installation with improved user feedback
* Eclipse plug-in support.
* Promote over traditional SDK	
CROPS 	
* Resurrect Eclipse plug-in and add support for Mars and Neon
* Container work file access for foreign OSes via samba
* Extensible SDK container (CLI only)
* Poky and Ostro containers (CLI only)
* Toaster container	
* Eclipse plug-in to use extensible SDK container
QA 	
* Extend test coverage
* Improve open QA tools: Test report tool, Autobuilder calls tests, device automation	TBD
== Previous Releases ==
Yocto General Features

This page defines general features that are available in all releases of Yocto.
== Core Features ==
Feature Name 	Description 	Priority	Status	Source	Comments / Bugzilla Links
Target embedded developers 	Yocto Project shall be targeted to Embedded developers creating custom image builds for OEM/ODM/Vendor specific boards typical of embedded market place. 	1 	Accept	Team 	
Common download 	The Yocto Project website will provide a common download location for Yocto Linux milestone builds and BSPs. 	1 	Accept	Team 	
License acceptance 	The Yocto Project website has the capability to require license acceptance to get access to certain IP blocks. 	1 	Accept	Team 	
Specify kernel versions 	A user can specify the versions for kernel and all packages explicitly or take the default versions. 	1 	Accept	Team 	
Upsgream project up-to-date	Upstream projects which are components of Yocto Project will be kept up to date as their quality demands. The project will track version changes for upstream projects such that they can be used. For example, the version of the default Linux kernel will be selected 6 weeks prior to the project release milestones. Note that earlier versions of packages will not be validated by default.	1 	Accept	Team 	
No GPL v3 version 	It will be possible to generate an OS image using a layer which contains no components licensed under GPL v3. It may be limited in features and may contain stale components. These exceptions will be documented. 	1 	Accept	Team 	
Easy install 	The hardware validation teams must be able to easily install an OS image generated by Yocto Project. Installation must be no more difficult than a recent Linux distribution. 	1 	Accept	Team 	
Ubuntu support 	Yocto Project builds on an IA host system with 4GB RAM and 50GB free disk space running Ubuntu 10.10. The Yocto Project standalone ADT will have additional OS package requirements for IDE components. 	1 	Accept	Team 	Note: Targets listed are for Yocto 1.0. This will be updated for Yocto 1.1.
Fedora support 	Yocto Project builds on an IA host system with 4GB RAM and 50GB free disk space running Fedora 13 or 14. The Yocto Project standalone ADT will have additional OS package requirements for IDE components. 	1 	Accept	Team 	Note: Targets listed are for Yocto 1.0. This will be updated for Yocto 1.1.
== Performance ==
Feature Name 	Description 	Priority	Status	Source	Comments / Bugzilla Links
Build Performance	The time to do a complete rebuild of local sources of poky-image sato on a developer's desktop should be less than 90 minutes.	1 	Accept	Team 	The desktop being used to test is: Intel(R) Core(TM) i7 CPU 940 @ 2.93GHz, 8 siblings, 4 cpu cores, total mem 6118644k, with: MACHINE=qemux86, BB_NUMBER_THREADS = "8", PARALLEL_MAKE = "-j 6", and only rpm packaging.
Boot Time 	TBD 	1 	Accept	Team 	
Footprint 	TBD - Need some statistics on memory and storage targets. 	1 	Accept	Team
Yocto Project 1.4 Migration notes

= Changes in 1.4 that impact migration =
STAMP and WORKDIR were redefined in this release such that they are now structured <name>/<version> instead of <name>-<version>.
All uses of FILESDIR were removed from OE-Core. FILESPATH was also massively simplified, particularly recipes with files in the current directory are no longer supported by default (use a <name>-<version> or 'files' directory to contain them). Files in -native recipes may also need tweaking since we now only use BPN as the package name to search for, not PN.
Yocto Project Branch Conventions

== Branching Conventions ==
=== Introduction ===
This page explains when we branch certain Yocto Project repositories, the naming conventions used and what we require from third party BSP maintainers if their BSPs are built via the Yocto Autobuilder
==== Branching Philosophy ====
We try to limit the number of branches in the main Yocto Project repository to feature branches, master, master-next and release branches. At one point in the past, we regularly utilized branches for milestones. In general, we no longer do so, however, we can and will utilize milestone branches when we're trying to maintain the stability of master, but get a very large feature into a milestone.
==== Naming Conventions ====
We utilize for the poky, eclipse-plugin-*, meta-qt3 repos the following convention
1. If it is a milestone branch, which should be rare, the branch name will be M.m_M<milestone_number>. Example: 1.5_M1
2. If it is a release branch, the branch name will be the name of the release (dylan, dora, etc)
3. If it is a next branch, the branch name will be the name of what it is the next of, appended with a -next (master-next, dora-next)
==== BSP repo maintainers ====
At one point in the past, we required BSP repo maintainers to maintain their repos utilizing our naming convention if they were utilizing the autobuilder infrastructure to maintain their builds. We no longer require this. However, BSP repo maintainers, should take note that it is their job to inform Build and Release of what branches/tags they wish to have included in a milestone/release build. It is also their job to make sure that the release branches are kept up to date.
Yocto Project EOSS 2024

== Yocto Project® EOSS Mini-Summit 2024 ==
The Yocto Project ran a mini-Summit at EOSS in 2024. 
EOSS home page: https://www.eosconference.com/san-diego/agenda/
Mini-Summit: https://www.yoctoproject.org/event/yocto-project-at-embedded-open-source-summit/
* DATE:​ April 16-18, 2024
* LOCATION:​ Seattle, Washington
== Slides ==
Slides are here:
== Example Wiki page with slides attached ==
https://wiki.yoctoproject.org/wiki/DevDay_Portland_2018
Yocto Project Release Checklist

Major Release 
- Week prior to build of release candidate
 - Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle
 - wic 
 - meta-yocto-bsp 
 - meta-yocto
 - linux-firmware 
 - bootloaders (grub, syslinux, u-boot, gummiboot, etc..) 
 - hwdata 
 - pciutils 
 - util-linux 
 - i2c-tools 
 - alsa 
 - graphics drivers 
 - cryptodev 
 - systemtap
 - perf
 - linux-yocto
- Prior to build of the first release candidate
 - Is DISTRO_VERSION updated in poky.conf?
 - Is SDK_VERSION updated in poky.conf?
 - Is SANITY_TESTED_DISTROS updated in poky.conf?
 - Are yocto-docs merged to the release branch?
 - Has bitbake -f -c distrodata universe been run?
 - Has an updated distro_alias.inc patch been accepted?
- After the final release candidate has returned from QA and is approved, verify the following:
 - Tarballs have been updated with the correct naming conventions. (for release prior to 4.0)
 - BSP tarballs have been generated.
 - rpm and deb directories have been removed. (Discontinued after 4.0.x)
 - Machines subdirectories have been cleaned up. (Symlinks removed, dupes deleted, etc.)
 - Eclipse plugins/archives have been published to http://downloads.yoctoproject.org/ and https://ep.yocto.io/. (Discontinued after 2.6.x)
 - ADT has been published, if applicable. (Deprecated with Yocto 2.0 release and later.)
 - sha256sum file for the entire release has been generated. (Discontinued after 3.4.x)
 - Release Notes have been created, finalized, and approved.
 - Release Notes have been signed.
 - Repos have been tagged with correct commit and signature. 
 - Release and BSP pages have been created on yoctoproject.org website. (Deprecated with new page introduced in Nov 2023)
 - The README for each BSP has been checked and updated if necessary.
 - Documentation links have been created on yoctoproject.org website. (Deprecated with new page introduced in Nov 2023)
 - Update the release dates and QA link on website backend. (Deprecated with new page introduced in Nov 2023)
 - Download links have been tested. (Deprecated with new website page in Nov 2023)
 - The mirror sync has been triggered and completed successfully.
 - Copy symlinked files into release sstate (Deprecated)
 - Update the idlebuild weekly build script to include any new branches
 - Update the slider at www.yoctoproject.org with the new release dates (Deprecated with new page introduced in Nov 2023)
 - The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
Yocto Project Roadmap

=== Yocto Project future roadmap ===
At the highest level, the Yocto Project consists of three major components:
* A build system - based primarily on the Bitbake project and including other associated projects such as Pseudo
* Metadata - which includes classes, recipes, files and patches which, when taken together, build a working Linux system (OpenEmbedded-Core and other layers)
* A developer experience - methodologies and tools for developing embedded devices, which is mostly based on Eclipse, but also includes Hob and other tools.
The project will continue to do regular releases to support development and bug fixes in all of these areas.
For more specifics around what the project community is working on, check out the Yocto Project bugzilla.
Yocto Project Tagging Conventions

=== Yocto Project Tags ===
In order to understand the tagging used within the Yocto Project, it is important to note what we release. We can break up our releases into three types. Major, minor, milestone. For each of these we release both the Yocto Project as well as the reference distribution, "poky", that we built with this version of the Yocto Project's build system.
During Milestone releases, we utilize the milestone naming convention to denote both poky and Yocto Project milestone releases. So, for example, during 1.4's milestone 4 release, we would use 1.4_M4.
Once we've branched to a major or minor named release branch, we no longer use the milestone name. We denote yocto releases and poky releases with different tags. There is no technical reason for this, it is merely for convenience. Some people are more familiar with Yocto release names over poky release names
=== Yocto Project Tagging Conventions ===
In general, we utilize 3 main types of tags in the main Yocto Project repositories:
Milestone Tags:
M.m_M<milestone number>
1.4_M2
Poky Tags:
<name>-M.m.p
dora-10.0.0
Yocto Project Tags:
yocto-M.m
yocto-1.5
We also have a few prefixes that we've utilized for tags in the past:
* release candidate
Used to denote a release candidate
yocto-1.5_M5.rc1
dora-10.0.0.rc8
* final release
Used to denote "final". Because we are aggressive in our release schedule, and because we do not delete tags, we utilize .final to denote the final version of a major and point releases.Most times, the .final tag will match up with the <name>-M.m.p tag. But we utilize .final when we sometimes have to slip a few changes into the release before it goes it. This is especially useful for documentation.
dora-10.0.0.final
When in doubt, always utilize the .final tag.
Yocto Project v1.0.1 Release Criteria

== Yocto Project 1.0.1 Release Criteria ==
Yocto Project 1.0.1 is a point release from Yocto Project 1.0. In general, it contains critical bug fixes as well as nice to have items that are small, well-contained and provide a high benefit to include.
The criteria for adding a code submission into 1.0.1 are that the change:
* Addresses a High priority issue. (Typically, these have critical or major severity.)
* Is small and simple to evaluate (both in lines of code and complexity)
* Fixes a specific problem which users are likely to encounter
* Fixes that problem in a clearly defined way
* Is self contained and unlikely to interact badly with other parts of the system
* Fixes known/clear bugs
Good candidate changes are ones which:
* Address usability issues
* Address host specific issues, particularly in releases of distros that come out after our release
* Address post release bugs users are hitting and reporting
* Address security issues
Bad candidate changes include:
* Significant changes of version (point release for security problems are acceptable)
* Anything involves major code changes where changes cannot be reviewed individually or separated out
* Adding new features
* Changes that break the layout or compatibility with existing builds
* Changes that would trigger significant rebuilds
	 Release Criteria		 Target		 Status
	Functional Completion		No new significant features are added. Any minor functionality added is documented in git logs.		List of commits has been defined and reviewed and all bugs are in the release.
	Build and Release (Yocto)		1.0.1 build can be built with no errors.		Build was successful.
	Build and Release (BSPs)		BSPs targeted for 1.0.1 (= all current BSPs) are built.		N/A - BSPs will not be built for 1.0.1.
	Open Bugs		All bugs targeted for 1.0.1 are in the build by May 13th.		Open bug query shows one bug - not a show-stopper?Bugs found during testing have been fixed:bug 1029 Fixed - mmc commands must be run from a prompt to do uboot - this will go in Release Notes and README.hardwarebug 1087 is FixedTotal bug count: 28 bugs total
	Functional Tests		100% of planned tests are executed and results are logged in bugzilla.		BLOCKED items are now testedfile:1.0.1FullTest_Pass19MAY11.PNGCompliance tests will not be done for 1.0.1.
	BSP Testing		100% of planned tests are executed and results are logged in bugzilla.		Tests passed
	Documentation		1.0.1 Release Notes are complete.		Need to provide Release Notes to tech editor prior to release.
	Build Performance		1.0.1 does not increase performance above 107 minutes on a developer machine.		We have increased build time (~2 minutes) due to a fix, but this was a concsious decision by the team.
	Publication		1.0.1 release is built and announced to the community.
Yocto Project v3.0 Status

= Project Dashboard =
https://wiki.yoctoproject.org/charts/combo.html
= Feature/Task Board = 
== Overview ==
Scheduled	Design	Design Complete	Development	Patch Review	Testing	Done	Blocked
 	 	 	 	 	 	 	
== List View ==
=== Blocked === 
=== Planned ===
=== Scheduled ===
=== Design ===
=== Design Complete ===
=== Development ===
=== Patch Review ===
=== Testing ===
=== Done ===
= Yocto Project v2.8 Release Criteria = 
== Milestone 1 - Target June 9, 2019 == 
	 Release Criteria		 Milestone 1 Target		 Milestone 1 Status
	Functional Completion		All high features are completed.	Done
	Build and Release (Yocto)		All completed features can be built with no errors.	Done
	Build and Release (BSPs)		Core BSPs can be built with no errors.	Done
	Open Bugs		All bugs have been dispositioned. Milestone high issues have been fixed.	Done
	Functional Tests		100% of planned tests are executed and results are logged in bugzilla.	Done -
	Distros Tested		Fedora, Ubuntu, Opensuse, Centos current version	Done - CentOs 7, Debian 9, Fedora 26, Fedora 27, OpenSuse 42.3, Ubuntu 16.04, Ubuntu 17.10
	BSP Testing		100% of planned tests are executed and results are logged in bugzilla.	Done -
	Build Performance		Try to at least maintain the current performance and improve if possible.	Done -
	Package Update		Plan to have 70% or greater packages updated.	Done
	Patch Upstream Status		Less than 50% of all patches in Pending state.	Done -
	Publication		The release is announced	Released
Yocto Project v3.1 Status

= Project Dashboard =
https://wiki.yoctoproject.org/charts/combo.html
= Feature/Task Board = 
== Overview ==
Scheduled	Design	Design Complete	Development	Patch Review	Testing	Done	Blocked
 	 	 	 	 	 	 	
== List View ==
=== Blocked === 
=== Planned ===
=== Scheduled ===
=== Design ===
=== Design Complete ===
=== Development ===
=== Patch Review ===
=== Testing ===
=== Done ===
= Yocto Project v3.1 Release Criteria = 
== Milestone 1 - Target Dec 2, 2019 == 
	 Release Criteria		 Milestone 1 Target		 Milestone 1 Status
	Functional Completion		All high features are completed.	
	Build and Release (Yocto)		All completed features can be built with no errors.	
	Build and Release (BSPs)		Core BSPs can be built with no errors.	
	Open Bugs		All bugs have been dispositioned. Milestone high issues have been fixed.	Done
	Functional Tests		100% of planned tests are executed and results are logged in bugzilla.	-
	Distros Tested		Fedora, Ubuntu, Opensuse, Centos current version	Done - CentOs 7, Debian 9, Fedora 26, Fedora 27, OpenSuse 42.3, Ubuntu 16.04, Ubuntu 17.10
	BSP Testing		100% of planned tests are executed and results are logged in bugzilla.	-
	Build Performance		Try to at least maintain the current performance and improve if possible.	-
	Package Update		Plan to have 70% or greater packages updated.	
	Patch Upstream Status		Less than 50% of all patches in Pending state.	-
	Publication		The release is announced