node-formidable / node-formidable/formidable
Release Lines and Release Process
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.2k
- Forks
- 689
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current release process and the legacy, master, next, and versioned branches alongside their npm dist-tags. Done means the proposed branch and dist-tag lifecycle is agreed and consistently documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100