On Mon, 2010-11-15 at 09:16 -0500, Kamil Paral wrote:
Hello all,
I have created
https://fedoraproject.org/wiki/AutoQA_Roadmap .
Since our manpower decreased (best wishes to wwoods) we really need to
get more focused and selective in our future goals. I would like us to
state some near-future goals that are doable, that have visible benefits
and then concentrate the team on achieving that.
Sometimes the tasks can be divided easily among several people,
sometimes they may not. But as much as possible we should avoid working
on several projects each, as was often the case now. Let's finish up
one task and then go to another, what do you say?
Definitely!
In the roadmap, I'm partially duplicating our Trac Roadmap:
https://fedorahosted.org/autoqa/roadmap
Still, it seemed to me that on wiki page one could easily see the most
important features we want to have in a release. Better than in Trac,
where it is split up more in a functional units rather than time
schedule units.
I'd like to see the thought process start with your
fedoraproject.org
page, and then once finalized ... moved into task-specific tickets in
TRAC. The
fedoraproject.org seems like a natural fit to start the
process since it's much easier to use and we have existing AutoQA
documentation on the wiki. TRAC definitely is more focused on dividing
up smaller work units. How do you feel about this approach (wiki for
the doc, TRAC for the work)?
I believe that the best part to concentrate upon right now are
depcheck
and upgradepath tests. They bring a huge benefit to the Fedora project,
we just need to finish them and hook them up. Therefore I propose Bodhi
comments support in depcheck and upgradepath as the nearest important
feature. Rewriting bodhi watcher is related to that. I would also like
to see AutoQA fully prepared for a staging environment (it almost is
now) - we will get hardware in the meantime. That would be 0.4.4 release.
I mentioned this to Kamil privately, but I'm working on budget to
purchase additional hardware that we could use for a staging
environment.
After we have this work done, I think it's about time to finally
set up ResultDB (we can have some preview in 0.4.4). Having it production
ready would be a next major step, 0.5.0 release.
Please look at the wiki page and tell us what you think.
Love having this info on the wiki and planning out the releases in
advance. Really nice touch.
Thanks,
James