Roadmap

Milestone: Hot issues

4 years late (01/01/10 00:00:00)

67%

Number of tickets:
closed:
18
active:
9
Total:
27

High importance problems that should have been solved yesterday.

Milestone: 0.9.0

21 months late (08/01/12 00:00:00)

100%

Number of tickets:
closed:
6
active:
0
Total:
6

Milestone: Nice to have soon

16 months late (12/31/12 00:00:00)

40%

Number of tickets:
closed:
2
active:
3
Total:
5

Lower priority items that are not targeted at a specific release, but we would like to have them implemented very soon. These tickets won't block any new release, but when they are complete, we will happily accept them to any major/minor release.

Milestone: Finger Food

16 months late (01/01/13 00:00:00)

25%

Number of tickets:
closed:
2
active:
6
Total:
8

Minor changes suitable for new folks.

Milestone: Future tasks

4 months late (01/01/14 00:00:00)

24%

Number of tickets:
closed:
5
active:
16
Total:
21

Ticket pool of all future tasks that are not specific to any other milestone. Tasks for the next release are picked from here.

Milestone: Automate installation test plan

Due in 6 years (01/01/20 00:00:00)

24%

Number of tickets:
closed:
8
active:
25
Total:
33

Tracking tasks/defects identified in order to automate the installation test plan for Fedora. For more information, see https://fedoraproject.org/wiki/Is_anaconda_broken_proposal

Milestone: Depcheck

Due in 6 years (01/01/20 00:00:00)

20%

Number of tickets:
closed:
3
active:
12
Total:
15

Tasks related to 'depcheck' test.

Milestone: Future test cases

Due in 6 years (01/01/20 00:00:00)

82%

Number of tickets:
closed:
14
active:
3
Total:
17

This is a pool of future test cases ideas that would be nice to have implemented inside AutoQA.

Milestone: Package Update Acceptance Test Plan

Due in 6 years (01/01/20 00:00:00)

83%

Number of tickets:
closed:
25
active:
5
Total:
30

This milestone tracks implementing various test cases outlined in the Package Update Acceptance Test Plan. Tests and other changes include:

  • Test changes
    • Upgrade path test
    • Improving rpmguard test output for maintainers
    • Improving rpmlint test output for maintainers (including whitelisting results)
  • Other changes
    • Detecting when package updates are available for test

Individual package updates are detected, evaluated and tested by various tests.

This milestone tracks implementing package sanity tests outlined in the Package Sanity Test Plan. Package sanity is a required component of the Package Update Acceptance Test Plan. Tasks in this milestone include package installation, removal, upgrade and downgrade.

Milestone: Packaging, Review, & Deployment

Due in 6 years (01/01/20 00:00:00)

70%

Number of tickets:
closed:
14
active:
6
Total:
20

Tracking the process of packaging and reviewing all software needed for a proper AutoQA and Autotest deployment in Fedora infrastructure

Milestone: Resultdb

Due in 6 years (01/01/20 00:00:00)

76%

Number of tickets:
closed:
13
active:
4
Total:
17

Tracking efforts towards creating a unified results database to allow for the creation of test result dashboards

Milestone: Rpmguard

Due in 6 years (01/01/20 00:00:00)

9%

Number of tickets:
closed:
1
active:
10
Total:
11

The pool of issues, ideas and improvements for rpmguard.

Milestone: Self Test

Due in 6 years (01/01/20 00:00:00)

0%

Number of tickets:
closed:
0
active:
4
Total:
4

Milestone: Virtualization

Due in 6 years (01/01/20 00:00:00)

40%

Number of tickets:
closed:
2
active:
3
Total:
5

The objective is to be able to use virtualization for AutoQA tests. The virtualization support must be able to distinguish tests which are not suitable for virt and tests which may be run in virt and execute them accordingly. Also it must be possible to run destructive tests inside virt and revert the state afterwards in an automated fashion.

Note: See TracRoadmap for help on using the roadmap.