Sitelet https://github.com/nodejs/node/issues/96
Skip to content

Shouldn't branch v0.12 be master here? #96

Description

@ghostbar

It would do everything a lot easier.

Activity

  1. brendanashworth commented on Dec 6, 2014

    @brendanashworth
    Contributor

    👍, this always really annoyed me in the old repository. Can we please also not have a billion branches in this one too?

  2. mikeal commented on Dec 6, 2014

    @mikeal
    Contributor

    this is probably a good idea since our next target version is 1.0 and having a v0.12 branch that differs from Joyent's branch for the target v0.12 release is confusing.

  3. migounette commented on Dec 6, 2014

    @migounette
  4. ralphtheninja commented on Dec 6, 2014

    @ralphtheninja
  5. jbergstroem commented on Dec 10, 2014

    @jbergstroem
    Member

    It seems to be the default branch on github now at least.

  6. bnoordhuis commented on Dec 10, 2014

    @bnoordhuis
    Member

    So it is. I'll go ahead and close the issue.

  7. bajtos commented on Dec 15, 2014

    @bajtos
    Contributor

    Not for me, https://github.com/iojs/io.js still shows v0.12

  8. bnoordhuis commented on Dec 15, 2014

    @bnoordhuis
    Member

    @bajtos That's the intended behavior. If you do a fresh clone, v0.12 is the default branch.

  9. bajtos commented on Dec 15, 2014

    @bajtos
    Contributor

    I see. I thought the plan was to rename v0.12 to master. Never mind.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions