Calligra/Schedules/Release Blockers

From KDE Community Wiki
Revision as of 17:57, 6 December 2010 by Cyrille (talk | contribs) (Created page with 'This page gives access to information on the blocker of a KOffice release. = Test suite = Result for the test suite can be available [http://www.koffice.org/testresults/status.h...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This page gives access to information on the blocker of a KOffice release.

Test suite

Result for the test suite can be available here. A KOffice release can only happen when:

  • there is no failing test in KOffice/libs
  • there is no regression

Results from an additional build server are available too:

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)

Link to Release critical bugs