formidable icon indicating copy to clipboard operation
formidable copied to clipboard

Published 20 hours ago • verified publisher icon node-formidable

Release Lines and Release Process

Open tunnckoCore opened this issue 4 years ago • 5 comments

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 avatar Oct 30 '21 21:10 tunnckoCore

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

GrosSacASac avatar Dec 13 '21 17:12 GrosSacASac

Not yet. I'll fix them all soon.

tunnckoCore avatar Dec 14 '21 20:12 tunnckoCore

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: https://github.com/vpulim/node-soap/pull/1183#issuecomment-1166485565

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?

alfaproject avatar Jun 26 '22 10:06 alfaproject

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

GrosSacASac avatar Jul 13 '22 15:07 GrosSacASac

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

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

tunnckoCore avatar Jul 13 '22 18:07 tunnckoCore