Version 7
Created by guillaume.smet on Apr 20, 2017 9:09 AM. Last modified by guillaume.smet on May 17, 2017 10:35 AM.

    Release Process

    Follow these steps for an official release.

     

    Prerequisites

    • You need to have access to http://ci.hibernate.org/: the release process is now driven by CI
    • Follow the order of operations - the API has to be released before the specification

     

    Prepare

     

    Release beanvalidation-api

    Prepare

    • Check that everything has been pushed to the upstream repository
    • Check that CI is green for the branch you want to release
    • Before you release try the latest snapshot of the API with the RI (if the RI is up to date with the API)

    Release

    • Go to CI, and select the beanvalidation-api-release job. Click on Build with parameters.
      • Be careful when filling the form with the build parameters
      • Fill in the DELIVERY_QUALIFIER if the release is an official JCP release step (use - if not)
    • Release the artifacts on the JBoss Nexus repository manager. This is a two-steps process.
      • Log into Nexus and examine your staging repository. Click on the Updated column 2 times to have the repositories sorted correctly.
      • You can either drop it in order to start over again or you can close and promote it making the artifacts available in the live repository. (Click Refresh after each action)
      • You can find more information in the description of the JBoss project release process. A Maven settings.xml for testing the artifacts in the staging repository can be found here.
    • Transfer the released issues in JIRA to the Closed state. You can use this search Issue Navigator - Hibernate JIRA and select another fixVersion. Once you have selected the right version, click on the button with three dots at the top right of the screen and click on Bulk update all XX issues. Use the Transition action to transition your issues from Resolved to Closed.

     

    Release beanvalidation-spec

    Prepare

    • Check that everything has been pushed to the upstream repository
    • Check that you are able to build the TCK audit file via the command ant create-tck-audit-file (a section id might be missing)
    • Check that CI is green for the branch you want to release
    • The changelog of the spec is now updated automatically: do not update it!

    Release

    • Go to CI, and select the beanvalidation-spec-release job. Click on Build with parameters.
      • Be careful when filling the form with the build parameters.
      • Fill in the RELEASE_VERSION_QUALIFIER if the release is an official JCP release step
      • Fill in the DELIVERY_QUALIFIER if the release is an official JCP release step (use - if not)
    • The release job pushes the specification to the website repository but there are still some manual steps:
    335 Views Categories: Tags: