[HTTPS-Everywhere] Are release announcements broken?

[Peter Eckersley]

On Tue, Oct 30, 2012 at 10:04:06AM -0500, Russell William Golden wrote:
> -----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?

A little bit.  Updates to the eff.org/https-everywhere page are performed
manually.  But in that case, I think the edit to the page had happened but our
CMS cache hadn't been cleared.

-- 
Peter Eckersley                            pde at eff.org
Technology Projects Director      Tel  +1 415 436 9333 x131
Electronic Frontier Foundation    Fax  +1 415 436 9993