Hey,
the 'stable' branch on GitHub (
https://github.com/EFForg/https-everywhere/tree/stable ) is quite old
and doesn't reflect the currently released addon version at all. The
HTTPS Everywhere Atlas states:
"Information current as of:
current release 94ec7b6 2015-12-21 11:26:25 -0600;
next release 9f7529d 2016-02-23 15:49:12 -0800;"
The information provided by the atlas apparently bases its "current
release" information on that stable branch - at least that's what I
assume to be the case. Thus, all information related to the current
release is outdated.
Is this intended or should the repository state, that the latest HTTPSE
release is based on, have been merged into the stable branch?
Kevin
On Feb 24th, 2016 7:56 PM, William Budington <[email protected]> wrote:
There is a new Firefox release for HTTPS Everywhere out today.
From the changelog:
* Fixes for Firefox Dev Edition
* Chrome: Fix regressions in custom rule functions
* Firefox: Fix custom ruleset regression
A new release for Chrome is forthcoming.
Download from the usual places.
_______________________________________________
HTTPS-Everywhere mailing list
[email protected]
https://lists.eff.org/mailman/listinfo/https-everywhere
_______________________________________________
HTTPS-Everywhere mailing list
[email protected]
https://lists.eff.org/mailman/listinfo/https-everywhere
