On Nov 24, 2015, at 02:12 PM, Nick Coghlan wrote:
On 24 November 2015 at 11:59, Barry Warsaw email@example.com wrote:
We'd have to also handle migration paths to newer Ubuntu releases, which probably means removing the config file on future upgrades.
You'll need to figure out those migration paths anyway, as the certificate verification compatibility break will exist between 14.04 and 16.04 regardless of what happens with PEP 493.
Sure, but that's a very different situation. If someone upgraded from 14.04.3 to 14.04.4, they definitely wouldn't expect it to break working code. If it did, it would be a pretty serious regression. Upgrading to LTS maintenance releases should be a no-brainer.
Upgrading from one LTS to a newer one, you *know* things are going to change, so you'll review the release notes and do some very careful analysis of your mission critical code.