Release a new version

This chapter describes how to release a new version

1 How to make a feature release

  1. Merge all feature branches that should go into this release
    • This should be done by Gitlab merge requests
  2. Test the whole product from A-Z
  3. Make sure all tests run successfully (run the Jenkins build job with all tests)
    • Ask the people who broke tests to fix them
  4. Write the changelog
    • The changelog should be kept simple and must be understandable by the customers (use good English)
    • Create a new textile file in portalnode-php-doc for the new release version
  5. Go to the Jenkins job for portalnode-php-dev and press “Perform Maven Release” (should be @ http://jenkins.office:8080/view/7%20GPN%20PHP/job/portalnode-php-dev/m2release/)
    • Jenkins will create a new release version number automatically and also prepare for the next release iteration (post-release)
  6. Download the release from http://archiva-mirror.office:8080/archiva/repository/internal/com/gentics/portalnode-php/, deploy it on a testserver, install it and test it.
  7. If everything is ok, run the “Upload job” for portalnode-php in Jenkins to upload the release build and everything to the Gentics website