© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Thank you for providing fix for this! This is a bit of a tricky fix for SRUing, because generally this is a very low-profile bug. Generally, by principle, we usually SRU high-impact bug fixes (or other cases, as per [1]). The main reason for this is that every change introduces risk of new regressions, so by 'risking' the release of a high-impact fix, we generally can gain more than we can lose. Second thing is - all users will be getting this update, having to download it from the archives, so we'd like it to be 'worth it'.
So I'm not saying this is an instant 'no'. It's just rather unfortunate that we don't have other fixes staged along with this one for SRUing, since releasing more fixes in a batch is generally better practice.
I'm willing to include this anyway (under the "Other safe cases" section), but for this to be possible I would need a bit more information in the Regression Potential field. It's good to know the fix has been written with this particular bug in mind, but I'd like someone to look at the changes and try to analyze where things could 'blow up' if something goes wrong, if the fix has a bug. Basically we'd like to know where to look for any obvious new regressions that could be introduced by the bugfix code changes.
Thanks!
[1] https:/