Re: [Mageia-dev] Updates process is now available
Le mardi 19 juillet 2011 11:49:24, Samuel Verschelde a écrit : Le mardi 19 juillet 2011 11:38:01, Manuel Hiebel a écrit : Could we add a keyword validated_update to bugs that are ready to be moved to updates, so they can be found easily ? That would be useful indeed, the number of update candidates is growing and it's not easy to differentiate those who need testing and those who need to be pushed. Samuel Yep, can we add this ? No one said no, I'd say let's go :) I added the validated_update keyword to several update requests. We need to add also sysadm-b...@ml.mageia.org in CC, but there's an extension being set so that it's automatic when you add the validated_update keyword. So now we can differentiate 2 lists : - updates that need testing : http://petitlien.fr/qa-testing - updates that have been validated and need to be pushed : http://petitlien.fr/updates-push I don't think I can save and share the searches in bugzilla (or don't know how to do) so I haven't done it for now. Samuel
Re: [Mageia-dev] Updates process is now available
Le jeudi 21 juillet 2011 à 14:47 +0200, Samuel Verschelde a écrit : I don't think I can save and share the searches in bugzilla (or don't know how to do) so I haven't done it for now. Samuel You can go https://bugs.mageia.org/userprefs.cgi?tab=saved-searches I have created updates-push and waiting for qa test. -- Manuel Hiebel (leuhmanu)
Re: [Mageia-dev] Updates process is now available
Could we add a keyword validated_update to bugs that are ready to be moved to updates, so they can be found easily ? That would be useful indeed, the number of update candidates is growing and it's not easy to differentiate those who need testing and those who need to be pushed. Samuel Yep, can we add this ? -- Manuel Hiebel (leuhmanu)
Re: [Mageia-dev] Updates process is now available
Le jeudi 7 juillet 2011 14:42:18, 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 secur...@groups.mageia.org if it's a security update (check that qa-b...@ml.mageia.org is in 'CC') Let it assigned to qa-b...@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 ? That would be useful indeed, the number of update candidates is growing and it's not easy to differentiate those who need testing and those who need to be pushed. Samuel
Re: [Mageia-dev] Updates process is now available
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 secur...@groups.mageia.org if it's a security update (check that qa-b...@ml.mageia.org is in 'CC') Let it assigned to qa-b...@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 ?
Re: [Mageia-dev] Updates process is now available
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 secur...@groups.mageia.org if it's a security update (check that qa-b...@ml.mageia.org is in 'CC') Let it assigned to qa-b...@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
Re: [Mageia-dev] Updates process is now available
On Thu, 07 Jul 2011, Damien Lallement wrote: 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 secur...@groups.mageia.org if it's a security update (check that qa-b...@ml.mageia.org is in 'CC') Let it assigned to qa-b...@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). Yes, but what is the difference between pushing standard update, and security update, after qa is done, and why should we disturb them for security updates, and not for standard updates ?
Re: [Mageia-dev] Updates process is now available
On Tuesday, June 21, 2011 09:57:22 am 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 A new ML has been created: qa-b...@ml.mageia.org. It will receive all the updates requests and will be the main QA contact for bugzilla. You can join it if you want to be part of the QA people working on updates (security or not). A saved search has been added to bugzilla to catch all updates waiting for QA validation: https://bugs.mageia.org/buglist.cgi?cmdtype=runnamednamedcmd=Updates%20wai ting%20for%20QA For more info, please ask here on on #mageia-dev or #mageia-qa Let's go to work on updates! This seems not to be working for me. I am getting an error: error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=9ed21bb1-462a-4c5b-9fa3-78e433ccc363 --define section=core/updates_testing -r 114150 svn+ssh://svn.mageia.org/svn/packages/cauldron/kolab-webadmin error: svn+ssh://svn.mageia.org/svn/packages/cauldron/kolab-webadmin is not allowed for this target (BTW on the web page it shows as -define section = instead of --define section) -- Thomas
Re: [Mageia-dev] Updates process is now available
On Sun, Jun 26, 2011 at 9:39 PM, Thomas Spuhler tho...@btspuhler.com wrote: On Tuesday, June 21, 2011 09:57:22 am 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 A new ML has been created: qa-b...@ml.mageia.org. It will receive all the updates requests and will be the main QA contact for bugzilla. You can join it if you want to be part of the QA people working on updates (security or not). A saved search has been added to bugzilla to catch all updates waiting for QA validation: https://bugs.mageia.org/buglist.cgi?cmdtype=runnamednamedcmd=Updates%20wai ting%20for%20QA For more info, please ask here on on #mageia-dev or #mageia-qa Let's go to work on updates! This seems not to be working for me. I am getting an error: error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=9ed21bb1-462a-4c5b-9fa3-78e433ccc363 --define section=core/updates_testing -r 114150 svn+ssh://svn.mageia.org/svn/packages/cauldron/kolab-webadmin error: svn+ssh://svn.mageia.org/svn/packages/cauldron/kolab-webadmin is not allowed for this target (BTW on the web page it shows as -define section = instead of --define section) -- Thomas because you need to modify on the update branch of the SVN mgarepo -d 1 kolab-webadmin
[Mageia-dev] Updates process is now available
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 A new ML has been created: qa-b...@ml.mageia.org. It will receive all the updates requests and will be the main QA contact for bugzilla. You can join it if you want to be part of the QA people working on updates (security or not). A saved search has been added to bugzilla to catch all updates waiting for QA validation: https://bugs.mageia.org/buglist.cgi?cmdtype=runnamednamedcmd=Updates%20waiting%20for%20QA For more info, please ask here on on #mageia-dev or #mageia-qa Let's go to work on updates! -- Damien Lallement Treasurer of Mageia.Org twitter: damsweb - IRC: damsweb/coincoin
Re: [Mageia-dev] Updates process is now available
On Tue, Jun 21, 2011 at 06:57:22PM +0200, 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. Awesome news! A saved search has been added to bugzilla to catch all updates waiting for QA validation: https://bugs.mageia.org/buglist.cgi?cmdtype=runnamednamedcmd=Updates%20waiting%20for%20QA That link isn't working for me :-( Thanks and regards, Remmy signature.asc Description: Digital signature
Re: [Mageia-dev] Updates process is now available
Le 21/06/2011 20:19, Remco Rijnders a écrit : On Tue, Jun 21, 2011 at 06:57:22PM +0200, Damien Lallement wrote: Hello all, security, qa and sysadmin team worked on the qa/updates process to provide updates as soon as possible. Thanks to them and congrats! -- Sandro Cazzaniga - https://lederniercoupdarchet.wordpress.com IRC: Kharec (irc.freenode.net) Software/Hardware geek Conceptor Magnum's Coordinator/editor (http://magnum.tuxfamily.org) Mageia contributor
Re: [Mageia-dev] Updates process is now available
Le mardi 21 juin 2011 à 18:57 +0200, Damien Lallement a écrit : 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 the page http://www.mageia.org/wiki/doku.php?id=qa_updates It's a new package fixing a bug (security or not) or adding a missing feature. Adding a missing feature is not part of a update as we defined it so this part seems strange to me, could this one be clarified ? Don't forget to enable the i586 medias on x86_64 systems I do not understand why is should be needed ( except for nspluginwrapper ). Is there something to watch for when doing this ? Write an validation message I do not understand what is the validation message about, could we clarify the goal of the message, or add a example ? Rewrite the advisory for the secteam (ask the developper to provide the advisory if missing) IIRC, the advisory should have been provided by the packager ( according to the others page ), so why rewrite it ? Isn't it a left over ? Unless what it mean check that the packager said something that normal people will understand ? Also, on the page, developer, is upstream developer, or packager who take care of the update ? -- Michael Scherer
