Yocto Project v1.0.1 Release Criteria: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(→‎Yocto Project 1.0.1 Release Criteria: added criteria for release)
Line 32: Line 32:
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || bgcolor="yellow" | Build will run May 14th to May 21st.  Beth will run a test build the week of May 3rd.  She has a plan that doesn't require getting new hardware to do.
| Build and Release (BSPs) || BSPs targeted for 1.0.1 (= all current BSPs) are built. || bgcolor="yellow" | Build will run May 14th to May 21st.  Beth will run a test build the week of May 3rd.  She has a plan that doesn't require getting new hardware to do.
|-
|-
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 17 bugs] exist for 1.0.1 so far; triage team will disposition to ensure we have the right list.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 30 bugs total]
| Open Bugs || All bugs targeted for 1.0.1 are in the build by May 13th. || bgcolor="yellow" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.0%20PointRelease 14 open bugs]<br>[http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&target_milestone=1.0%20PointRelease 30 bugs total]
|-
|-
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || First test pass will be May 21st-22nd (weekly).  Go/No-Go will determine if full test pass should be done.
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || First test pass will be May 21st-22nd (weekly).  Go/No-Go will determine if full test pass should be done.

Revision as of 20:26, 9 May 2011

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. There are 300 commits that Richard is looking through to pull for 1.0.1.
Build and Release (Yocto) 1.0.1 build can be built with no errors. Build will run May 14th to May 21st. Beth will run a test build the week of May 3rd. She has a plan that doesn't require getting new hardware to do.
Build and Release (BSPs) BSPs targeted for 1.0.1 (= all current BSPs) are built. Build will run May 14th to May 21st. Beth will run a test build the week of May 3rd. She has a plan that doesn't require getting new hardware to do.
Open Bugs All bugs targeted for 1.0.1 are in the build by May 13th. 14 open bugs
30 bugs total
Functional Tests 100% of planned tests are executed and results are logged in bugzilla. First test pass will be May 21st-22nd (weekly). Go/No-Go will determine if full test pass should be done.
BSP Testing 100% of planned tests are executed and results are logged in bugzilla. First test pass will be May 21st-22nd (weekly). Go/No-Go will determine if full test pass should be done.
Documentation 1.0.1 Release Notes are complete. Release notes to begin May 14th.
Build Performance 1.0.1 does not increase performance above 107 minutes on a developer machine.
Publication 1.0.1 release is built and announced to the community.