[HTTPS-Everywhere] When to move rules to stable branch?

[Claudio Moretti]

My 2c: as far as I remember, rules are pushed into stable when one of the
EFF developers (with commit rights on the main repo) has time to review
them.

There probably is a similar discussion in the list's archive, but the main
reasoning behind this was, also as far as I can remember, that reviewing a
rule is not as easy as it looks like. There are certain websites that
mostly work but have a few pages that fail (epically) and, in the users'
best interests, manual verification was required.

Now, there was talk about writing a testing suite for rulesets, to allow
automatic verification, but nobody had the time to do it... If you can,
you're welcome to try :)

Also, I did write (a while back) a small Python script that compares the
Alexa top 1M with our development branch and spits out the rules not yet
merged in stable that match websites in the list. However, this can only
give you priority on which rules to check first... Imagine if we
automatically merged a broken rule for Google...

/scary thoughts

Anyway, if you can support on the testing suite you'd make a lot of people
in this list very, very happy!

Cheers,

Claudio
Il 17/set/2014 20:49 <sjw at gmx.ch> ha scritto:

>  +1
> I pushed a lot of rulesets that are quite important in my country (top 100
> websites). Saldy, they are still not moved to stable yet.
>
>
> Am 15.09.2014 um 18:21 schrieb Alexander Buchner:
>
> Are there rules of thumb when rules from the development branch get
> pushed to the stable branch?
>
> For example:
> What has to be done forhttps://www.eff.org/https-everywhere/atlas/domains/leo.org.html
> andhttps://www.eff.org/https-everywhere/atlas/domains/openstreetmap.org.html
> to "qualify" for stable?
>
>
>
>
> _______________________________________________
> HTTPS-Everywhere mailing listHTTPS-Everywhere at lists.eff.orghttps://lists.eff.org/mailman/listinfo/https-everywhere
>
>
>
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20140917/fcd0975a/attachment.html>