[HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

Seth David Schoen schoen at eff.org
Mon Jun 9 09:50:20 PDT 2014

Yan Zhu writes:

> Wouldn't this also be solved by making the ruleset versions sub-versions
> of the releases?
> ex: 4.0development.16.0 == first ruleset release corresponding to
> 4.0development.16

Does that mean that you can't update to a new ruleset release without
first updating to the corresponding extension release version?

Seth Schoen  <schoen at eff.org>
Senior Staff Technologist                       https://www.eff.org/
Electronic Frontier Foundation                  https://www.eff.org/join
815 Eddy Street, San Francisco, CA  94109       +1 415 436 9333 x107

More information about the HTTPS-Everywhere mailing list