[Mageia-dev] Bugzilla mass ping: continued
Hi everyone, a little over 2 weeks ago, when cauldron equalled Mageia 2, so there wasn't a real cauldron, I did a mass ping for almost all cauldron bugs (except package requests) to ask whether they were still valid for Mageia 2. Most, if not all, of the following bugs were pinged then, but there seems not to have been a reply. However, there are too many of them for me to check: https://bugs.mageia.org/buglist.cgi?negate0=1&keywords=NEEDINFO&chfieldto=2012-05-27&query_format=advanced&keywords_type=allwords&chfieldfrom=2012-05-26&field0-0-0=status_whiteboard&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&version=Cauldron&type0-0-0=substring&value0-0-0=MGA2TOO&product=Mageia If you know about any of those bugs that it got solved, please make a comment in it and close it as RESOLVED - FIXED If you know the bug is still there in Mageia 2 and/or current cauldron: Please make a comment that the bug is still valid and * remove the "NEEDINFO" keyword * put "MGA2TOO" on the whiteboard if it exists in Mageia 2 *and* cauldron * change version to "2" if you know it was recently solved for cauldron, but not yet for "2" Thanks in advance, Marja
Re: [Mageia-dev] Bugzilla mass ping
On Wed, May 30, 2012 at 08:08:30AM +0300, Sander Lepik wrote: > With new bugzilla we should be able to choose multiple versions. And we can > use keywords to > handle them. For example: tested_mgaX_arch -> validate_update_mgaX -> > update_pushed_mgaX. Normally you'd use flags for this. You can setup flags that it automatically goes to a few people when it is requested, etc. The UI is confusing though (IMO). -- Regards, Olav
Re: [Mageia-dev] Bugzilla mass ping
On 30/05/12 06:08, Sander Lepik wrote: 30.05.2012 05:14, blind Pete kirjutas: Would it be possible to have a bug report refer to multiple versions and simultaneously have X marked as OLD, Y marked as FIXED, and Z marked as BLOCKING? With new bugzilla we should be able to choose multiple versions. And we can use keywords to handle them. For example: tested_mgaX_arch -> validate_update_mgaX -> update_pushed_mgaX. -- Sander QA will still need two bugs though for updates (one for each release), we have no plans to incorporate those keywords into our workflow. It would make the validation process too confused and lead to errors. Claire
Re: [Mageia-dev] Bugzilla mass ping
30.05.2012 05:14, blind Pete kirjutas: > Would it be possible to have a bug report refer to multiple versions > and simultaneously have X marked as OLD, Y marked as FIXED, and > Z marked as BLOCKING? With new bugzilla we should be able to choose multiple versions. And we can use keywords to handle them. For example: tested_mgaX_arch -> validate_update_mgaX -> update_pushed_mgaX. -- Sander
Re: [Mageia-dev] Bugzilla mass ping
nicolas vigier wrote: [snip] > The way I see it, the bug should be fixed first in Cauldron, because > it's the developement version. And when it is confirmed that the fix is > good, it is applied to all affected stable versions. That would depend on whether the bug was an annoyance or a show stopping urgent security fix. [snip] > I think spamming people with multiple bugs for the same issue only > increase the chances of people ignoring bugzilla emails. > > It also makes it difficult to read all infos about the bugs, some infos > will be in the bug for Mageia 2, other infos will be in the Cauldron > bug. > > In my opinion we should have only one bug for an issue, with keyword or > comments to indicate that it also affect other versions. And only when a > solution is found, the bug is forked for each release to track the > upload and QA tests. Would it be possible to have a bug report refer to multiple versions and simultaneously have X marked as OLD, Y marked as FIXED, and Z marked as BLOCKING? -- blind Pete Sig goes here...
Re: [Mageia-dev] Bugzilla mass ping
On Mon, 28 May 2012, Samuel Verschelde wrote: > Le samedi 26 mai 2012 14:52:53, nicolas vigier a écrit : > > On Sat, 26 May 2012, Marja van Waes wrote: > > > On 26-05-12 13:23, Anne Nicolas wrote: > > >> Well rather than that it should be switched to Cauldron > > > > > > According to > > > https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_rel > > > eases.21_What_now.3F we should clone the still valid cauldron bugs for > > > Mageia 2, and the cauldron bug should then be set to block the same bug > > > in Mageia 2. > > > > That's a lot of bugs to clone. Instead of cloning every bugs, I would > > rather set bugs to Cauldron, and when someone fix a cauldron bug he > > should decide whether it's something worth fixing in Mageia 2 or not, > > and open a Mageia 2 bug if necessary. > > The way I see it, a cauldron bug has a lower priority than a Mageia 1 or 2 > bug, since the cauldron bug must be fixed before Mageia 3, whereas users > already actually use Mageia 1 and Mageia 2 and can be affected by the bug. The way I see it, the bug should be fixed first in Cauldron, because it's the developement version. And when it is confirmed that the fix is good, it is applied to all affected stable versions. > > So if creating actual bug reports for Mageia 2 would increase the chance for > the bug to be taken care of, I would still favor cloning every open still > valid bug in Mageia 2. I think spamming people with multiple bugs for the same issue only increase the chances of people ignoring bugzilla emails. It also makes it difficult to read all infos about the bugs, some infos will be in the bug for Mageia 2, other infos will be in the Cauldron bug. In my opinion we should have only one bug for an issue, with keyword or comments to indicate that it also affect other versions. And only when a solution is found, the bug is forked for each release to track the upload and QA tests.
Re: [Mageia-dev] Bugzilla mass ping
On Tue, May 29, 2012 at 09:36:51AM +0300, Sander Lepik wrote: > 29.05.2012 00:36, Olav Vitters kirjutas: > >If filed before, I assume it'll of course affect Mageia 2. > If it's installer bug then it can't affect Mageia 2 anymore. > > I prefer > >either setting version or target milestone to lowest Mageia version in > >which the bug should be fixed. > Setting milestone to lowest version doesn't sound good either. That > milestone is passed - what's the point? For installer or in general? I'm focussed about GNOME, for that target milestone is perfectly fine.. because updates can be made. There are still a bunch of bugs I haven't gotten around to unfortunately. -- Regards, Olav
Re: [Mageia-dev] Bugzilla mass ping
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > As i already said, there is no point to clone installer bugs. Just > extra work and we don't have that many people in QA. And later result is that we're going to fix as OLD ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/Eb7wACgkQqEs9DA4DquAmfQCfZjVqTdrZa0w6XN8rFyXjC9An ePEAn1HpWusm7WhlSxIWzJMnkq88Ob3w =GHBM -END PGP SIGNATURE-
Re: [Mageia-dev] Bugzilla mass ping
29.05.2012 00:36, Olav Vitters kirjutas: If filed before, I assume it'll of course affect Mageia 2. If it's installer bug then it can't affect Mageia 2 anymore. I prefer either setting version or target milestone to lowest Mageia version in which the bug should be fixed. Setting milestone to lowest version doesn't sound good either. That milestone is passed - what's the point? Even when having two: We just branched, I prefer if all current bugs are assumed to be Mageia 2 ones with the Cauldron still not reported. As i already said, there is no point to clone installer bugs. Just extra work and we don't have that many people in QA. -- Sander
Re: [Mageia-dev] Bugzilla mass ping
29.05.2012 00:07, Samuel Verschelde kirjutas: MGA2TOO on the whiteboard could be enough maybe, provided packagers actually know how to use it (it means that a search for MGA2 bugs must take into account both those set to MGA2 and those with the MGA2TOO text in whiteboard), but it will make statistics harder to build. Samuel MGA2TOO is temporary solution. When we get new bugzilla we can choose multiple affected versions. So lets just hope that new bugzilla won't take too much time. -- Sander
Re: [Mageia-dev] Bugzilla mass ping
On Sat, May 26, 2012 at 02:34:22PM +0200, Marja van Waes wrote: > On 26-05-12 13:23, Anne Nicolas wrote: > > > > >Well rather than that it should be switched to Cauldron > > > > According to > https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F > we should clone the still valid cauldron bugs for Mageia 2, and the > cauldron bug should then be set to block the same bug in Mageia 2. If filed before, I assume it'll of course affect Mageia 2. I prefer either setting version or target milestone to lowest Mageia version in which the bug should be fixed. Even when having two: We just branched, I prefer if all current bugs are assumed to be Mageia 2 ones with the Cauldron still not reported. -- Regards, Olav
Re: [Mageia-dev] Bugzilla mass ping
On 26/05/12 12:20, Marja van Waes wrote: I plan to do a mass ping today, because we need to find out whether they are still valid for Mageia 2 Thanks, I think it is good idea, let's make mga2 almost bugfree before making Cauldron bugfull ;)
Re: [Mageia-dev] Bugzilla mass ping
Le samedi 26 mai 2012 14:52:53, nicolas vigier a écrit : > On Sat, 26 May 2012, Marja van Waes wrote: > > On 26-05-12 13:23, Anne Nicolas wrote: > >> Well rather than that it should be switched to Cauldron > > > > According to > > https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_rel > > eases.21_What_now.3F we should clone the still valid cauldron bugs for > > Mageia 2, and the cauldron bug should then be set to block the same bug > > in Mageia 2. > > That's a lot of bugs to clone. Instead of cloning every bugs, I would > rather set bugs to Cauldron, and when someone fix a cauldron bug he > should decide whether it's something worth fixing in Mageia 2 or not, > and open a Mageia 2 bug if necessary. The way I see it, a cauldron bug has a lower priority than a Mageia 1 or 2 bug, since the cauldron bug must be fixed before Mageia 3, whereas users already actually use Mageia 1 and Mageia 2 and can be affected by the bug. So if creating actual bug reports for Mageia 2 would increase the chance for the bug to be taken care of, I would still favor cloning every open still valid bug in Mageia 2. MGA2TOO on the whiteboard could be enough maybe, provided packagers actually know how to use it (it means that a search for MGA2 bugs must take into account both those set to MGA2 and those with the MGA2TOO text in whiteboard), but it will make statistics harder to build. Samuel
Re: [Mageia-dev] Bugzilla mass ping
On 26-05-12 14:52, nicolas vigier wrote: On Sat, 26 May 2012, Marja van Waes wrote: On 26-05-12 13:23, Anne Nicolas wrote: Well rather than that it should be switched to Cauldron According to https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F we should clone the still valid cauldron bugs for Mageia 2, and the cauldron bug should then be set to block the same bug in Mageia 2. That's a lot of bugs to clone. Instead of cloning every bugs, I would rather set bugs to Cauldron, and when someone fix a cauldron bug he should decide whether it's something worth fixing in Mageia 2 or not, and open a Mageia 2 bug if necessary. AL13N suggested to set a ALSO_MGA2 keyword for those bugs (so leave them to cauldron) instead of cloning them. We don't have such a keyword atm, but I'll use MGA2TOO on the whiteboard instead for now. That might change, depending on what leuhmanu, remmy and other bug squad members think about it. They might have an even better idea :)
Re: [Mageia-dev] Bugzilla mass ping
On 2012/05/26 16:14 (GMT+0300) Jani Välimaa composed: On 26.05.2012 15:52, nicolas vigier wrote: On Sat, 26 May 2012, Marja van Waes wrote: According to https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F we should clone the still valid cauldron bugs for Mageia 2, and the cauldron bug should then be set to block the same bug in Mageia 2. That's a lot of bugs to clone. Instead of cloning every bugs, I would rather set bugs to Cauldron, and when someone fix a cauldron bug he should decide whether it's something worth fixing in Mageia 2 or not, and open a Mageia 2 bug if necessary. +1 +2 It's particularly nuts to demand a bug confirmation of a bug filed on RC, less than two weeks old, where the bug has had no activity since being filed and little likelihood of having been addressed so close to a release. Bugs don't magically get fixed just by virtue of a release or name change. BTW, the mirror I checked still has Cauldron. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] Bugzilla mass ping
On 26.05.2012 15:52, nicolas vigier wrote: > On Sat, 26 May 2012, Marja van Waes wrote: > >> On 26-05-12 13:23, Anne Nicolas wrote: >> >>> >>> Well rather than that it should be switched to Cauldron >>> >> >> According to >> https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F >> we should clone the still valid cauldron bugs for Mageia 2, and the >> cauldron bug should then be set to block the same bug in Mageia 2. > > That's a lot of bugs to clone. Instead of cloning every bugs, I would > rather set bugs to Cauldron, and when someone fix a cauldron bug he > should decide whether it's something worth fixing in Mageia 2 or not, > and open a Mageia 2 bug if necessary. > +1
Re: [Mageia-dev] Bugzilla mass ping
On Sat, 26 May 2012, Marja van Waes wrote: > On 26-05-12 13:23, Anne Nicolas wrote: > >> >> Well rather than that it should be switched to Cauldron >> > > According to > https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F > we should clone the still valid cauldron bugs for Mageia 2, and the > cauldron bug should then be set to block the same bug in Mageia 2. That's a lot of bugs to clone. Instead of cloning every bugs, I would rather set bugs to Cauldron, and when someone fix a cauldron bug he should decide whether it's something worth fixing in Mageia 2 or not, and open a Mageia 2 bug if necessary.
Re: [Mageia-dev] Bugzilla mass ping
Claire Robinson a écrit : > On 26/05/12 11:20, Marja van Waes wrote: >> Hi everyone, >> >> We have very many Cauldron bugs that aren't listed as package requests. >> >> https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=matches&component=Installer&component=RPM%20Packages&component=Release%20%28media%20or%20process%29&component=Security&product=Mageia >> >> >> >> I plan to do a mass ping today, because we need to find out whether they >> are still valid for Mageia 2 >> >> Cheers, >> Marja >> > > My inbox just went crazy :\ > > Claire > Mine too :( Sigmund would have called that "Fehlleistung" (acte manqué... ou gaffe en français ) (parapraxis or blunder in English) ;) I need a vacuum cleaner
Re: [Mageia-dev] Bugzilla mass ping
On 26-05-12 13:23, Anne Nicolas wrote: Well rather than that it should be switched to Cauldron According to https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F we should clone the still valid cauldron bugs for Mageia 2, and the cauldron bug should then be set to block the same bug in Mageia 2. Cheers, marja
Re: [Mageia-dev] Bugzilla mass ping
Le samedi 26 mai 2012 12:22:09 Claire Robinson a écrit : > On 26/05/12 11:20, Marja van Waes wrote: > > Hi everyone, > > > > We have very many Cauldron bugs that aren't listed as package requests. > > > > https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&; > > query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASS > > IGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=m > > atches&component=Installer&component=RPM%20Packages&component=Release%20%2 > > 8media%20or%20process%29&component=Security&product=Mageia > > > > > > I plan to do a mass ping today, because we need to find out whether they > > are still valid for Mageia 2 > > > > Cheers, > > Marja > > My inbox just went crazy :\ > > Claire +1 :) Apparently the automatic filtering if kmail don't like these too much :p Sometimes I must redo a manual filtering for the forgotten ones in the inbox dir :)
Re: [Mageia-dev] Bugzilla mass ping
Le 26 mai 2012 13:22, "Claire Robinson" a écrit : > > On 26/05/12 11:20, Marja van Waes wrote: >> >> Hi everyone, >> >> We have very many Cauldron bugs that aren't listed as package requests. >> >> https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=matches&component=Installer&component=RPM%20Packages&component=Release%20%28media%20or%20process%29&component=Security&product=Mageia >> >> >> I plan to do a mass ping today, because we need to find out whether they >> are still valid for Mageia 2 >> >> Cheers, >> Marja >> > > My inbox just went crazy :\ > > Claire Mine too :)
Re: [Mageia-dev] Bugzilla mass ping
Le 26/05/2012 13:22, Claire Robinson a écrit : On 26/05/12 11:20, Marja van Waes wrote: Hi everyone, We have very many Cauldron bugs that aren't listed as package requests. https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=matches&component=Installer&component=RPM%20Packages&component=Release%20%28media%20or%20process%29&component=Security&product=Mageia I plan to do a mass ping today, because we need to find out whether they are still valid for Mageia 2 Cheers, Marja My inbox just went crazy :\ Claire Well rather than that it should be switched to Cauldron -- http://mageia.org
Re: [Mageia-dev] Bugzilla mass ping
On 26/05/12 11:20, Marja van Waes wrote: Hi everyone, We have very many Cauldron bugs that aren't listed as package requests. https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=matches&component=Installer&component=RPM%20Packages&component=Release%20%28media%20or%20process%29&component=Security&product=Mageia I plan to do a mass ping today, because we need to find out whether they are still valid for Mageia 2 Cheers, Marja My inbox just went crazy :\ Claire
[Mageia-dev] Bugzilla mass ping
Hi everyone, We have very many Cauldron bugs that aren't listed as package requests. https://bugs.mageia.org/buglist.cgi?order=Importance&field0-0-0=component&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&version=Cauldron&type0-0-0=matches&component=Installer&component=RPM%20Packages&component=Release%20%28media%20or%20process%29&component=Security&product=Mageia I plan to do a mass ping today, because we need to find out whether they are still valid for Mageia 2 Cheers, Marja
