|
|
| (8 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | '''Stopper''', '''Blocker''', '''Showstopper''', '''Release Stopper''', '''Release Blocker''' or however you want to call it. These [[bug]]s/[[issue]]s are most critical, because the release can be stopped until it is fixed. The result can be a delay of one or more weeks for a release.
| + | #REDIRECT [[Showstopper]] |
| − | | + | |
| − | | + | |
| − | ==Meaning==
| + | |
| − | In the past '''Stopper''' issues were reported on Release Candidates only. Since OOo 3.2 this was changed. Since OOo 3.2 there is a general phase to promote '''Stopper''' issues. When the release code-line is split (branched off) from the general development code-line (DEV300) this phase starts. Only '''Stopper''' issues are excepted by the Release Manager for integration into the release code-line. This is needed to stabilize the version until the release. It isn't allowed to make bigger changes, where the risk isn't clear and which aren't explicit needed for the release.
| + | |
| − | | + | |
| − | | + | |
| − | ==Criteria for a '''Stopper''' issue==
| + | |
| − | * it is a regression in main functionality
| + | |
| − | * it is a crash in main functionality
| + | |
| − | * it is a freeze or loop in main functionality
| + | |
| − | * it is a security issue
| + | |
| − | * it is a privacy issue
| + | |
| − | * it is a data loss
| + | |
| − | * it is a build breaker on one or more of the generally supported platforms
| + | |
| − | * it is an important usability issue in Accessibility (A11Y)
| + | |
| − | | + | |
| − | ==Samples for a '''Stopper''' issue==
| + | |
| − | * OOo isn't installable on one or more systems
| + | |
| − | * an OOo application cannot be started
| + | |
| − | * OOo crashes when common documents are saved/loaded
| + | |
| − | * general functionality is broken from one build to another
| + | |
| − | * ODF validation problem
| + | |
| − | * a supported API is broken from one build to another
| + | |
| − | All these issues have to be reproducible by a developer. Without reproducible scenario it isn't possible for a developer to find the root cause and the bug cannot be fixed.
| + | |
| − | | + | |
| − | | + | |
| − | ==What isn't a '''Stopper''' issue==
| + | |
| − | * general fixes for unimportant bugs
| + | |
| − | * general code clearing up
| + | |
| − | * general features or enhancements
| + | |
| − | | + | |
| − | | + | |
| − | ==How to promote/nominate a '''Stopper''' issue==
| + | |
| − | When you found a [[bug]], which you want to promote as '''Stopper''' you have to submit it in [[IssueTracker]] first. If you have an issue number you have to write a mail to releases@openoffice.org. (Please [http://www.openoffice.org/mail_list.html register at this mailing list] first to get answers for your mail directly.)
| + | |
| − | | + | |
| − | You should write into the mail the issue ID (best with direct link), a short summary and why you want to promote this issue.
| + | |
| − | | + | |
| − | Within the next 1-3 days you will get an exception or a rejection via mail from a Release Manager.
| + | |
| − | | + | |
| − | If you aren't sure if your bug is a '''Stopper''' or not, you can ask on the mailing list too.
| + | |
