Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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
(Created page with "= How to perform a release = The following process applies to any release, including milestones, release candidates and final. [http://www.example.com link title] # Prepare t...") |
(Publish spec documents step) |
||
| Line 6: | Line 6: | ||
## Clone the MicroProfile Config repository | ## Clone the MicroProfile Config repository | ||
## Run the [https://github.com/eclipse/microprofile-config/blob/master/perform_release/prepare_release.sh prepare_release.sh] script (specify required env vars before) - it should create a tag and push it to the upstream repository | ## Run the [https://github.com/eclipse/microprofile-config/blob/master/perform_release/prepare_release.sh 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 | # Deploy artifacts into Eclipse repository | ||
## Run Jenkins job CONFIG-deploy-prerelease-artifacts, specify created tag as a parameter | ## Run Jenkins job CONFIG-deploy-prerelease-artifacts, specify created tag as a parameter | ||
| − | + | # Download PDF and HTML documents from the Jenkins job and from spec/target/generated-docs and publish them (via email until we find a better way) | |
# Notify MicroProfile community about the new version | # Notify MicroProfile community about the new version | ||
## Send information about the created tag and artifact to review the release, e.g. on mailing-list | ## Send information about the created tag and artifact to review the release, e.g. on mailing-list | ||
Revision as of 10:39, 22 June 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 PDF and HTML documents from the Jenkins job and from spec/target/generated-docs and publish them (via email until we find a better way)
- Notify MicroProfile community about the new version
- 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
- If a release candidate is approved, it can be turned into final
- Run the above steps for the final version and announce the final version
- Publish the final artifact to Maven central (not available yet)