m (Clarify non-visual rules) |
(Shortcuts) |
||
| Line 6: | Line 6: | ||
! colspan="2" | Requirement | ! colspan="2" | Requirement | ||
|- | |- | ||
| - | | | + | | Days in quarantine? |
| colspan="3" | System | | colspan="3" | System | ||
| - | | colspan="2" | | + | | colspan="2" | >= 10 |
|- | |- | ||
| Screenshot in OBS. if user-facing? | | Screenshot in OBS. if user-facing? | ||
| Line 49: | Line 49: | ||
|} | |} | ||
| + | * Packagers/authors/maintainers will '''not''' be permitted to vote on their own packages. | ||
| + | * Packagers/authors/maintainers will be able to remove their package from -testing at any time. | ||
* ''Optional'' questions are not required for a user to vote on a package. | * ''Optional'' questions are not required for a user to vote on a package. | ||
* ''Mandatory'' questions must be answered for a user to vote on a package. | * ''Mandatory'' questions must be answered for a user to vote on a package. | ||
* All criteria must be met for a package to be unlocked. | * All criteria must be met for a package to be unlocked. | ||
| + | |||
| + | == Shortcut upgrades == | ||
| + | Some packages will be urgent bug fixes in response to an external API change or critcial bug. In addition to a package owner (or repository master) being able to pull a package on-demand; the promotion capability to -testing should have a ''Critical bug-fix'' box (if, and only if, the package already exists in Apps). This will: | ||
| + | |||
| + | * Add a large box to the evaluation page saying: "The package maintainer has indicated that this release fixes a critical bug. No new functionality should be introduced, as the QA criteria have been relaxed.'' | ||
| + | * All the requirements below will be halved (e.g. 5 day quarantine, 5 net positive votes for inclusion, 1 net positive vote for uninstallation) | ||
| + | * An additional question will be mandatory: | ||
| + | |||
| + | {| class="wikitable" | ||
| + | ! Question | ||
| + | ! colspan="3" | Possible answers | ||
| + | ! colspan="2" | Requirement | ||
| + | |- | ||
| + | | Introduces new functionality? | ||
| + | | Yes | ||
| + | | colspan="2" | No | ||
| + | | ''n'' - ''y'' > 5 | ||
| + | | Mandatory | ||
| + | |} | ||
| + | |||
| + | Regular reporting will be done over the use of the ''critical fix'' flag. If testers or packagers are found to be abusing it, they will be banned from further testing and/or use of the flag for a period (to be determined). | ||
Proposed initial set of quality metrics for promotion into Apps. Unlike in maemo.org Extras, a guided form will be provided.
| Question | Possible answers | Requirement | |||
|---|---|---|---|---|---|
| Days in quarantine? | System | >= 10 | |||
| Screenshot in OBS. if user-facing? | System | n/a | |||
| Should be in Apps? | Yes | No | y - n > 10 | Mandatory | |
| Appropriate icon, if user-installable? | Yes | No | Don't know | y - n > 3 | Optional |
| Appropriate description? | Yes | No | Don't know | ||
| Impacts power/performance in unexpected way? | Yes | No | Don't know | y - n > 2 | |
| Obvious license/copyright issues? | Yes | No | Don't know | ||
| Uninstall cleanly? | Yes | No | Don't know | ||
Some packages will be urgent bug fixes in response to an external API change or critcial bug. In addition to a package owner (or repository master) being able to pull a package on-demand; the promotion capability to -testing should have a Critical bug-fix box (if, and only if, the package already exists in Apps). This will:
| Question | Possible answers | Requirement | |||
|---|---|---|---|---|---|
| Introduces new functionality? | Yes | No | n - y > 5 | Mandatory | |
Regular reporting will be done over the use of the critical fix flag. If testers or packagers are found to be abusing it, they will be banned from further testing and/or use of the flag for a period (to be determined).