Preparing new release » History » Revision 17
Revision 16 (cryptogopher, 2019-08-19 21:57) → Revision 17/37 (cryptogopher, 2019-08-19 22:02)
h1. Preparing new release # Make sure all tests pass on each merged issue branch, on all supported Redmine versions: <pre> $ RUBYOPT="-W1" rake redmine:plugins:test NAME=issue_recurring </pre> # [[Common_git_operations#Merge-branch-into-master|Merge]] all outstanding branches into master. # Rerun above tests on @master@ branch if there were: ## multiple branches merged, ## conflicts during merge. # Update source:README.md: *Features*, *Changelog* and compatibility list in *Installation* paragraphs. # Bump plugin version number in source:init.rb. # Commit and push changes. # Create and push git tag with new version number: <pre> $ git tag -a 1.1 $ git push origin 1.1 </pre> # Close corresponding issues (if not closed by appropriate commit messages). # Update plugin information on https://redmine.org/plugins/issue-recurring # Add release news on IT https://it.michalczyk.pro/projects/issue-recurring/news # Add new version on IT https://it.michalczyk.pro/projects/issue-recurring/settings/versions to _IT -> Issue recurring project -> Settings -> Versions_