Skip to content

Commit

Permalink
Move Redmine version creation
Browse files Browse the repository at this point in the history
The time between creating git branches and not having a Redmine version
existing means the target version is wrong. The original intent of the
procedure was that the release owner continued immediately with the
"Other systems" part after "Branching", but this makes it obvious it
needs to happen quickly after branching to minimize the window.
  • Loading branch information
ekohl committed Jul 8, 2024
1 parent 7bccb57 commit 334c468
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion procedures/foreman/branch.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,7 @@ The next step should only be done after all branching, including packaging, has

- [ ] Bump versions to <%= develop %>-develop using <%= rel_eng_script('develop_branch_bump') %>
- [ ] Push version bumps to <%= develop %>-develop using <%= rel_eng_script('develop_branch_push') %>
- [ ] Create Redmine version <%= develop %>.0 and make sure it is shared with subprojects in [foreman](https://projects.theforeman.org/projects/foreman/settings/versions)
- [ ] Ask Hammer maintainer to bump [hammer-cli](https://github.com/theforeman/hammer-cli) and [hammer-cli-foreman](https://github.com/theforeman/hammer-cli-foreman)

# Preparing build systems: <%= target_date %>
Expand Down Expand Up @@ -120,7 +121,6 @@ The next step should only be done after all branching, including packaging, has

- [ ] 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') %>: `./schedule <%= target_date + 1 %>` (make sure there are no conflicts with other important dates)
- [ ] Create Redmine version <%= develop %>.0 and make sure it is shared with subprojects in [foreman](https://projects.theforeman.org/projects/foreman/settings/versions)
- [ ] Ensure current Foreman deprecations for the next release are removed in __develop__

This was based on the [wiki procedure](https://projects.theforeman.org/projects/foreman/wiki/Release_Process#Branching-for-series) and sometimes has a bit more info.

0 comments on commit 334c468

Please sign in to comment.