Editing Task:Package QA web interface
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{task|proposal}} | {{task|proposal}} | ||
| - | + | = Need = | |
| - | * Developers need to promote their package from | + | * Developers need to promote their package from extras-devel to extras-testing and extras |
* Packages need to be tested before they are available for the general public | * Packages need to be tested before they are available for the general public | ||
* Community members should be able to help test applications | * Community members should be able to help test applications | ||
| Line 8: | Line 8: | ||
* Testers should see a list of packages waiting to be tested | * Testers should see a list of packages waiting to be tested | ||
| - | + | = Workflow = | |
| - | + | == Regular == | |
A developer uploads a source tarball to the autobuilder. After successful building, this package ends up in extras-devel. | A developer uploads a source tarball to the autobuilder. After successful building, this package ends up in extras-devel. | ||
| Line 24: | Line 24: | ||
Possible outcome: | Possible outcome: | ||
| - | * If a package receives negative feedback, the | + | * If a package receives negative feedback, the debmaster will look at the package's problems. If the problem is serious, the package will be removed from the test queue and the author will be notified. |
| + | |||
* If the package receives X positive feedback, the package goes to the promotion queue for Extras. | * If the package receives X positive feedback, the package goes to the promotion queue for Extras. | ||
| + | |||
* If the package receives no feedback within X days, the debmaster will look at the package and see what needs to be done. | * If the package receives no feedback within X days, the debmaster will look at the package and see what needs to be done. | ||
When a package is in the promotion queue for Extras, the original uploader (or team) can promote the package to Extras. This makes it easy for the project to time their release. | When a package is in the promotion queue for Extras, the original uploader (or team) can promote the package to Extras. This makes it easy for the project to time their release. | ||
| - | + | == Exceptions == | |
* Security fixes can be specially handled by debmaster. | * Security fixes can be specially handled by debmaster. | ||
* Fixes for serious bugs can be specially handled by debmaster. | * Fixes for serious bugs can be specially handled by debmaster. | ||
| - | + | == Implementation questions == | |
* How would we handle dependencies, when promoting and testing an application. | * How would we handle dependencies, when promoting and testing an application. | ||
* Will we remove a package from extras-testing when it has received X amount of negative feedback or only remove it from the testing queue page. | * Will we remove a package from extras-testing when it has received X amount of negative feedback or only remove it from the testing queue page. | ||
| - | + | = Inspirational mockup = | |
[https://fedoraproject.org/wiki/MyFedora/Mockups#Package_Details Fedora Packages page] | [https://fedoraproject.org/wiki/MyFedora/Mockups#Package_Details Fedora Packages page] | ||
| - | + | = Implementation steps = | |
# Package page | # Package page | ||
Learn more about Contributing to the wiki.