RELEASING.md

Yash release procedure

1. Make sure all issues relevant to the release are associated with the corresponding milestone and are closed. (Milestones)
2. Run make update-po in po and see if there is any text that needs translation. If all the texts are up-to-date, revert (git reset) the change in auto- generated comments to avoid committing it.
3. Make sure the latest commit (which is to be released) has been successfully tested by Jenkins:
   • Full test
   • Valgrind test
   • Extra test
   • Note that these tests are run no more than once a day. You may have to wait for the tests to complete.
4. Update the version number in configure.
   • See commit b83905d for an example of what to change.
   • Also update the year in the copyright notice if releasing for the first time in the current year.
5. Update NEWS and NEWS.ja to include the release date.
6. Commit and push the change.
7. Obtain the distribution tarball from Jenkins. (Distribution build)
   • Make sure the tarball includes the just committed update.
8. Tag and push the revision.
9. Release the tarball on GitHub. (Releases)
10. Close the milestone for the just-published release and create one for the next release. (Milestones)
11. Update doc on the gh-pages branch.
    • All the files should be copied intact from the Documentation build based on the Distribution build for the released commit.