Preparing new release¶

1. Sync locale strings across language files (add test to check for differences? or execute system tests in different locales?).
2. Make sure all tests pass on each merged issue branch, on all supported Redmine versions:
   1. Redmine 3.4: silence warnings by adding t.warning = false in description of plugins tests in ./lib/tasks/redmine.rake:
      

      desc 'Runs the plugins integration tests.'
      Rake::TestTask.new :integration => "db:test:prepare" do |t|
        t.libs << "test" 
        t.verbose = true
        t.warning = false
        t.pattern = "plugins/#{ENV['NAME'] || '*'}/test/integration/**/*_test.rb" 
      end
      

   2. run tests:
      

      RAILS_ENV=test bundle exec rake redmine:plugins:test NAME=issue_recurring
      

   3. Redmine 4.0 and above: run system tests
      

      RAILS_ENV=test bundle exec ruby plugins/issue_recurring/test/system/issue_recurrences_test.rb
      

3. Merge all outstanding branches into master.
4. Rerun above tests on master branch if there were:
   1. multiple branches merged,
   2. conflicts during merge.
5. Update source:README.md: Features, Changelog and compatibility list in Installation paragraphs.
6. Bump plugin version number in source:init.rb.
7. Commit and push changes.
8. Create and push git tag with new version number:
   

   $ git tag -a 1.1
   $ git push origin 1.1
   

9. Close corresponding issues (if not closed by appropriate commit messages).
10. Update plugin information on https://redmine.org/plugins/issue-recurring
11. Add release news on IT https://it.michalczyk.pro/projects/issue-recurring/news
12. Add new version on IT https://it.michalczyk.pro/projects/issue-recurring/settings/versions