Skip to content

RELEASE.md

Latest commit

 

History

History
17 lines (13 loc) · 1.3 KB

RELEASE.md

File metadata and controls

17 lines (13 loc) · 1.3 KB

Releasing xcproj

In this documents you'll find all the necessary steps to release a new version of xcproj.

Although some of the steps have been automated, there are some of them that need to be executed manually.

  1. First of all, create a new release branch with the following name release/x.x.x where x.x.x is the new version that is going to be released.
  2. Update the CHANGELOG.md adding a new entry at the top with the new version. The new entry should include all the changes in the new version, mentioning the people involved in these changes, and the issues that were closed with those changes. Commit the changes in CHANGELOG.md.
  3. Validate the state of the project by executing bundle exec rake ci
  4. Generate the release with bundle exec rake release.
  5. Create a new release on GitHub including the information from the last entry in the CHANGELOG.md.
  6. Close the GitHub Milestone associated to that release and open a new one for the next release.
  7. Rebase the release/x.x.x branch into master.

Notes

  • If any of the steps above is not clear above do not hesitate to propose improvements.
  • Release should be done only by authorized people that have rights to crease releases in this repository and commiting changes to the Tap repository.