Lars Wirzenius wrote:
Is there a list of what QA activites are being done, and by whom? I've
heard, for example, that some people test building of packages in
testing to find FTBFS errors that happen after the package has already
entered testing, or to find missing build dependencies. I also know that
some other people than me are or were running piuparts on packages.
It would be nice to have a list of these, and maybe have a more
concerted and organized QA effort.
I doubt that there's a list, but we can start one right now in our
wiki. By the way, i'll say what i'm doing right now:
I think someone told you already about my piupartme python code, that
is still in early stages of development but aims to run piuparts against
packages and keep track of the versions to avoid do the same thing two
times. It uses a 'maybe-failed', 'maybe-succesful' structure that i plan
to publish in the web.
I don't have resources to keep piupartme for Debian but someone wants to
run it against Ubuntu universe packages.
I hacked beagle a bit and i want to run my customized package (for tests)
against all the Debian source packages. The plan is test against uncompressed
ones first and maybe in the future avoid the uncompress step. I told Joerg
about this project, the plan is focus on seek for licensing issues in the
archive first. The next step should publish a web search, extending
packages.d.o (no jokes, please) but who knows.
Suggestions, bandwidth, cpu cycles and disk space are welcome.
Thanks,
Gustavo Franco
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
