[HTTPS-Everywhere] Please help test 5.0development.3

[Jacob Hoffman-Andrews]

Hi all,

In case you missed this, you'll need to manually update to
5.0development.3. Please take some time to do this today. I need extra
help testing this release, because it's likely to become the 5.0 stable
release, introducing new rulesets for our large userbase and probably
exposing a large number of bugs. I'd like to try and catch as many of
those as possible before that release goes out.

Thanks,
Jacob

On 03/10/2015 02:59 PM, Jacob Hoffman-Andrews wrote:
> Note: If you currently have the previous development version,
> 5.0development.2, installed, it will not auto-update. You need to
> manually install 5.0development.3 from
> https://www.eff.org/https-everywhere#install-development.
>
> This is because I made error in packaging the previous development
> version, 5.0development.2. The updateURL embedded in the .xpi points at
> the stable-branch updateURL:
> https://www.eff.org/files/https-everywhere-update-2048.rdf. Instead it
> should have pointed at the development-branch updateURL:
> https://www.eff.org/files/https-everywhere-devel-update-2048.rdf.
>
> The most recent version, 5.0development.3, has this same packaging
> error. Right now my plan is to leave it as-is. Once I release 5.0
> stable, in a couple weeks, everyone with the development version
> installed will auto-update to the stable series. I'm thinking that I
> will probably postpone forking off a 6.0 development series until and
> unless we have major experimental changes to the code. Maintaining the
> two separate release series has increased maintenance overhead and
> reduced the quality of both releases.
>
> Let me know what you think, and please do manually install the latest
> version to help test:
> https://www.eff.org/https-everywhere#install-development
>
> On 03/10/2015 11:46 AM, Jacob Hoffman-Andrews wrote:
>> It may take a few minutes for the web cache to expire.
>>
>> Please test this version thoroughly! It's our candidate for a 5.0 stable
>> series release, so we want it to work great. I've disabled a lot of
>> rules that failed the ruleset fetch test, so please check your favorite
>> sites. If they are no longer rewritten, send pull requests to fix the
>> tests and re-enable them.
>>
>> Thanks,
>> Jacob
>>
>> 5.0development.3                            (2015-03-10)
>>   * Added automated ruleset testing.
>>   * Disabled many rules that failed ruleset tests.
>>   * Fix cookie securing so it works for wildcard cookies
>>     even when a wildcard target host is not present.
>>   * User rule creation in Chromium is only offered on HTTPS.
>>   * Enabling and disabling user rules on Chromium works.
>>   * Candidate for 5.0 series stable release.
>> _______________________________________________
>> HTTPS-Everywhere mailing list
>> HTTPS-Everywhere at lists.eff.org
>> https://lists.eff.org/mailman/listinfo/https-everywhere
>>
>