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.

Sign up for GitHub

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

Jump to bottom

Release Lines and Release Process #769

Open
tunnckoCore opened this issue Oct 30, 2021 · 5 comments
Open

Release Lines and Release Process #769

tunnckoCore opened this issue Oct 30, 2021 · 5 comments
Labels
Status: In Progress This issue is being worked on, and has someone assigned. Type: Discussions Things that need discussion. Brainstorming. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity, without a functionality.

Comments

@tunnckoCore
Copy link
Member

tunnckoCore commented Oct 30, 2021 •
edited

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
@tunnckoCore tunnckoCore mentioned this issue Oct 30, 2021
Closed
@tunnckoCore tunnckoCore pinned this issue Oct 30, 2021
@tunnckoCore tunnckoCore mentioned this issue Oct 30, 2021
Open
@SharpBCD SharpBCD mentioned this issue Nov 22, 2021
Closed
@xHyroM xHyroM mentioned this issue Dec 11, 2021
Closed
@GrosSacASac
Copy link
Contributor

Should I delete v3 tag on npm and replace it with next ?

@tunnckoCore
Copy link
Member Author

Not yet. I'll fix them all soon.

@sabihismail sabihismail mentioned this issue Jan 1, 2022
Closed
@dresende dresende mentioned this issue Jan 6, 2022
Closed
@gaurishhs gaurishhs mentioned this issue Jan 7, 2022
Closed
@majorb22 majorb22 mentioned this issue Jan 16, 2022
Closed
@cubesnyc cubesnyc mentioned this issue Feb 8, 2022
Closed
@tunnckoCore tunnckoCore added Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity, without a functionality. Type: Discussions Things that need discussion. Brainstorming. Status: In Progress This issue is being worked on, and has someone assigned. and removed priority labels Apr 2, 2022
@Akxe Akxe mentioned this issue Apr 23, 2022
Closed
@leonidio-com leonidio-com mentioned this issue Jun 14, 2022
Closed
@alfaproject
Copy link

Hello, is there any update on this? node-soap updated to formidable 2 and broke our webpack build. I've asked why they didn't update to v3 and they said it's not the latest: vpulim/node-soap#1183 (comment)

Considering it's been out for a while I was wondering if something stagnated or people just forgot or if there's any bigger issue in v3?

@kylecombes kylecombes mentioned this issue Jul 1, 2022
Closed
@GrosSacASac
Copy link
Contributor

@tunnckoCore are you ok if I mark v3 as latest now ?

@tunnckoCore
Copy link
Member Author

Let me check tonight and tomorrow, I have some things locally.

I delayed, because I've seen they dropped the CVS.

@ajmeese7 ajmeese7 mentioned this issue Jul 16, 2022
Closed
@mwaibel-go mwaibel-go mentioned this issue Jul 21, 2022
Closed
@demosofa demosofa mentioned this issue Jul 25, 2022
Closed
@neronim1141 neronim1141 mentioned this issue Aug 1, 2022
Open
@demosofa demosofa mentioned this issue Aug 2, 2022
Closed
@stevenwdv stevenwdv mentioned this issue Aug 8, 2022
Closed
@Sethlans Sethlans mentioned this issue Sep 21, 2022
Closed
@Wengiel31 Wengiel31 mentioned this issue Sep 30, 2022
Closed
@nagayev nagayev mentioned this issue Oct 4, 2022
Closed
@mariusrak mariusrak mentioned this issue Oct 11, 2022
Closed
@bottom-up-ai bottom-up-ai mentioned this issue Nov 4, 2022
Closed
@jokrax0 jokrax0 mentioned this issue Dec 8, 2022
Closed
@KnightKrusty KnightKrusty mentioned this issue Dec 23, 2022
Closed
@tunnckoCore tunnckoCore unpinned this issue Dec 30, 2022
@redevill redevill mentioned this issue Jan 30, 2023
Closed
@nikis nikis mentioned this issue Feb 9, 2023
Closed
@Shawful Shawful mentioned this issue Mar 15, 2023
Closed
@aredridel aredridel mentioned this issue Apr 10, 2023
Closed
@boriskogan81 boriskogan81 mentioned this issue May 30, 2023
Closed
@devalp-pro devalp-pro mentioned this issue Jun 20, 2023
Closed
@richard-here richard-here mentioned this issue Jul 11, 2023
Closed
@lou-alfaro lou-alfaro mentioned this issue Jul 31, 2023
Closed
@ugobey ugobey mentioned this issue Sep 28, 2023
Closed
@Mitame Mitame mentioned this issue Nov 24, 2023
Open
@momo-ai momo-ai mentioned this issue Dec 11, 2023
Closed
@R0N1n-dev R0N1n-dev mentioned this issue Jan 2, 2024
Closed
@theGOTOguy theGOTOguy mentioned this issue Jan 21, 2024
Closed
@prvashisht prvashisht mentioned this issue Feb 21, 2024
Open
@MohamedKarrab MohamedKarrab mentioned this issue Mar 4, 2024
Open
@FredTheNoob FredTheNoob mentioned this issue Mar 8, 2024
Closed
@jfirebaugh jfirebaugh mentioned this issue Apr 4, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: In Progress This issue is being worked on, and has someone assigned. Type: Discussions Things that need discussion. Brainstorming. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity, without a functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alfaproject @tunnckoCore @GrosSacASac