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
m (Ondrej.mihalyi.gmail.com moved page ConfigRelease to MicroProfile/Config/ConfigRelease: Belongs to the MicroProfilenamespace) |
(Added link to eclipse repo) |
||
| Line 8: | Line 8: | ||
# 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 | + | # 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 | # 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 | ||
| + | ### Git tag is in the [https://github.com/eclipse/microprofile-config source repository] | ||
| + | ### artifacts (API, TCK, PDF?) are in the [https://repo.eclipse.org/content/groups/microprofile/org/eclipse/microprofile/config/ Eclipse repository] | ||
== How to perform a release of a final version == | == How to perform a release of a final version == | ||
Revision as of 14:08, 5 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
- 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)