-
-
Notifications
You must be signed in to change notification settings - Fork 691
Open
Labels
Status: In ProgressThis issue is being worked on, and has someone assigned.This issue is being worked on, and has someone assigned.Type: DiscussionsThings that need discussion. Brainstorming.Things that need discussion. Brainstorming.Type: MaintenanceUpdating phrasing or wording to make things clearer or removing ambiguity, without a functionality.Updating phrasing or wording to make things clearer or removing ambiguity, without a functionality.
Description
There will be 3 lines: Legacy, Current (master / latest), and Next.
- v1 as Legacy:
legacybranch -legacydist-tag - v2 as Current:
masterbranch -latestdist-tag - v3 as Next:
nextbranch -nextdist-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
Metadata
Metadata
Assignees
Labels
Status: In ProgressThis issue is being worked on, and has someone assigned.This issue is being worked on, and has someone assigned.Type: DiscussionsThings that need discussion. Brainstorming.Things that need discussion. Brainstorming.Type: MaintenanceUpdating phrasing or wording to make things clearer or removing ambiguity, without a functionality.Updating phrasing or wording to make things clearer or removing ambiguity, without a functionality.