Skip to content

RELEASE.md

Latest commit

 

History

History
39 lines (37 loc) · 2.67 KB

RELEASE.md

File metadata and controls

39 lines (37 loc) · 2.67 KB

Releasing a new Mojarra version

In below example we assume 4.0.3.

  1. Check beforehand that this version does NOT exist in staging else bump the version
  2. Go to Mojarra CI
  3. Log in
  4. Open 1_mojarra_build_and_stage
  5. Click Build with parameters in menu
    • BRANCH = 4.0
    • RELEASE_VERSION = 4.0.3
    • JDK = JDK11
    • click [Build] button
  6. Wait for it to finish successfully
  7. Drill down into this build e.g. build 106
  8. Click Console Output in menu
  9. Ctrl+F 'orgglassfish', to find release ID, e.g. Created staging repository with ID "orgglassfish-1273", remember this for STAGING_RELEASE_ID in a later step
  10. Verify that it's present in staging
  11. Verify that a new 4.0.3 branch is created
  12. Verify that a new 4.0.3-RELEASE tag is created
  13. Open 2_mojarra-run-tck-against-staged-build_4_0 (there are separate ones for 2.3 and 3.0)
  14. Click Build with parameters in menu
    • IMPL_SOURCE = STAGE
    • IMPL_VERSION = 4.0.3
    • IMPL_BRANCH = 4.0
    • click [Build] button
  15. Wait for it to finish successfully
  16. Open 3_mojarra-staging-to-release
  17. Click Build with parameters in menu
    • STAGING_RELEASE_ID = orgglassfish-1273
    • click [Build] button
  18. Wait for it to finish successfully
  19. Verify that it's present in Maven Central (might take up to a hour)
  20. If everything is OK, then merge 4.0.3 branch into 4.0 via a PR
  21. Delete the 4.0.3 branch after merge
  22. Manage the milestones page
    • make sure all issues/PRs are linked to proper milestone
    • close the milestones which were just released
    • create new milestones for next releases