MicroProfile/Config/ConfigRelease

How to perform a release

The following process applies to any release, including milestones, release candidates and final. link title

1. Prepare the release
   1. Clone the MicroProfile Config repository
   2. Run the prepare_release.sh script (specify required env vars before) - it should create a tag and push it to the upstream repository
2. Deploy artifacts into Eclipse repository
   1. Run Jenkins job CONFIG-deploy-prerelease-artifacts, specify created tag as a parameter
3. Download the PDF document from the Jenkins job and from spec/target/generated-docs in the workspace and copy it to this wiki or github release page (this step could be removed if we release it to a maven repo)
4. Notify MicroProfile community about the new version
   1. Send information about the created tag and artifact to review the release, e.g. on mailing-list
      1. Git tag is in the source repository
      2. artifacts (API, TCK, PDF?) are in the Eclipse repository

How to perform a release of a final version

Do the steps above for a release candidate, except increase the development version instead of leaving it the same as before

If a release candidate is approved, it can be turned into final

1. Run the above steps for the final version, but:
   1. set BASE_REVISION variable to the name of the release candidate tag
   2. increase DEV_VERSION to point to the next snapshot version
2. Publish the final artifact to Maven central (not available yet)
3. announce the final version
4. increase the snapshot version in master: merge the intermediary branch branch_$RELEASE_VERSION created locally by the script to master and push master:
   1. git checkout master
   2. git merge branch_$RELEASE_VERSION
   3. git push origin master