Preparing new release » History » Revision 28
Revision 27 (cryptogopher, 2022-07-24 21:20) → Revision 28/37 (cryptogopher, 2022-09-01 14:37)
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:
<pre>
RAILS_ENV=test bundle exec rake db:drop db:create db:migrate redmine:plugins:migrate redmine:load_default_data
</pre>
## run tests:
<pre>
RAILS_ENV=test bundle exec rake redmine:plugins:test NAME=issue_recurring
</pre>
## (only for Redmine 4.0) run system tests separately:
<pre>
RAILS_ENV=test bundle exec ruby plugins/issue_recurring/test/system/issue_recurrences_test.rb
</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