On Nov 11, 2013 1:52 AM, "Denis Silakov" <[email protected]> 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
Ok > > QA constantly monitors bugzilla for bugs with "qa_verified" set to "?", publishers monitors it for bugs with "published" flag set to "?". Ah, I see how it is. I already have an updatereq flag and more than likely can probably do a published flag as well... I'm just hoping if there was a more automated way. I know that ABF has the APIs to do them, I just want to take advantage of them. Especially the new testing repo functionality. Robert
