[Mageia-dev] Finalizing update process

Michael Scherer misc at zarb.org
Thu Jun 9 01:08:08 CEST 2011


Le mercredi 08 juin 2011 à 18:57 +0200, Christiaan Welvaart a écrit :
> On Wed, 8 Jun 2011, Michael Scherer wrote:
> 
> > Le mercredi 08 juin 2011 à 10:40 +0200, Anne nicolas a écrit :
> >> Hi there
> >>
> >> We have some stuff to complete here:
> >> http://mageia.org/wiki/doku.php?id=security
> >>
> >> <http://mageia.org/wiki/doku.php?id=security>Can we spend the 2 or 3 coming
> >> days to finalize it and start updates submits?
> >
> > Pascal is working on this.
> >
> > So here is a proposal :
> > - anybody can submit a package to updates_testing.
> > - once submitted to testing, it should ask to QA to test, along with :
> >  - a reason for the update ( likely bug number )
> >  - potentially a priority ( ie, if this is just a translation update or
> > a urgent 0 day exploit )
> >  - a way to test the bug and see it is fixed
> >  - text for the update
> 
> > - qa validate the update ( with process to define )
> 
> > - someone move the package from updates_testing to testing
> 
> Someone from security (stable updates) team I guess?

Someone who type the command would be a admin ( until someone decide to
write a script for that, and to plug it to the current restricted shell
framework ).

Who decide exactly what should og or not is open. IE, that the part of
the process to define.

-- 
Michael Scherer



More information about the Mageia-dev mailing list