2014-04-09 15:14:20 +08:00
|
|
|
1. Test (make clean all check), fix if broken before proceeding
|
2019-01-02 18:33:23 +08:00
|
|
|
2. Ensure proper version in package.json and package-lock.json
|
2014-04-09 15:14:20 +08:00
|
|
|
3. Ensure NEWS section exists for the new version, review it, add release date
|
2019-01-02 18:33:23 +08:00
|
|
|
4. If there are modified dependencies in package.json, update them with `npm upgrade {{package_name}}@{{version}}`
|
|
|
|
|
5. Commit package.json, package-lock.json (or yarn.lock), NEWS
|
2015-10-22 22:26:37 +08:00
|
|
|
6. git tag -a Major.Minor.Patch # use NEWS section as content
|
2017-02-18 01:01:59 +08:00
|
|
|
7. Stub NEWS/package for next version
|
2013-10-03 23:15:11 +08:00
|
|
|
|
2014-04-09 15:14:20 +08:00
|
|
|
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<Major>.<Minor>' are kept for any critical
|
|
|
|
|
fix that might need to be shipped before next feature release
|
|
|
|
|
is ready.
|
