Excerpts from Jeremy Stanley's message of 2017-10-11 16:29:31 +0000: > On 2017-10-11 12:05:33 -0400 (-0400), Doug Hellmann wrote: > [...] > > We have a bunch of open bugs. It would be good to triage those to see > > which, if any, need to be migrated. > [...] > > Well, they'll all be migrated (whether open or closed), but closing > them in LP where possible will reduce the risk that people continue > trying to update them there later.
Oh, nice, I didn't realize all of the bugs would be copied over. Triaging will still help clean up the active items, but I don't think it's a blocker. > > Unfortunately the degree to which bug handling can be disabled in LP > is somewhat lacking if you want to still have old bugs archived > there (so that existing links on mailing lists and such continue > working). You can disable reporting new bugs and hide links to the > bug tracker from the project page on LP, but bugs can still get > updated there. We've talked about the possibility for a bug-spammer > that adds a comment to and closes all LP bugs on a project pointing > to the corresponding URLs of imported SB stories. However, as you > know, dealing with API timeouts for LP is sort of un-fun so this > may be a foolish idea. Commenting on bugs seems to trigger the timeout less often than trying to update some of the metadata. At least that's what I think we've found with the release tools. It's also safe to ignore the timeout errors in this case, I think. On the other hand, I think just closing down the tracker is probably sufficient. It's not like we have lots of people commenting on pbr bugs right now. Doug __________________________________________________________________________ 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