Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release procedure for patch releases should include a note about bumping projects with no updates #513

Open
ehelms opened this issue Mar 13, 2023 · 2 comments

Comments

@ehelms
Copy link
Member

ehelms commented Mar 13, 2023

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.

@ekohl
Copy link
Member

ekohl commented Mar 13, 2023

I've aimed to keep the procedure short, so it's only a procedure. However, we certainly need explanations. https://projects.theforeman.org/projects/foreman/wiki/Release_Process hasn't been updated for a while.

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.

@ehelms
Copy link
Member Author

ehelms commented Mar 13, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants