Skip to content

Potential v4.x backports #231

Closed
Closed

Description

@gibfahn

We have a couple of requested backports for v4.x, so opening this issue to track them. Please add to the list as you find them.

Things like the exitedAfterDisconnect backport may generate enough discussion that it's worth spinning out a separate issue, we can do that as it becomes necessary.

Semver-minor

  • cluster: alias suicide to exitedAfterDisconnect #7998 (Refs: #13684)

Semver-patch

  • deps: upgrade OpenSSL to version 1.0.2l #13233 (Refs: #12913 and #12691)
  • deps: cherry-pick 18ea996 from c-ares upstream #13883

Activity

  1. MylesBorins commented on Jun 15, 2017

    @MylesBorins
    Contributor

    we could modify #7998 to create an alias for exitedAfterDisconnect with no warning... this would be able to land as a patch

  2. mhdawson commented on Jun 15, 2017

    @mhdawson
    Member

    +1 on Myles suggestion for an alias.

  3. gibfahn commented on Jun 15, 2017

    @gibfahn
    MemberAuthor

    we could modify #7998 to create an alias for exitedAfterDisconnect with no warning... this would be able to land as a patch

    I don't understand, AFAICT #7998 doesn't have a warning, isn't this just an alias:

    image

    Also isn't adding an alias (i.e. a new property) semver-minor?

  4. MylesBorins commented on Feb 10, 2018

    @MylesBorins
    Contributor

    closing as v4.x is not likely to get another release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions