search

node-formidable / formidable

The most used, flexible, fast and streaming parser for multipart form data. Supports uploading to serverless environments, AWS S3, Azure, GCP or the filesystem. Used in production.
MIT License
7.01k stars 680 forks source link

Release Lines and Release Process #769

Open tunnckoCore opened 2 years ago

tunnckoCore commented 2 years ago

There will be 3 lines: Legacy, Current (master / latest), and Next.

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

GrosSacASac commented 2 years ago

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

tunnckoCore commented 2 years ago

Not yet. I'll fix them all soon.

alfaproject commented 2 years ago

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?

GrosSacASac commented 1 year ago

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

tunnckoCore commented 1 year ago

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

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