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

[Yan Zhu]

On 06/09/2014 09:50 AM, Seth David Schoen wrote:
> 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?
> 

We decided in IRC last week that this would be the desired default behavior.

In general, it would be difficult to guarantee that a new ruleset
version is compatible with *all* previous extension versions. Ex: we
introduce a new XML property, "hasKeyPins", or change the XML ruleset
structure in a way that is not backwards-compatible past the previous
extension release.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140609/7484df02/attachment.sig>