ExternalVendorCode/openmct
1
0
Fork 0
mirror of https://github.com/nasa/openmct.git synced 2024-12-19 21:27:52 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

chore: bump version to 3.1.0-next and update docs (#6921)

Browse Source 
* chore: bump version to `3.1.0-next`

* docs: update version.md

---------

Co-authored-by: John Hill <john.c.hill@nasa.gov>
This commit is contained in:
Jesse Mazzella 2023-08-16 09:15:30 -07:00 committed by GitHub
parent 87feb0db34
commit 82b1760b0e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/src/process/version.md
View File

@ -53,7 +53,7 @@ requirements.
Additionally, the following project-specific standards will be used: Additionally, the following project-specific standards will be used:
* During development, a "-SNAPSHOT" suffix shall be appended to the * During development, a "-next" suffix shall be appended to the
version number. The version number before the suffix shall reflect version number. The version number before the suffix shall reflect
the next expected version number for release. the next expected version number for release.
* Prior to a 1.0.0 release, the _minor_ version will be incremented * Prior to a 1.0.0 release, the _minor_ version will be incremented
@ -93,7 +93,7 @@ numbers by the following process:
1. Update version number in `package.json` 1. Update version number in `package.json`
1. Checkout branch created for the last sprint that has been successfully tested. 1. Checkout branch created for the last sprint that has been successfully tested.
2. Remove a `-SNAPSHOT` suffix from the version in `package.json`. 2. Remove a `-next` suffix from the version in `package.json`.
3. Verify that resulting version number meets semantic versioning 3. Verify that resulting version number meets semantic versioning
requirements relative to previous stable version. Increment the requirements relative to previous stable version. Increment the
version number if necessary. version number if necessary.
@ -138,7 +138,7 @@ numbers by the following process:
1. Create a new branch off the `master` branch. 1. Create a new branch off the `master` branch.
2. Remove any suffix from the version number, 2. Remove any suffix from the version number,
or increment the _patch_ version if there is no suffix. or increment the _patch_ version if there is no suffix.
3. Append a `-SNAPSHOT` suffix. 3. Append a `-next` suffix.
4. Commit changes to `package.json` on the `master` branch. 4. Commit changes to `package.json` on the `master` branch.
The commit message should reference the sprint being opened, The commit message should reference the sprint being opened,
preferably by a URL reference to the associated Milestone in preferably by a URL reference to the associated Milestone in
@ -150,6 +150,6 @@ numbers by the following process:
Projects dependent on Open MCT being co-developed by the Open MCT Projects dependent on Open MCT being co-developed by the Open MCT
team should follow a similar process, except that they should team should follow a similar process, except that they should
additionally update their dependency on Open MCT to point to the additionally update their dependency on Open MCT to point to the
latest archive when removing their `-SNAPSHOT` status, and latest archive when removing their `-next` status, and
that they should be pointed back to the `master` branch after that they should be pointed back to the `master` branch after
this has completed. this has completed.

2
package.json
View File

@ -1,6 +1,6 @@
{ {
"name": "openmct", "name": "openmct",
"version": "3.0.0-SNAPSHOT", "version": "3.1.0-next",
"description": "The Open MCT core platform", "description": "The Open MCT core platform",
"devDependencies": { "devDependencies": {
"@babel/eslint-parser": "7.22.5", "@babel/eslint-parser": "7.22.5",