... | @@ -2,7 +2,10 @@ |
... | @@ -2,7 +2,10 @@ |
|
1. Remove the ``-SNAPSHOT`` suffix from the version number in the ``pom.xml``.
|
|
1. Remove the ``-SNAPSHOT`` suffix from the version number in the ``pom.xml``.
|
|
1. Adapt change log file ``src/changes/changes.xml``.
|
|
1. Adapt change log file ``src/changes/changes.xml``.
|
|
1. Execute the Jenkins job [teetime-release](https://build.se.informatik.uni-kiel.de/jenkins/view/TeeTime/job/teetime-release) to build and to deploy the site (on github) and the project (on maven central).
|
|
1. Execute the Jenkins job [teetime-release](https://build.se.informatik.uni-kiel.de/jenkins/view/TeeTime/job/teetime-release) to build and to deploy the site (on github) and the project (on maven central).
|
|
1. Login on [sonatype](https://oss.sonatype.org/#nexus-search;quick~teetime) to make the new release publicly available.
|
|
1. Login on [sonatype](https://oss.sonatype.org/#nexus-search;quick~teetime) to move the new uploaded version from the auto-generated repository to the release repository (a.k.a. maven central) by
|
|
|
|
1. clicking on ``Staging repositories`` on the right side bar,
|
|
|
|
1. selecting the auto-generated repository, and
|
|
|
|
1. clicking on the copy (?) button (auto-drop should be enabled).
|
|
1. Tag the commit and push it.
|
|
1. Tag the commit and push it.
|
|
1. Merge the ``release`` branch into the ``master``.
|
|
1. Merge the ``release`` branch into the ``master``.
|
|
1. Delete the ``release`` branch.
|
|
1. Delete the ``release`` branch.
|
... | | ... | |