Hi All,
I'm actually working on a system that does this within bugzilla and will
ultimately provide for automatic release of updates when a high enough level of
package approval has been reached. It uses the flag system of Bugzilla but uses
a controlled voting system. I have to confess though to struggling with the
perl but I am progressing with it albeit slowly!!
I feel as clearly ROSA does that this is a good solution .
Best,
Colin
Colin Close
QA TEAM
On Monday 11 November 2013 10:52:48 Denis Silakov wrote:
> On 11/10/2013 09:15 AM, Robert Xu wrote:
> > In fact, I think it might be a good idea to turn Publication without
> > QA off for openmandriva2013.0 now, and give the ability to
> > publish/reject to QA (I don't know if ABF has this ability, or should
> > I write a separate QA website that uses the API, or...?)
>
> In ROSA, we just restrict publishing permission for the 'main' repo of
> released branches to a limited group of people ('contrib' is open for
> all, since we provide almost no guarantees for it). If we need to update
> a package, we create a bug in bugzilla, QA verifies it and if everything
> is ok somebody with necessary permissions publish the package. We have
> additional support for this workflow in our bugzilla - "qa_verified" and
> "published" flags. E.g., like here:
> http://bugs.rosalinux.ru/show_bug.cgi?id=3099
>
> QA constantly monitors bugzilla for bugs with "qa_verified" set to "?",
> publishers monitors it for bugs with "published" flag set to "?".
>
>
