1 Release checklist

Juliette edited this page 2016-04-19 17:50:51 +02:00

Table of Contents

• Action checklist for TGMPA v2.x releases:

Action checklist for TGMPA v2.x releases:

1. Create release PR:

   • Create/update changelog
   • Add version nr and release date to the changelog
   • Regenerate the .pot file
   • Fill in version nrs for new functions and hooks added - these will generally be in 2.x.x format until release version number is known
   • Up version nrs
     • in readme.md
     • top of file in class-tgm-plugin-activation.php
     • version nr constant in class-tgm-plugin-activation.php
     • top of file in example.php
     • maybe up Tested up to: in readme.md
   • If any strings were added/changes: ping translators to update their translators and PR against the release PR branch

2. After release PR has been merged to develop:

   • Merge develop into master
   • Tag master with the new version number
   • Fast forward develop to master to have a clean start

   Packagist will auto-release a new version based on the tagging.

3. Wait a day or two just in case.

4. Update website:

   • Add a zip of the new version to the gh-pages branch in the releases folder
   • Test the Custom Generator against the new release: Verify that all 7 versions which can be generated are adjusted properly. See https://github.com/TGMPA/TGM-Plugin-Activation/pull/519 for what the differences should be between versions.
   • Write a blog post for the website about the new release.
   • Create a PR against the gh-pages branch to bring the website up to date.

   When something is merged to the gh-pages branch, it will automatically update the contributors list, changelog information and latest version information based on the master branch.