[Mageia-dev] Updates process is now available

Damien Lallement dams at mageia.org
Thu Jul 7 14:46:47 CEST 2011


Le 07/07/2011 14:42, nicolas vigier a écrit :
> On Tue, 21 Jun 2011, Damien Lallement wrote:
>
>> Hello all,
>>
>> security, qa and sysadmin team worked on the qa/updates process to provide
>> updates as soon as possible.
>> All is now ready (boklm is finalizing a scrip to move updates from
>> "testing" to "updates"). This script will be uses by security team members
>> and a few QA people to push updates.
>>
>> You can now read:
>> - http://www.mageia.org/wiki/doku.php?id=updates_policy
>> - http://www.mageia.org/wiki/doku.php?id=qa_updates
>
> I have some questions about updates process :
>
> The page says to assign bug after validation :
> Assign the bug to security at groups.mageia.org if it's a security update
> (check that qa-bugs at ml.mageia.org is in 'CC')
> Let it assigned to qa-bugs at ml.mageia.org if it's a standard update
>
> Is it usefull to assign differently for security and non-security
> updates ?
>
> Could we add a keyword "validated_update" to bugs that are ready to be
> moved to updates, so they can be found easily ?

I just write this because that's what was discuss on the meeting at this 
time with misc, ennael, stew and I (you were here too IIRC).
We can discuss this point again if needed. :-)

The idea was just not to assign package to secteam if not a secteam 
update (not to distrub them for standard packages).
-- 
Damien Lallement
Treasurer of Mageia.Org

twitter: damsweb - IRC: damsweb/coincoin


More information about the Mageia-dev mailing list