729 B
729 B
How to release
- Test (npm test), fix if broken before proceeding.
- Ensure proper version in
package.json
andpackage-lock.json
. - Ensure NEWS section exists for the new version, review it, add release date.
- Commit
package.json
,package-lock.json
, NEWS. - Run
git tag -a Major.Minor.Patch
. Use NEWS section as content. - Stub NEWS/package for next version.
Versions
- Bugfix releases increment Patch component of version.
- Feature releases increment Minor and set Patch to zero.
- If backward compatibility is broken, increment Major and set to zero Minor and Patch.
- Branches named 'b.' are kept for any critical fix that might need to be shipped before next feature release is ready.