Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
Matt Riedemann mrie...@linux.vnet.ibm.com wrote on 07/14/2015 07:28:45 PM: From: Matt Riedemann mrie...@linux.vnet.ibm.com To: openstack-dev@lists.openstack.org Date: 07/14/2015 07:40 PM Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem? [...] Markus, Since you'll be at the meetup next week how about you throw something into the etherpad [1] about this so we can discuss details there. [1] https://etherpad.openstack.org/p/liberty-nova-midcycle -- Thanks, Matt Riedemann Sure. I've added it as Bug management - automatize bug cleanup. Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
Markus Zoeller/Germany/IBM@IBMDE wrote on 07/10/2015 03:55 [...] So you have a bunch of bugs that are Confirmed (or Triaged) + an assignee set. I would argue that you need to separate two cases: the bug had no activity for the last 60 days: assignee should be removed the bug had activity in the last 60 days: status should be in progress otherwise you further hide the fact that the bug is abandoned by setting status in addition to the assignee. Cheers, -- Thierry Carrez (ttx) Right. My first intention was to switch all to in progress and then switch a subset of that back to the previous status, depending on their activity. I see now that this would cause confusion. I'll process them seperately like Thierry suggested to avoid that confusion. I'll announce the expected changes in the next days before I actually execute them. Regards, Markus Zoeller (markus_z) Here are the numbers. From the currently 215 Confirmed and Triaged bugs which have an assignee (= inconsistency), there are: active inactive - Triaged 4 5 Confirmed57 149 active = there is a comment within the last 60 days in Launchpad - or - the bug mentions at least one patch set in gerrit which is * under review * verified by Jenkins * and without negative code reviews (older than 28 days) inactive = the last update of the bug is older than 60 days - and - the bug mentions no active patch sets or only patch sets which have -1s which are not addressed for 28 days. I'm not sure why the number of the inactive confirmed bugs is so big. Could it be that this is a way to bookmark bugs where one wants to work on in the future? Below are the details of the Confirmed and Triaged bugs which would be affected as soon as I run the mentioned script in 'active' mode. Maybe a short note why I think that this could improve Nova: I assume that the average turnaround time of the bugs, from their creation until they get closed with appropriate patch sets, can be decreased if the 'stale' bugs get a regular cleanup to enable other contributers to work on them. I'll wait a week until I execute this to give you some time to speak up. Details: Legend: --- =In Progress: Switch the status of the bug to In Progress -Assignee: Remove the current assignee Age : Days since the last update (in LP or Gerrit) Patch Set ...: A summary of a patch set in Gerrit. Constructed as: [review-id] (+2s +1s -1s -2s) (G:Jenkins Vote W:Workflow Flag) last update in days === CleanUpReport(9 Items): 'Triaged' bugs with an assignee === Bug ID Title Age Contributer Cleanup Action --- 1467409 HyperV destroy vm fails on Wi[...] 21 Adelina Tuve =In Progress 1177570 Hyper-V tests can be refactor[...] 368 Alessandro P -Assignee 1355171 Can not have IPv4 or IPv6 onl[...] 91 Chris Gacsal -Assignee 1412480 Hyper-V: Instance booted from[...] 175 Claudiu Belu -Assignee 1458013 ec2 code uses requests to tal[...] 29 Deepti Ramak =In Progress 1436079 There is no API samples funct[...] 103 Eli Qiao -Assignee 1458934 Ironic: heavy polling 25 Lucas Alvare =In Progress 1441361 Don't trace on InstanceInfoCa[...] 96 Matt Riedema -Assignee 1415087 [OSSA 2015-011] Format-guessi[...] 7 Tony Breeds =In Progress --- 4 x =In Progress 5 x -Assignee === === CleanUpReport(206 Items): 'Confirmed' bugs with an assignee === Bug ID Title Age Contributer Cleanup Action --- 1309184 nova should delete neutron po[...] 305 Aaron Rosen -Assignee 1265447 floating-ip-bulk-delete metho[...] 151 Abhishek Tal -Assignee 1301368 Hyper-V configdrive is not at[...] 105 Adrian Vladu -Assignee 1335784 remove secgroup rule won't cu[...] 305 Akash Gangil -Assignee 1153842 nova volume-attach vmid vo[...] 500 Alessandro P -Assignee 1408176 Nova instance not boot after [...] 26 Alex Xu =In Progress 1301532 Quotas can be exceeded by mak[...] 90 Alex Xu -Assignee Patch Set: [110863] (2 1 0 0) (G:0 W:None) age(d):341 - MERGED 1443494 Return supported micro-versio[...] 69 Alex Xu -Assignee 1253571
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
On 7/14/2015 5:51 AM, Markus Zoeller wrote: Markus Zoeller/Germany/IBM@IBMDE wrote on 07/10/2015 03:55 [...] So you have a bunch of bugs that are Confirmed (or Triaged) + an assignee set. I would argue that you need to separate two cases: the bug had no activity for the last 60 days: assignee should be removed the bug had activity in the last 60 days: status should be in progress otherwise you further hide the fact that the bug is abandoned by setting status in addition to the assignee. Cheers, -- Thierry Carrez (ttx) Right. My first intention was to switch all to in progress and then switch a subset of that back to the previous status, depending on their activity. I see now that this would cause confusion. I'll process them seperately like Thierry suggested to avoid that confusion. I'll announce the expected changes in the next days before I actually execute them. Regards, Markus Zoeller (markus_z) Here are the numbers. From the currently 215 Confirmed and Triaged bugs which have an assignee (= inconsistency), there are: active inactive - Triaged 4 5 Confirmed57 149 active = there is a comment within the last 60 days in Launchpad - or - the bug mentions at least one patch set in gerrit which is * under review * verified by Jenkins * and without negative code reviews (older than 28 days) inactive = the last update of the bug is older than 60 days - and - the bug mentions no active patch sets or only patch sets which have -1s which are not addressed for 28 days. I'm not sure why the number of the inactive confirmed bugs is so big. Could it be that this is a way to bookmark bugs where one wants to work on in the future? Below are the details of the Confirmed and Triaged bugs which would be affected as soon as I run the mentioned script in 'active' mode. Maybe a short note why I think that this could improve Nova: I assume that the average turnaround time of the bugs, from their creation until they get closed with appropriate patch sets, can be decreased if the 'stale' bugs get a regular cleanup to enable other contributers to work on them. I'll wait a week until I execute this to give you some time to speak up. Details: Legend: --- =In Progress: Switch the status of the bug to In Progress -Assignee: Remove the current assignee Age : Days since the last update (in LP or Gerrit) Patch Set ...: A summary of a patch set in Gerrit. Constructed as: [review-id] (+2s +1s -1s -2s) (G:Jenkins Vote W:Workflow Flag) last update in days === CleanUpReport(9 Items): 'Triaged' bugs with an assignee === Bug ID Title Age Contributer Cleanup Action --- 1467409 HyperV destroy vm fails on Wi[...] 21 Adelina Tuve =In Progress 1177570 Hyper-V tests can be refactor[...] 368 Alessandro P -Assignee 1355171 Can not have IPv4 or IPv6 onl[...] 91 Chris Gacsal -Assignee 1412480 Hyper-V: Instance booted from[...] 175 Claudiu Belu -Assignee 1458013 ec2 code uses requests to tal[...] 29 Deepti Ramak =In Progress 1436079 There is no API samples funct[...] 103 Eli Qiao -Assignee 1458934 Ironic: heavy polling 25 Lucas Alvare =In Progress 1441361 Don't trace on InstanceInfoCa[...] 96 Matt Riedema -Assignee 1415087 [OSSA 2015-011] Format-guessi[...] 7 Tony Breeds =In Progress --- 4 x =In Progress 5 x -Assignee === === CleanUpReport(206 Items): 'Confirmed' bugs with an assignee === Bug ID Title Age Contributer Cleanup Action --- 1309184 nova should delete neutron po[...] 305 Aaron Rosen -Assignee 1265447 floating-ip-bulk-delete metho[...] 151 Abhishek Tal -Assignee 1301368 Hyper-V configdrive is not at[...] 105 Adrian Vladu -Assignee 1335784 remove secgroup rule won't cu[...] 305 Akash Gangil -Assignee 1153842 nova volume-attach vmid vo[...] 500 Alessandro P -Assignee 1408176 Nova instance not boot after [...] 26 Alex Xu =In Progress 1301532 Quotas can be exceeded by mak[...] 90 Alex Xu -Assignee Patch Set: [110863] (2 1 0 0) (G:0 W:None) age(d):341 - MERGED 1443494 Return supported micro-versio[...] 69 Alex Xu -Assignee 1253571 libivrt+xen
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
On 07/10/2015 04:09 AM, Markus Zoeller wrote: I'd like to switch the status of ~200 bugs at once to adjust the bookkeeping in LaunchPad. This will concern Confirmed and Triaged bugs which have an assignee [1]. AFAIK they should be In Progress. I'm concerned if this would affect some reports I'm not aware of in a bad way. So, if you think this is a bad thing, please speak up. FWIW, I'll use an enhanced version of [2] which I will provide in the next days. A few days later I'll have a version ready which can update stale In Progress bugs by querying Gerrit. [1] http://bit.ly/1GbhJWu [2] https://review.openstack.org/#/c/197060/ I would not do that. Bugs with assignee tend to get ignored by other people looking at the problem, and in *most* cases the assignee is not actually working on the bug. I would instead go the other direction and pop any In Progress bug that has seen no activity in the last 60 days back to Confirmed. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
+1 On 7/10/15, 1:32 PM, Sean Dague s...@dague.net wrote: On 07/10/2015 04:09 AM, Markus Zoeller wrote: I'd like to switch the status of ~200 bugs at once to adjust the bookkeeping in LaunchPad. This will concern Confirmed and Triaged bugs which have an assignee [1]. AFAIK they should be In Progress. I'm concerned if this would affect some reports I'm not aware of in a bad way. So, if you think this is a bad thing, please speak up. FWIW, I'll use an enhanced version of [2] which I will provide in the next days. A few days later I'll have a version ready which can update stale In Progress bugs by querying Gerrit. [1] https://urldefense.proofpoint.com/v2/url?u=http-3A__bit.ly_1GbhJWud=BQIC Agc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYB k8YTeq9N3-diTlNj4GyNcm=l81nvT6_KcJY11CmckP4tRUoT25Y8Hn7zMMGBuD2vC8s=0Jw 7eQetRMf4t5LhJi52-n_tjW5h71s56yiu-UO6eh4e= [2] https://review.openstack.org/#/c/197060/ I would not do that. Bugs with assignee tend to get ignored by other people looking at the problem, and in *most* cases the assignee is not actually working on the bug. I would instead go the other direction and pop any In Progress bug that has seen no activity in the last 60 days back to Confirmed. -Sean -- Sean Dague https://urldefense.proofpoint.com/v2/url?u=http-3A__dague.netd=BQICAgc=S qcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9 N3-diTlNj4GyNcm=l81nvT6_KcJY11CmckP4tRUoT25Y8Hn7zMMGBuD2vC8s=8XJOGkHSUvo Uv8dQrHymUt_XXKtMf0hpWsKYuUzoWnse= __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
On 07/10/2015 09:34 AM, Markus Zoeller wrote: Sean Dague s...@dague.net wrote on 07/10/2015 12:32:00 PM: From: Sean Dague s...@dague.net To: openstack-dev@lists.openstack.org Date: 07/10/2015 12:32 PM Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem? On 07/10/2015 04:09 AM, Markus Zoeller wrote: I'd like to switch the status of ~200 bugs at once to adjust the bookkeeping in LaunchPad. This will concern Confirmed and Triaged bugs which have an assignee [1]. AFAIK they should be In Progress. I'm concerned if this would affect some reports I'm not aware of in a bad way. So, if you think this is a bad thing, please speak up. FWIW, I'll use an enhanced version of [2] which I will provide in the next days. A few days later I'll have a version ready which can update stale In Progress bugs by querying Gerrit. [1] http://bit.ly/1GbhJWu [2] https://review.openstack.org/#/c/197060/ I would not do that. Bugs with assignee tend to get ignored by other people looking at the problem, and in *most* cases the assignee is not actually working on the bug. I would instead go the other direction and pop any In Progress bug that has seen no activity in the last 60 days back to Confirmed. -Sean The bugs I'm referring to are *not* set to In Progress but have an assignee. I think this is an inconsistency which I try to resolve. I can treat them like In Progress bugs and remove the assignee if there is no activity in the last 60 days. Is this what you say? Right, that's what I'm saying. Removing the assignee is typically the resolution to these when I've processed them manually, because they are old, and no one is working on it. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
Markus Zoeller wrote: The bugs I'm referring to are *not* set to In Progress but have an assignee. I think this is an inconsistency which I try to resolve. I can treat them like In Progress bugs and remove the assignee if there is no activity in the last 60 days. Is this what you say? So you have a bunch of bugs that are Confirmed (or Triaged) + an assignee set. I would argue that you need to separate two cases: the bug had no activity for the last 60 days: assignee should be removed the bug had activity in the last 60 days: status should be in progress otherwise you further hide the fact that the bug is abandoned by setting status in addition to the assignee. Cheers, -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
Sean Dague s...@dague.net wrote on 07/10/2015 12:32:00 PM: From: Sean Dague s...@dague.net To: openstack-dev@lists.openstack.org Date: 07/10/2015 12:32 PM Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem? On 07/10/2015 04:09 AM, Markus Zoeller wrote: I'd like to switch the status of ~200 bugs at once to adjust the bookkeeping in LaunchPad. This will concern Confirmed and Triaged bugs which have an assignee [1]. AFAIK they should be In Progress. I'm concerned if this would affect some reports I'm not aware of in a bad way. So, if you think this is a bad thing, please speak up. FWIW, I'll use an enhanced version of [2] which I will provide in the next days. A few days later I'll have a version ready which can update stale In Progress bugs by querying Gerrit. [1] http://bit.ly/1GbhJWu [2] https://review.openstack.org/#/c/197060/ I would not do that. Bugs with assignee tend to get ignored by other people looking at the problem, and in *most* cases the assignee is not actually working on the bug. I would instead go the other direction and pop any In Progress bug that has seen no activity in the last 60 days back to Confirmed. -Sean The bugs I'm referring to are *not* set to In Progress but have an assignee. I think this is an inconsistency which I try to resolve. I can treat them like In Progress bugs and remove the assignee if there is no activity in the last 60 days. Is this what you say? Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?
Thierry Carrez thie...@openstack.org wrote on 07/10/2015 03:43:06 PM: From: Thierry Carrez thie...@openstack.org To: openstack-dev@lists.openstack.org Date: 07/10/2015 03:43 PM Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem? Markus Zoeller wrote: The bugs I'm referring to are *not* set to In Progress but have an assignee. I think this is an inconsistency which I try to resolve. I can treat them like In Progress bugs and remove the assignee if there is no activity in the last 60 days. Is this what you say? So you have a bunch of bugs that are Confirmed (or Triaged) + an assignee set. I would argue that you need to separate two cases: the bug had no activity for the last 60 days: assignee should be removed the bug had activity in the last 60 days: status should be in progress otherwise you further hide the fact that the bug is abandoned by setting status in addition to the assignee. Cheers, -- Thierry Carrez (ttx) Right. My first intention was to switch all to in progress and then switch a subset of that back to the previous status, depending on their activity. I see now that this would cause confusion. I'll process them seperately like Thierry suggested to avoid that confusion. I'll announce the expected changes in the next days before I actually execute them. Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
