Issue recurring

h1. Preparing new release

# Silence warnings (Redmine creates many of them) and make sure all tests pass on each merged issue branch, on all supported Redmine versions:

## make sure _./lib/tasks/redmine.rake_ contains @t.warning = false@ in description of plugins tests:

<pre>

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

</pre>

## run tests:

<pre>

$ rake redmine:plugins:test NAME=issue_recurring

</pre>

# Sync locale strings across language files (add test to check for differences?).

# [[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