Comment 8 for bug 1205072
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote Re: Action trigger Granularity strings saving lable not value | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
What would the exact scenario of breakage be? Someone upgrades to 2.7.4. They have their cron jobs referencing the uppercase granularity settings. Then they go in and make changes to an event definition, which saves the new lowercase granularity label. Now their events won't get processed until they adjust their cron jobs and they would also need to edit all the event definitions that use granularity so some are not on the old format and some on the new.
This has to happen at some point for this change to go through. If it doesn't happen when someone upgrades to the next point release, then it will happen when they do a major upgrade. It probably is bad form to do this for minor upgrades, when someone would reasonably expect things to just keep working. But they will just keep working right up until you edit your event definitions.
It probably should just go into 2.8 at this point, since 2.8 is so close.