-
Notifications
You must be signed in to change notification settings - Fork 269
Release strategy
ADF project use the semantic versioning in combination of tag. ADF Continuous delivery (CD) release:
- Monthly stable release in the official https://registry.npmjs.org/ registry changing the MINOR version so 1.5.0, 1.6.0 and..
-
Weekly beta release in the official https://registry.npmjs.org/ registry using
1.6.0-beta1,1.6.0-beta2,1.6.0-beta3,1.6.0-beta4and the NPM tag @beta (note how to download the beta packages is explained below ) -
PR alpha release in the official https://registry.npmjs.org/ registry using
1.6.0-ISH_KEY(ISH_KEY is the key of the git commit relative the PR) and the NPM tag @alpha (note how to download the alpha packages is explained below )
@latest o---------------------------------------------------------------o Monthly
| |
@beta o---------------o---------------o---------------o---------------o Weekly
| |
@alpha o---o---o---o---o---o---o---o---o---o---o---o---o---o---o---o---o Any PR accepted on development
By default, npm install download the packages from https://registry.npmjs.org/ registry with latest tag. If you want to download a different tagged packages you need to specify the different tag in this way:
Beta version are created weekly
npm install NAME_PACKAGE@beta --save
pratical example
npm install ng2-alfresco-core@beta --save
The alpha version are created from any merged PR on development
npm install NAME_PACKAGE@alpha --save
pratical example
npm install ng2-alfresco-core@alpha --save
If you downloaded our repository on your machine and you want update the demo shell to the @alpha or @beta you can use the the script :
./scripts/start.sh -v @beta
./scripts/start.sh -v @alpha
Tags are a supplement to semver (e.g., 1.5.0) for organizing and labeling different versions of packages. In addition to being more human-readable, tags allow publishers to distribute their packages more effectively.