The next update autoqa

[James Laska]

Hi gang,

With Fedora 14 mostly behind us, at least our test execution efforts, I
was hoping to plan out the next version of autoqa.  Given we've been
primarily focused on producing a high quality release, there aren't a
large number of changes in master since v0.4.2-1.  However, there were
some significant changes, including:

6670ee2 2010-10-14 allow tests to distinguish CRASHED and ABORTED ([e-mail])
a5ce337 2010-10-13 Reviewed. ([e-mail])
821f162 2010-10-11 Added reviewed initscript tests. ([e-mail])
e0f77a1 2010-10-06 Include traceback in email output ([e-mail])
82baf5f 2010-10-06 Removed individual XYZ_failed methods in test.py ([e-mail])
78cacd5 2010-10-05 guard setup() with ExceptionCatcher ([e-mail])
8e4e894 2010-10-05 allow self.outputs and self.highlights to be lists of strings ([e-mail])
03ca1e8 2010-10-04 Automatically log test output ([e-mail])
c6e5d3a 2010-10-01 Correct missing config_loader import ([e-mail])
a2bd1b1 2010-10-01 Tell post-tree-compose that composes are enabled for F14 ([e-mail])
885e0e1 2010-09-30 tidy up upgradepath test code ([e-mail])
993e394 2010-09-29 upgradepath doesn't support -testing repos yet, disable scheduling ([e-mail])

Additionally, I believe there are some upcoming changes we'll want to
include.  I'm guessing we're targeting the following changes ...

1. First release of depcheck
              * Add mash support to depcheck
                (https://fedorahosted.org/autoqa/ticket/201)
              * Add depcheck to post-bodhi-update hook
                (https://fedorahosted.org/autoqa/ticket/204)
              * Make depcheck submit karma/comments to bodhi
                (https://fedorahosted.org/autoqa/ticket/205)
     2. ResultsDB support
              * Enable results collection (ticket?)
     3. Anything else?

Should we cut a new version (autoqa-0.4.3-1) now including all changes
in master.  Should we wait for the remaining changes listed above?  What
is a good timeframe for the release?

Thanks,
James

[Kamil Paral]

----- "James Laska"  wrote:
> Hi gang,
>
> With Fedora 14 mostly behind us, at least our test execution efforts,
> I
> was hoping to plan out the next version of autoqa.  Given we've been
> primarily focused on producing a high quality release, there aren't a
> large number of changes in master since v0.4.2-1.  However, there
> were
> some significant changes, including:
>
> 6670ee2 2010-10-14 allow tests to distinguish CRASHED and ABORTED
> ([e-mail])
> a5ce337 2010-10-13 Reviewed. ([e-mail])
> 821f162 2010-10-11 Added reviewed initscript tests.
> ([e-mail])
> e0f77a1 2010-10-06 Include traceback in email output
> ([e-mail])
> 82baf5f 2010-10-06 Removed individual XYZ_failed methods in test.py
> ([e-mail])
> 78cacd5 2010-10-05 guard setup() with ExceptionCatcher
> ([e-mail])
> 8e4e894 2010-10-05 allow self.outputs and self.highlights to be lists
> of strings ([e-mail])
> 03ca1e8 2010-10-04 Automatically log test output ([e-mail])
> c6e5d3a 2010-10-01 Correct missing config_loader import
> ([e-mail])
> a2bd1b1 2010-10-01 Tell post-tree-compose that composes are enabled
> for F14 ([e-mail])
> 885e0e1 2010-09-30 tidy up upgradepath test code ([e-mail])
> 993e394 2010-09-29 upgradepath doesn't support -testing repos yet,
> disable scheduling ([e-mail])
>
> Additionally, I believe there are some upcoming changes we'll want to
> include.  I'm guessing we're targeting the following changes ...
>  1. First release of depcheck
>           * Add mash support to depcheck
>             (https://fedorahosted.org/autoqa/ticket/201)
>           * Add depcheck to post-bodhi-update hook
>             (https://fedorahosted.org/autoqa/ticket/204)
>           * Make depcheck submit karma/comments to bodhi
>             (https://fedorahosted.org/autoqa/ticket/205)
>  2. ResultsDB support
>           * Enable results collection (ticket?)
>  3. Anything else?
>
> Should we cut a new version (autoqa-0.4.3-1) now including all
> changes
> in master.  Should we wait for the remaining changes listed above? 
> What
> is a good timeframe for the release?

I believe now is a good time for a next release. The above-mentioned
pending features will take some time to be completed and tested,
I wouldn't wait for it.

Once we have depcheck and upgradepath sending comments to bodhi,
I see it as another major milestone and I'd go for a next release.