On Tue, May 24, 2016 at 11:00:35AM +0200, Markus Zoeller wrote: > On 24.05.2016 09:34, Duncan Thomas wrote: > > Cinder bugs list was far more manageable once this had been done. > > > > It is worth sharing the tool for this? I realise it's fairly trivial to > > write one, but some standardisation on the comment format etc seems > > valuable, particularly for Q/A folks who work between different projects. > > A first draft (without the actual expiring) is at [1]. I'm going to > finish it this week. If there is a place in an OpenStack repo, just give > me a pointer and I'll push a change.
FWIW I had to do a similar thing recently when I set all TripleO bugs reported pre-liberty Incomplete - I ended up hacking up process_bugs.py from release-tools: https://github.com/openstack-infra/release-tools/blob/master/process_bugs.py Perhaps we can adapt one of the scripts there (or add a new one if needed) that can be used for several projects? Here's a diff of my hacked-up version FWIW (I never got around to cleaning it up and pushing it anywhere): http://paste.fedoraproject.org/370318/14640938/ It shows how to add the comment and set the state, which you may be able to reuse. One thing I am unsure of is, can you actually force-expire bugs, or only mark them incomplete and wait for launchpad to expire them (exact criteria for this aren't that clear to me..) Thanks, Steve __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
