Comment 5 for bug 1653184
Revision history for this message
| su_v (suv-lp) wrote Re: [Bug 1653184] Re: Critical warnings with symbols and clones | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On 2017-01-03 15:46 (+0100), jazzynico wrote:
> <off-topic>
> I'm wondering how we should manage our old reports milestoned
> 0.91.1. Most (if not all) of them are backports from the current
> 0.92.x branch, and I'd tend to change everything to 0.92 so that they
> show as fixed in a released version. Do you have an opinion on it?
> </off-topic>
From my point of view, the reports targeted for milestone 0.91.1 with
bug status 'Fix Committed' should be "mass-changed" to milestone 0.92
once the new release has been officially announced (or maybe even before
the announcement).
I would assume that this could be done with a modified version of the
script bryce used (and likely will use for 0.92, too) to change the bug
status for the reports of the latest milestone (from 'Fix Committed' to
'Fix Released'):
https:/
The script requires a platform/distro which provides the necessary
python modules to access launchpad via scripts, and someone to run it
who has any required priviledges on launchpad (probably any member of
the admin group of the 'Inkscape' project).
Probably best coordinated with Bryce (mailing list, or irc)?