|
|
| (8 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| This page contains a sneak peak into [[AutoQA]] future plans. The information here are by no means complete and immutable, but they try to reflect our best intentions and estimates. Only important features are listed (a particular release may of course contain many more enhancements, planned or unplanned).
| | {{header|qa}} |
|
| |
|
| | A sneak peak into [[AutoQA]] future plans can be displayed on the following page: |
|
| |
|
| === 0.4.3 ===
| | https://fedorahosted.org/autoqa/roadmap |
| '''Date:''' ''November 2010''
| |
| | |
| '''Overview:''' This will be just a maintenance release, no big changes in it. It should reflect the fact that Fedora 14 was released.
| |
| | |
| '''Notable changes:'''
| |
| * tests reflect Fedora 14 release
| |
| * upgradepath is disabled for -testing repos
| |
| * test output is stored and accessible amongst other test logs, not just at autoqa-results
| |
| * added new initscripts tests
| |
| | |
| | |
| === 0.4.4 ===
| |
| '''Date:''' ''January 2011''
| |
| | |
| '''Overview:''' This will be an important milestone in AutoQA project, because our results will be widely visible for the first time. This release will focus on the most mandatory tests - depcheck and upgradepath - that offer a large benefit (non-broken repos) while ensuring very low chance of reporting false positives. After deploying this release the RelEng team should have much higher confidence when pushing updates to the stable repositories.
| |
| | |
| '''Notable changes:'''
| |
| * new depcheck test is added and enabled by default
| |
| * depcheck and upgradepath tests report results as Bodhi comments
| |
| * bodhi watcher is rewritten into a watcher monitoring koji -pending tags
| |
| * full support for deploying to a staging server
| |
| | |
| | |
| === 0.5.0 ===
| |
| '''Date:''' ''February 2011''
| |
| | |
| '''Overview:''' This release will focus on shifting from autoqa-results-based storage of results to resultdb-based storage. This will be a major step in AutoQA architecture.
| |
| | |
| '''Notable changes:'''
| |
| * resultdb is deployed and all tests send their results to it (autoqa-results is still used if simple web front-end is still not ready)
| |
| | |
|
| |
|
| | The information there are by no means complete and immutable, but they try to reflect our best intentions and estimates. Only important features are described for a milestone (a particular release may of course contain many more enhancements, planned or unplanned). Standard versioning scheme is used where major number is used for large project changes, minor number for new feature additions, and revision number for bugfix releases. |
|
| |
|
| [[Category:AutoQA]] | | [[Category:AutoQA]] |
A sneak peak into AutoQA future plans can be displayed on the following page:
https://fedorahosted.org/autoqa/roadmap
The information there are by no means complete and immutable, but they try to reflect our best intentions and estimates. Only important features are described for a milestone (a particular release may of course contain many more enhancements, planned or unplanned). Standard versioning scheme is used where major number is used for large project changes, minor number for new feature additions, and revision number for bugfix releases.
