Skip to main content

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.

Jump to: navigation, search

MicroProfile/Config/ConfigRelease

< MicroProfile‎ | Config
Revision as of 05:07, 22 June 2017 by Mihalyi.omnifish.ee (Talk | contribs) (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...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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
  1. Deploy artifacts into Eclipse repository
    1. Run Jenkins job CONFIG-deploy-prerelease-artifacts, specify created tag as a parameter
  1. 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

How to perform a release of a final version

  1. Do the steps above for a release candidate
  2. If a release candidate is approved, it can be turned into final
    1. Run the above steps for the final version and announce the final version
    2. Publish the final artifact to Maven central (not available yet)

Back to the top