Hello Per,
> Me and André Schnabel has come to the conclusion that
it might be time
> to look into our QA-Track tool and analyze if we can
make it better. If
> it can meet it's users wishes more, then it might have
a positive impact
> on the daily work.
>
for me the QA Track tool is quite important to get
information about
which localization has approved which binaries within the
last two
releases as I use it to decide on which localization has to
be built by
Sun as languagepack (if >= 80% UI has been translated) or
as full
installation set (if additionally >= 80% helpcontent has
been
translated) or if it is not built because the localization
hasn't been
updated within the last releases. And I need to know about
the QA approvals.
>
> Here are some key improvements that has been brought
up:
>
> + Make it better configurable - e.g. able to add new
languages
+1
> + A way to generate an issue, once a (or a number of)
builds gets approved.
-1
I doubt there should be an email for each build that gets
approved.
Instead there should be some kind of helper to create an
email for the
distribution approval like the distribution request in
http://www.openoffice.org/issues/show_bug.cgi?id=81693
> + A filter by release version. Means we need a function
to tell what
> version a build belongs to. E.g. all *2.3.0* belongs to
OOo 2.3.0
> codeline but some build provides may also use *OOG*.
You mean something like
2.3.0 := OOG680_m5 ?
Kind regards, Joost
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe qa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org
|