Jump to content

Calligra/Schedules/Release Blockers: Difference between revisions

From KDE Community Wiki
← Older editNewer edit →
Cyrille (talk | contribs)
437 edits
No edit summary
Danders (talk | contribs)
4 edits
Line 9: Line 9:


Results build server are available here:
Results build server are available here:
* [http://my.cdash.org/index.php?project=Calligra&display=project Calligra on cdash]
https://invent.kde.org/office/calligra/-/pipelines
* [http://158.36.191.251:8080/viewLog.html?buildTypeId=bt7&buildId=lastFinished&guest=true Loading files from the test suite] [http://158.36.191.251:8080/guestAuth/feed.html?itemsType=builds&buildStatus=successful&buildStatus=failed&itemsType=changes&userKey=guest rss]
* [http://158.36.191.251:8080/viewLog.html?buildTypeId=bt6&buildId=lastFinished&guest=true Running the unit tests]
 


= Release critical bugs =
= Release critical bugs =

Revision as of 06:27, 9 September 2022

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 release critical bugs

Test suite

Results build server are available here: https://invent.kde.org/office/calligra/-/pipelines

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

Retrieved from "https://community.kde.org/index.php?title=Calligra/Schedules/Release_Blockers&oldid=94510"