> will create _some_ support burden. Is the code to support 1.x in > Enigmail really *that* difficult to work with/work around that it > justifies taking on these burdens now, rather than some time down > the road when more people have already transitioned?
Ah, the broccoli argument. "I hate broccoli, but it's on my plate, and Mom and Dad won't let me have ice cream until I finish all my food. So do I want to eat the broccoli now or later?" My vote: eat the broccoli now and enjoy the rest of your meal, rather than try to enjoy your meal while dreading the broccoli. Also, users have had eight years to transition. What are we supposed to do, wait another seven years? Letting Enigmail users know today, "in about a year you'll have to be using GnuPG 2.x with Enigmail," is hardly ripping the rug out from beneath people's feet. I'm not in any way worried about this transition.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ 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
