[HTTPS-Everywhere] Are release announcements broken?

Russell William Golden niveusluna at niveusluna.org
Tue Oct 30 08:04:06 PDT 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Eckersley wrote:
> There are a couple of problems with release anouncements.  One is
> that the script that generates them is buggy, and doesn't work in
> all cases.  So we need to remember to send them by hand.  The other
> is that all emails which claim to be from me get auto-moderated as
> an anti-spam measure.  It's possible that the 3.0.2 anouncement
> failed to pass one or both of these hoops.

Good to know.

Another potential problem: I had checked the HTTPS Everywhere page on
Fri Oct 26, and it did not show 3.0.3 as available. Yet the changelog
says that 3.0.3 was made on Thu Oct 25. The extension also did not
update in my SeaMonkey profile until this morning (Tue Oct 30).

Do the same script problems that affect release announcements also
affect making the new builds available?

Thank you,

Russell Golden
Fedora Project Contributor
(972) 836-7128
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQIcBAEBAgAGBQJQj+xmAAoJEKRLXWFvZpgnTnQP/AvZ2TuVuOkZuaBDu0jDSKd1
xOLdnf/4CHaMpUHrzw44LwopGPHRR1mftlPcXEXj81/7vkbXK7KokTxMflaFtSlJ
QJ94kHkFUxrh0d7bBDTxKBIlUOxVhzLleysxHghL8bOujXQoCNlDx4I4JNkJIKGu
aqipfEDk25SIHOzrp3+sVwSN8ctkeIz8kF/uICIgwo4LNAOiaWcbLG1v1trSqzV0
fVfhFm1nEkbibOrBZvPgOqAVWKUpIRY7fMpY0VhkPhnpX3krCW3Tlaly55WSzBSY
AxbEILhzbwVrdd/YkShcv/M+L9nVWy7z7IIfo1bm3bG+6u/CD5D9ECPP9r+g3y+c
Vn164xX9SyX/06nZcEbNtnJe+IQwJJEMrl/nOtBLHYtgYTf5YtAImuOGallBzbD6
cDw+PARSAZGC2H+2+Ei+teXDXj4ylGTVznlRp2yNujKR400OWf8yGwN7h7CTz7/a
3UGswQIij4xDErMJxhXnWw64PIy20Ag61r6HFFaqNaEtSR4A4JtDC2jSOyDIEGrz
8ypHEPHnVxJMa8I9Mi+4CrXcl71jVod4i7Ysag3ndKkhnbQ/4mRlwNIQ4o0UU7jc
+00JxO1OzLR8Yof/ssvyjUOggDqNQegVFb1Itnk2scAa56o5LfhJwJFkhpOuEwJ8
Tci/422WGtut8T9tS+u8
=CiBg
-----END PGP SIGNATURE-----




More information about the HTTPS-everywhere mailing list