> ... except that the support for GnuPG 2.0.x is already in Enigmail. You're misunderstanding who I'm talking about when I say "we're caught flat-footed." I don't mean us-the-developers. I mean us-the-community. If 1.4 gets EOLed there's going to be a mad rush of people trying to upgrade, and then that tidal flood you're worried about *will* happen.
Compare this to if the next version of Enigmail checks to see if GnuPG 1.4 is being used, and if so, puts up a one-time screen saying "Hello! You're using an old version of GnuPG. In 2016 Enigmail will start requiring GnuPG 2. You can download it for your operating system at... [insert OS-specific link here]." And the check could be repeated once a month, giving polite prompts to people still running 1.4 to upgrade. One involves a mad rush, and the other is a more orderly walk towards the exit. If that was the only reason for doing this, it would still be sufficient -- IMO -- to justify the decision. > Removing support for 1.4.x helps exactly 0 users... It helps users by encouraging them to migrate to a newer codebase which has much better support and maintenance. And it helps users by axing out a large chunk of code that has been the source of serious bugs in the past, and which -- IMO -- almost certainly still has serious bugs in it. (Which is absolutely no slight on the skill or professionalism of the developers.) > I see no clamor from 1.4.x users to improve password caching for > Enigmail. Am I missing something? Yes. Look at the bug tracker. > For the Enigmail devs, sure, that's a compelling use case. :) And > again, I sincerely hope I'm wrong that "some support issues" will > actually be a tidal wave of unhappy users ... I'm pretty sure you're wrong.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
