Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MicroProfile/Config/ConfigRelease"
< MicroProfile | Config
(Added link to eclipse repo) |
(→How to perform a release of a final version) |
||
Line 16: | Line 16: | ||
== How to perform a release of a final version == | == 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 | |
− | ## Publish the final artifact to Maven central (not available yet) | + | # Run the above steps for the final version, but: |
+ | ## set BASE_REVISION variable to the name of the release candidate tag | ||
+ | ## increase DEV_VERSION to point to the next snapshot version | ||
+ | # Publish the final artifact to Maven central (not available yet) | ||
+ | # announce the final version | ||
+ | # increase the snapshot version in master: merge the intermediary branch branch_$RELEASE_VERSION created locally by the script to master and push master: | ||
+ | ## git checkout master | ||
+ | ## git merge branch_$RELEASE_VERSION | ||
+ | ## git push origin master |
Revision as of 15:07, 7 July 2017
How to perform a release
The following process applies to any release, including milestones, release candidates and final. link title
- Prepare the release
- Clone the MicroProfile Config repository
- Run the prepare_release.sh script (specify required env vars before) - it should create a tag and push it to the upstream repository
- Deploy artifacts into Eclipse repository
- Run Jenkins job CONFIG-deploy-prerelease-artifacts, specify created tag as a parameter
- Download the PDF document from the Jenkins job and from spec/target/generated-docs and copy it to this wiki or github release page (this step could be removed if we release it to a maven repo)
- Notify MicroProfile community about the new version
- Send information about the created tag and artifact to review the release, e.g. on mailing-list
- Git tag is in the source repository
- artifacts (API, TCK, PDF?) are in the Eclipse repository
- Send information about the created tag and artifact to review the release, e.g. on mailing-list
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
- Run the above steps for the final version, but:
- set BASE_REVISION variable to the name of the release candidate tag
- increase DEV_VERSION to point to the next snapshot version
- Publish the final artifact to Maven central (not available yet)
- announce the final version
- increase the snapshot version in master: merge the intermediary branch branch_$RELEASE_VERSION created locally by the script to master and push master:
- git checkout master
- git merge branch_$RELEASE_VERSION
- git push origin master