Preparing new release » History » Revision 34
Revision 33 (cryptogopher, 2022-09-10 20:40) → Revision 34/37 (cryptogopher, 2022-09-10 20:41)
h1. Preparing new release # Sync locale strings across language files (add test to check for differences? or execute system tests in different locales?). # Make sure all tests pass on each merged issue branch, on all supported Redmine versions: ## Start in Redmine's directory: <pre> cd /var/lib/redmine </pre> ## (only before 1st run) prepare database (load default data separately, https://www.redmine.org/boards/2/topics/48044): database: <pre> RAILS_ENV=test bundle exec rake db:drop db:create db:migrate redmine:plugins:migrate RAILS_ENV=test bundle exec rake redmine:load_default_data </pre> (load default data separately, https://www.redmine.org/boards/2/topics/48044) ## run tests: <pre> RAILS_ENV=test bundle exec rake redmine:plugins:test NAME=issue_recurring </pre> ## (optionally) rerun failing tests separately: <pre> RAILS_ENV=test bundle exec ruby plugins/issue_recurring/test/integration/issue_recurrences_test.rb --name test_create_recurrence --verbose </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