Discussion on proposed changes to the release process:
Continuing from: Release team meeting agenda 2022-03-16
-
Single branching procedure for all projects
-
Single release owner
-
Single release process
1 Like
Apologies I waited to long to edit the post above but here is the overall results of this meeting:
Discussion on proposed changes to the release process:
Continuing from: Release team meeting agenda 2022-03-16
-
Single branching procedure for all projects
Merging the procedures in tool-belt-
Foreman may need to stop relying on documentation at theforeman.org and go to docs.theforeman.org – this is a big difference in the current procedure.
-
theforeman-rel-eng may also need to be updated so that Foreman and Katello are one project? – This may need to also be investigated more as the scripts may need to be updated.
-
Koji configs may need to be updated in tool-belt to be on file or we can keep it as two files, but have the tool-belt koji command use a foreman and katello config.
-
-
Single release process
-
Many of the concerns from the branch procedure also apply to this process.
-
Consolidating Jenkins jobs so they will release foreman and Katello rpms.
-
-
Single release owner
-
An immediate concern would be what if the release owner was not as comfortable with the code base would they be able to deal with merge conflicts from cherry-picks as a release goes on. We may want to have at least other members who would be able to confirm the cherry-picks for a release quickly.
-
An advantage of this is it could really speed up the process in general and remove overhead of having to re-familiarize with the process.
-
If it was one person would be something that would take a significant amount of time/ be something that requires more dedication? Hopefully by taking time to automate more of the porcess this time wouldn’t be too much.
-
1 Like