Opened 6 years ago

Closed 6 years ago

#10310 closed enhancement (fixed)

Automate merging rules from development (master) to stable (3.0)

Reported by: zyan Owned by:
Priority: High Milestone: HTTPS-E next Firefox dev release
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version: HTTPS-E 4.0dev14
Severity: Keywords:
Cc: pde@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This could be as simple as a script that we run before making each stable release to determine which changes to master should be ported to stable. One idea is to use the Alexa Top 1M domains list [1] to mark ruleset changes as higher or lower priority. Right now we just do this manually.

Another possible metric for "stability" is the amount of time that a ruleset has been in master without any bug reports.

[1] zip: http://s3.amazonaws.com/alexa-static/top-1m.csv.zip

Child Tickets

Change History (2)

comment:1 Changed 6 years ago by zyan

Summary: Automate merging rules from Master to StableAutomate merging rules from development (master) to stable (3.0)

comment:2 Changed 6 years ago by zyan

Resolution: fixed
Status: newclosed

Closing this because Claudio wrote the Alexa-checker script; also, we are turning dev. into the new stable in April.

Note: See TracTickets for help on using tickets.