You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An issue I ran into is that it's not obvious to go bump projects like foreman-selinux that may not receive any fixes when doing a patch release. The process should include a note saying (or a script helping to ensure) that all projects that require one get a version bump even if it's an "empty" release.
The text was updated successfully, but these errors were encountered:
Any idea what would be the best place to store this documentation?
If we do decide to replace koji I'd be inclined to move away from this repository and instead make https://github.com/theforeman/theforeman-rel-eng the primary place. So I'm hesitant to add the docs in this repo.
Turns out this mostly inspired by the fact that I had an error, and then projects were not getting auto-tagged and bumped (see theforeman/theforeman-rel-eng#194 (comment)). That led me down a path where I thought I had missed part of the procedure but was in actuality the script not completing. I think this particular issue can then be closed.
To your good question though, the obvious place in I thought of was exactly that -- https://github.com/theforeman/theforeman-rel-eng should be the place for all things documentation around release process.
An issue I ran into is that it's not obvious to go bump projects like foreman-selinux that may not receive any fixes when doing a patch release. The process should include a note saying (or a script helping to ensure) that all projects that require one get a version bump even if it's an "empty" release.
The text was updated successfully, but these errors were encountered: