relval progress report

[Adam Williamson]

hey, folks - just in case no one spotted it on test@, I have been
moonlighting as a python developer lately...

https://www.happyassassin.net/cgit/relval/

is a little thing I'm writing with the initial goal of making the
process of kicking off a release validation event easy. In the true
tradition of software projects, it already has a hopelessly confused
naming history: it's now officially the module 'wikitcms' with the
command line tool 'relval', but I didn't get around to renaming the
repository yet...

right now it'll create the validation result pages for an event, and
handle categories: it deals with the limitation in the magic template
system that results in pages being in the wrong category, and makes sure
the whole hierarchy of categories up to Test_Results is correct (per the
SOP) each time you create an event.

I'm trying to write it in such a way as to be reasonably extensible and
re-usable, with an eye to making it do more later. I just had a quick
look, and I think it may be possible to either fold testcase_stats into
it, or rewrite testcase_stats to use it as a backend for at least some
stuff and simplify it. testcase_stats is written to do MW API calls
itself, which it doesn't really need to do, it could use mwclient as
relval/wikitcms does, and it can probably use some of wikitcms'
knowledge of what pages should exist for what events and so on. I do
mean to add a property of ComposeEvent() which would be the result pages
that currently actually exist for that event.

i'd be very grateful for your comments / mocking laughter ;) thanks
folks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net