Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Release 2019.1.7 forthcoming #17157

Closed
Closed

Description

@zoracon

Type: other

cc @J0WI, @Bisaloo, @Hainish, @jsha, @andresbase

Rather short notice, however this release will be somewhat minor but please put comment any extra needed checks, call outs, or notes that may be needed.

Release Notes (incomplete):

  • Change "Block all unencrypted requests" language to "Encrypt all sites eligible"
  • Amend check_rules.py fetch test to disable rules only if all rules are problematic,
    and comment rules out if other rules are functional in the set
  • HSTS Prune and updates

Activity

  1. changed the title [-]Release 2018.12.19 forthcoming[/-] [+]Release 2018.1.03 forthcoming[/+] on Dec 19, 2018
  2. pinned this issue on Dec 19, 2018
  3. zoracon commented on Dec 19, 2018

    @zoracon
    ContributorAuthor

    Updating this, since EFF is about to go on holiday, we decided to postpone the release until after we get back so there will be full support in case an issue occurs.

  4. cschanaj commented on Dec 23, 2018

    @cschanaj
    Collaborator

    I believe the upcoming version should be 2019.1.3 😄

  5. cschanaj commented on Dec 31, 2018

    @cschanaj
    Collaborator

    It seems that the PR labeller is crashed, #17197 and #17199 should be marked as top-1k.

  6. Bisaloo commented on Dec 31, 2018

    @Bisaloo
    Collaborator

    Sorry, I guess that's me again. It happens every time I submit a HSTS-prune PR

  7. changed the title [-]Release 2018.1.03 forthcoming[/-] [+]Release 2018.1.8 forthcoming[/+] on Jan 2, 2019
  8. zoracon commented on Jan 2, 2019

    @zoracon
    ContributorAuthor

    Due to some scheduling conflicts we are pushing the release to Monday since a Friday release is not ideal for obvious reasons. Bear with us!

  9. J0WI commented on Jan 5, 2019

    @J0WI
    Contributor

    #16595 fixes #15862, would be great to get some feedback there. But this could also be served in a ruleset update and does not block a new release.

  10. Bisaloo commented on Jan 7, 2019

    @Bisaloo
    Collaborator

    If the release happens today, the date should be 2019.1.7 😉

  11. changed the title [-]Release 2018.1.8 forthcoming[/-] [+]Release 2019.1.7 forthcoming[/+] on Jan 7, 2019
  12. Bisaloo commented on Jan 8, 2019

    @Bisaloo
    Collaborator

    This update reverted my EASE setting. That could be very problematic in some threat models. I could swear there was an issue for this but I can't find it anymore. Anyone remembers this?

  13. reopened this on Jan 8, 2019
  14. zoracon commented on Jan 8, 2019

    @zoracon
    ContributorAuthor

    Looks like an oversight on my part led to the "EASE" language not making it into this release. Merging #17156 into master and scheduling another release for this month soon.

    This update reverted my EASE setting. That could be very problematic in some threat models. I could swear there was an issue for this but I can't find it anymore. Anyone remembers this?'

    @Bisaloo Do you think the issue was resolved and returned? Or was this an issue that was closed? I'll search around for it in the meantime.

  15. Bisaloo commented on Jan 9, 2019

    @Bisaloo
    Collaborator

    I'm not sure. I don't know if it was open of closed and I'm even starting to wonder if I'm not mixing things up with similar but different issues 😕 . I'll keep looking.

  16. unpinned this issue on Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions