Move Redmine steps until after tagging

Until a release has been tagged, things can still be added and the bot
could set the wrong Fixed in Release values.

procedures/foreman/release.md.erb

@@ -17,14 +17,8 @@
 
 ## Release Owner
 
-<% unless is_rc -%>
-- [ ] Add a new [Redmine version](https://projects.theforeman.org/projects/foreman/settings/versions) for the next minor, unless the series is EOL. Be sure the version is set to sharing with subprojects.
-<% end -%>
 - [ ] Remove/change target version field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
 - [ ] Ensure that code in git matches issues fixed in <%= full_version %> in redmine. [issues](https://github.com/theforeman/theforeman-rel-eng/blob/master/issues) can be used to generate a comparison between the two.
-<% unless is_rc -%>
-- [ ] Change Redmine version <%= full_version %> state to Closed using <%= rel_eng_script('close_redmine_version') %>
-<% end -%>
 
 # Tagging a release: <%= target_date %>
 
@@ -42,6 +36,10 @@
   - [ ] Create tags using <%= rel_eng_script('tag_project') %>
   - [ ] Push tags using <%= rel_eng_script('tag_push') %>
 - [ ] Run the Jenkins [Tarballs Release](https://ci.theforeman.org/job/tarballs-release/) using <%= rel_eng_script('release_tarballs') %> to create tarballs
+<% unless is_rc -%>
+- [ ] Change Redmine version <%= full_version %> state to Closed using <%= rel_eng_script('close_redmine_version') %>
+- [ ] Add a new [Redmine version](https://projects.theforeman.org/projects/foreman/settings/versions) for the next minor, unless the series is EOL. Be sure the version is set to sharing with subprojects.
+<% end -%>
 
 ## Release Engineer