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

Activity

1. brendanashworth commented on Dec 6, 2014

   

   brendanashworth

   on Dec 6, 2014

   Contributor

   More actions

   👍, 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

   on Dec 6, 2014

   Contributor

   More actions

   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

   on Dec 6, 2014

   More actions

   +1 on board with you @mikeal @indutny @trevnorris @isaacs @bnoordhuis @piscisaureus
4. ralphtheninja commented on Dec 6, 2014

   

   ralphtheninja

   on Dec 6, 2014

   More actions

   👍 https://www.youtube.com/watch?v=xnKhsTXoKCI
5. caineio

   added

   needs info

   need info

   and removed

   needs info

   on Dec 8, 2014
6. piscisaureus

   removed

   need info

   on Dec 8, 2014
7. jbergstroem commented on Dec 10, 2014

   

   jbergstroem

   on Dec 10, 2014

   Member

   More actions

   It seems to be the default branch on github now at least.
8. bnoordhuis commented on Dec 10, 2014

   

   bnoordhuis

   on Dec 10, 2014

   Member

   More actions

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

   closed this as completedon Dec 10, 2014
10. bajtos commented on Dec 15, 2014

    

    bajtos

    on Dec 15, 2014

    Contributor

    More actions

    Not for me, https://github.com/iojs/io.js still shows v0.12
11. bnoordhuis commented on Dec 15, 2014

    

    bnoordhuis

    on Dec 15, 2014

    Member

    More actions

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

    

    bajtos

    on Dec 15, 2014

    Contributor

    More actions

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