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.
MicroProfile/Config/ConfigRelease
< MicroProfile | Config
Revision as of 18:37, 4 July 2017 by Unnamed Poltroon (Talk) (Ondrej.mihalyi.gmail.com moved page ConfigRelease to MicroProfile/Config/ConfigRelease: Belongs to the MicroProfilenamespace)
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)