Skip to content

Commit

Permalink
Start the RC1 release procedure after branching
Browse files Browse the repository at this point in the history
  • Loading branch information
ekohl committed Aug 31, 2023
1 parent 207816e commit ecdf905
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions procedures/foreman/branch.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,9 @@ The next step should only be done after all branching, including packaging, has

## Release Owner

- [ ] Generate and post the release procedure, if not already posted:
- [ ] Use <%= rel_eng_script('procedure_release') %>: `PROJECT=foreman VERSION=<%= release %> ./procedure_release "<%= target_date %>" "<%= owner %>" "<%= engineer %>"
- [ ] Post the output in [Development/Releases](https://community.theforeman.org/c/development/releases/20) using `Foreman <%= release %>.0-rc1 release process`
- [ ] Create the <%= release %>.0-rc release procedure in [Development/Releases](https://community.theforeman.org/c/development/releases/20): `PROJECT=foreman VERSION=<%= release %> ./procedure_release <%= target_date %> '<%= owner %>' '<%= engineer %>' | wl-copy`
- [ ] Create a `Foreman <%= develop %> Schedule and Planning` post on [Development/Releases](https://community.theforeman.org/c/development/releases/20) using <%= rel_eng_script('schedule') %>
- [ ] Create Redmine version <%= develop %>.0 and make sure it is shared with subprojects in [foreman](https://projects.theforeman.org/projects/foreman/settings/versions)
Expand Down

0 comments on commit ecdf905

Please sign in to comment.