On 2/6/15 3:05 PM, Robert J. Hansen wrote:
By that same token, what compelling use case does 2.0.x provide that
1.4.x does not?
Werner has several times made various noises about stopping work on 1.4,
as for a very long time he's been operating on a paper-thin budget of
time and resources. If the workload on 2.1 increases 1.4 won't get
dropped, but it'll get further and further behind feature parity with
the 2.1 series. Doing an upgrade now to 2.0 guarantees that we won't be
caught flat-footed if-and-when GnuPG 1.4 stops receiving updates.
... except that the support for GnuPG 2.0.x is already in Enigmail.
Removing support for 1.4.x helps exactly 0 users, unless you agree with
Patrick that Enigmail should be used as a lever to "encourage" users to
upgrade.
The gpg-agent is interesting, and potentially useful for heavy
command line PGP users; but for Enigmail's purposes you've already
got that covered.
Except for bugs in it.
I see no clamor from 1.4.x users to improve password caching for
Enigmail. Am I missing something?
Upgrading to 2.0 means we eat our broccoli, deal
with some support issues, and manage to cut a large chunk of the
codebase which we know has bugs in it. That, too, is a compelling case
for 2.0.x.
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 ...
Doug
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
