[HTTPS-E Rulesets] [HTTPS-Everywhere] Rulesets freeze, starting today

[Yan Zhu]

Update: it's been 2 months! There have been surprisingly few
AARRRGGHH-level broken sites, but perhaps that is because not many users
are testing on the development.

I have merged all the patches (*not* new rulesets) sent to these lists
and opened as pull requests on Github; I've also fixed a few of the bugs
sent to the mailing list that seemed high priority. If you think that
I've missed your patch, let me know. (Reminder: patches will be merged
much faster if you format them with git format-patch or open pull
requests on Github.)

I've also marked the bugs reported via Github that should be fixed
before 4.0stable is ready:
https://github.com/EFForg/https-everywhere/issues?milestone=1&page=1&state=open.
Fixes for any of those are welcome.

On the trac.torproject.org bug tracker [1], I've gone through most of
them and addressed anything that seemed urgent and easy to fix. Help
there would also be welcome (warning: trac is a mess!).

In general, if anyone finds a bug that is probably breaking the web for
a lot of users, please cc me in the email or put [URGENT] in the subject
line. Recent examples: StackExchange logins, pcworld.com.

I plan to release 4.0stable next week or the week after, depending on
how many fires we have to put out at EFF!

[1]
https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&groupdesc=1&group=type&max=200&component=EFF-HTTPS+Everywhere&component=HTTPS+Everywhere%3A+Chrome&order=priority&col=id&col=summary&col=component&col=status&col=owner&col=type&col=priority&col=milestone&report=19

thanks!
Yan


On 02/05/2014 11:14 AM, Yan Zhu wrote:
> Hi all,
> 
> It's time to start preparing for HTTPS Everywhere 4.0 to become the
> new stable release. 4.0 stable will include all of the rules that are
> currently in development, which means that the stable channel will
> suddenly go from having 3,074 rules to having 10,655 rules!
> 
> This is a major undertaking that will probably take around 2 months of
> testing to fix ruleset bug disasters, so here's my proposal for how to
> do this:
> 
> 1. 4.0development.15, which is going to be released later today, will
> be the last 4.0development release. The next development release will
> be versioned as 5.0development.0.
> 
> 2. After 4.0development.15 is released today, Peter and I will no
> longer be merging new rulesets until 4.0 stable is released in 2
> months. However, we'll accept ruleset bug fixes, ruleset deletions,
> and new features/enhancements in the codebase.
> 
>    In the 2 month ruleset freeze period, we need as many people as
> possible testing out 4.0development.15 and reporting/fixing bugs! If
> you're on Firefox, please download the latest development release:
> https://www.eff.org/files/https-everywhere-devel.xpi. If you're on
> Chrome, you have to build your own .crx from the master branch of our
> git repo if you want to test out the development rules.
> 
> 3. At the end of 2 months, we declare victory and release 4.0 stable
> from the head of the master (aka development) branch. After this
> release, we'll start merging new rulesets into master again for
> 5.0development.0.
> 
> 
> Once 4.0 stable is out, we can continue discussing whether to support
> external ruleset feed subscriptions, since ideally HTTPS Everywhere
> should be doing ruleset updates every week or so. I haven't seen a
> proposal for external ruleset subscriptions that is complete enough
> for us to consider it at this time.
> 
> -Yan
> 
> 
> 
> 
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere
> 

-- 
Yan Zhu  <yan at eff.org>
Staff Technologist
Electronic Frontier Foundation                  https://www.eff.org
815 Eddy Street, San Francisco, CA  94109       +1 415 436 9333 x134

-------------- 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-rules/attachments/20140404/20a3f4dc/attachment.sig>