There will be 3 lines: Legacy, Current (master / latest), and Next.
- v1 as Legacy:
legacy branch - legacy dist-tag
- v2 as Current:
master branch - latest dist-tag
- v3 as Next:
next branch - next dist-tag
When v3 should become latest on npm, we cut the master branch to version-2 branch and merge next branch into master. When new updates and releases are needed for v2 and it's not Current anymore (because v3 is the new Current), we publish it on version-2 dist-tag from version-2 (or just v2) branch.
Same repeats when v4 needs to become Current - move master to version-3 branch, merge next branch to master.
I just want consistency.. duh.
cc @GrosSacASac
There will be 3 lines: Legacy, Current (master / latest), and Next.
legacybranch -legacydist-tagmasterbranch -latestdist-tagnextbranch -nextdist-tagWhen v3 should become
lateston npm, we cut themasterbranch toversion-2branch and mergenextbranch intomaster. When new updates and releases are needed for v2 and it's not Current anymore (because v3 is the new Current), we publish it onversion-2dist-tag fromversion-2(or justv2) branch.Same repeats when v4 needs to become Current - move
mastertoversion-3branch, mergenextbranch tomaster.I just want consistency.. duh.
cc @GrosSacASac