On 15 June 2011 22:32, Stew Benedict <stewbi...@gmail.com> wrote: > On 06/15/2011 09:22 AM, Stew Benedict wrote: >> >> On 06/15/2011 08:50 AM, Dexter Morgan wrote: >>> >>> On Wed, Jun 15, 2011 at 2:20 PM, Thomas Backlund<t...@mageia.org> wrote: >>>> >>>> BTW, should we have a read-only security/update-announce ml that where >>>> we >>>> mail about all updates ? >>>> >>> yes seems a must have to push updates descriptions , distributions >>> affected, ... >>> >> That is accounted for in the policy document (last line) >> > Due to the unbridled enthusiasm for getting started on updates, we now have > 4 trial packages :) > > vde2, mysql, curl, subversion > > Bugs: > > https://bugs.mageia.org/show_bug.cgi?id=1678 (vde2) > https://bugs.mageia.org/show_bug.cgi?id=1554 (mysql) > https://bugs.mageia.org/show_bug.cgi?id=1813 (curl) > https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion) > > Packages need fixes applied, built for mga1 (I believe mysql is already in > updates_testing), packager should do some initial testing then re-assign the > bug to QA > > QA process for updates: > > http://mageia.org/wiki/doku.php?id=qa_updates > > > > -- > Stew Benedict > > >
qa-bugs@ can't be be set as the assignee in bug reports, it should be made possible. The same for sec team, there should be a way to assign/put-in-CC. -- Ahmad Samir