Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: remove redundant LTS/Current information in Collaborator Guide #25842

Closed
wants to merge 1 commit into from

Commits on Jan 31, 2019

  1. doc: remove redundant LTS/Current information in Collaborator Guide

    Remove bullet points about how breaking changes are handled in Current
    and LTS branches.
    
    * This information is covered in
      https://github.com/nodejs/Release#release-plan.
    * Having it here and in the above link means that the two may get out of
      sync, resulting in confusion.
    * The above link appears later in the doc in the LTS section.
    * Most Collaborators should not land *anything* in LTS branches and will
      almost never have a reason to land things into Current branches. They
      land stuff on the master branch. Adding this material here is
      confusing because it implies that Collaborators do land stuff on those
      branches. Save talk about those branches and how they're managed for
      later in the LTS section where it can be made clear that most
      Collaborators should not be landing code there anyway.
    Trott committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    31ff9fd View commit details
    Browse the repository at this point in the history