Preparing new release¶

1. Silence warnings (Redmine creates many of them) and make sure all tests pass on each merged issue branch, on all supported Redmine versions:
   1. make sure ./lib/tasks/redmine.rake contains t.warning = false in description of plugins tests:
      

      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:
      

      $ rake redmine:plugins:test NAME=issue_recurring
      

2. Sync locale strings across language files.
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