Nemcio/SCM-Manager
1
0
Fork 0
mirror of https://github.com/scm-manager/scm-manager.git synced 2026-07-01 00:08:28 +02:00
Code Issues Packages Projects Releases Activity

Update for new plugin release process

Browse Source
This commit is contained in:
René Pfeuffer
2020-04-09 19:45:24 +02:00
committed by GitHub
parent 9cdec81ec0
commit 70c2d5e844
1 changed files with 18 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
docs/v2/release-process.md
View File

@@ -14,7 +14,7 @@ git fetch && git checkout develop && git reset --hard origin/develop
Change "Unreleased" header in `CHANGELOG.md` to `<version> - <current date>`
## Create release branch:
## Create release branch
`git checkout -b release/<version>`
@@ -37,6 +37,7 @@ Jenkins will
- merge with master branch
- build and deploy everything
- set the new development version for the develop branch
- delete the release branch
## Make a party
@@ -44,7 +45,7 @@ Jenkins will
To release a new version of a Plugin for SCM-Manager v2 you have to do the following steps (replace placeholder `<version>` accordingly, eg. with `2.1.0`):
## Update to latest version
## Check out default branch
Make sure you have no changes you want to keep!
@@ -52,20 +53,6 @@ Make sure you have no changes you want to keep!
git fetch && git checkout develop && git reset --hard origin/develop
```
## Set new version
Edit `pom.xml`:
- `version` and `scm.tag` have to be set to the new version.
- ensure that all dependencies to other scm resources have released versions
- ensure `parent.version` points to stable release
Edit `package.json`:
- `version` has to be set to the new version.
- ensure that all dependencies to other scm resources have released versions
- ensure the version of `@scm-manager/ui-plugins` points to the same version as `parent.version` in the `pom.xml`
## Modify Changelog
Change "Unreleased" header in `CHANGELOG.md` to `<version> - <current date>`
@@ -78,42 +65,34 @@ Change "Unreleased" header in `CHANGELOG.md` to `<version> - <current date>`
`mvn clean install`
## Create release branch
```
git checkout -b release/<version>
```
## Commit and push release
```
git commit -am "Release version <version>"
git push origin develop
```
## Merge with master branch
The merge should be possible with a fast forward. If this fails, check for changes on the `master` branch that are not present on the `develop` branch. Merge these changes into the `develop` branch, first!
## Push release branch
```
git checkout master && git pull && git merge develop --ff-only && git push origin master
git push origin release/<version>
```
## Create and push tag
## Wait for Jenkins build
```
git tag -s -a <version> -m "<version>"
git push --tags origin
```
Jenkins will
## Prepare next development version
- update versions in pom.xml and package.json
- merge with master branch
- build and deploy everything
- set the new development version for the develop branch
- delete the release branch
```
git checkout develop
```
Edit `pom.xml`: `version` has to be set to the new development version, `tag` to `HEAD`.
Edit `package.json`: `version` has to be set to the new development version.
```
git commit -am "Prepare for next development iteration"
git push origin develop
```
## Attention: Creating new plugins
If you are creating a new plugin which doesn't exist in the SCM-Manager Plugin-Center yet, your plugin will not be shown after the release. First you have to create a `index.md` in the Plugin-Center Repository.