Calligra/Schedules/Release Blockers: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
= Release blockers = | = Release blockers = | ||
A Calligra release can only happen when: | |||
* there is no failing test in | * there is no failing test in | ||
* there is no regression | * there is no regression | ||
Revision as of 17:40, 4 September 2011
This page gives access to information on the blocker of a Calligra release. A summay of release blockers is available on Calligra's quality website.
Release blockers
A Calligra release can only happen when:
- there is no failing test in
- there is no regression
Test suite
Results build server are available here:
Release critical bugs
Release critical bugs are marked in KDE's bugzilla using the release_blocker keyword.
Definition of a Release Critical bug
A Release Critical Bug is:
- data loss
- crash that prevent the use of the application (for instance crash at startup)
A Release Critical Bug isn't:
- user interaction (for instance a feature that can be done better)
- appearance (for instance a docker that is X pixels wider than it should)