Skip to content

Track backporting Path optimizations #87

Closed

Description

@MylesBorins

Original PR:

Fixes:

The number of regressions already found makes me a bit anxious about landing these changes. Personally I would like to see this live on v5.x for as long as possible before we backport to v4.x, if we do at all.

A good sign that it is time to backport this will be when we are having trouble landing other unrelated fixes / changes. Until that happens I think it would make the most sense to hold off and keep this issue updated.

I've added the lts-agenda tag so that we can discuss this at the next meeting

Activity

  1. MylesBorins commented on Mar 30, 2016

    @MylesBorins
    ContributorAuthor

    I think this one should go with it too nodejs/node@9de9a08 from nodejs/node#5673

  2. MylesBorins commented on Apr 4, 2016

    @MylesBorins
    ContributorAuthor

    Looks like we'll also need nodejs/node@3072546 from nodejs/node#6028

  3. MylesBorins commented on May 2, 2016

    @MylesBorins
    ContributorAuthor

    Closing for now. This will be reopened if we find that the path changes need to land.

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