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

Fix small typos in Katello branching and release processes; add helpful clarifications #472

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

qcjames53
Copy link
Contributor

@qcjames53 qcjames53 commented Feb 26, 2025

Fix small typos in Katello branching and release processes; add helpful clarifications.

I was routinely running into small discrepancies between the Foreman and Katello branching and release process scripts. I have made several changes to fix small issues in the processes and to clarify some sticking points:

  • The branching instructions now name the first release candidate as VERSION.rc1 instead of VERSION-rc1. Katello differs from Foreman in that we use dots for release candidates.
  • Cherry pick instructions add the necessary PROJECT and VERSION bash variables.
  • A few ./tools are now ./tools.rb.
  • Developers are told they can skip the foreman-documentation section after rc1 if there are no new headline features or contributors.
  • Added a shell command to generate an alphabetized contributors list.
  • Changelog instructions add the necessary PROJECT and VERSION bash variables.
  • Final release tagging instructions lead to a detached head state so the git push command has been modified to allow pushes to upstream from this state.
  • Katello gem pushes require 2FA; instructions have been modified to reflect this.
  • Added instructions for how to generate release instructions for the next release.

@@ -99,7 +99,7 @@ Note: If for some reason there was an issue with the tarballs that required uplo
<% if is_first_rc || (!is_rc && !is_first_ga) -%>
- Add `topics/foreman-<%= version %>.adoc` to `guides/doc-Release_Notes/master.adoc`: `sed -i '/x.y.z releases here/a include::topics/foreman-<%= version %>.adoc[leveloffset=+1]' guides/doc-Release_Notes/master.adoc`
<% end -%>
- Make sure [foreman-contributors.adoc](https://github.com/theforeman/foreman-documentation/blob/<%= short_version %>/guides/doc-Release_Notes/topics/foreman-contributors.adoc) is updated
- Update [foreman-contributors.adoc](https://github.com/theforeman/foreman-documentation/blob/<%= short_version %>/guides/doc-Release_Notes/topics/foreman-contributors.adoc) with the list of contributors using `git log --since="<YYYY-MM-DD of previous major release branching>" --format="%an" | sort | uniq`. Manually clean up any erroneous entries.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have https://github.com/theforeman/theforeman.org/blob/gh-pages/scripts/committers.rb that should be used.

That repo also contains a longer .mailmap to map bad entries to normal users. To use those, it uses %aN instead. It's also based on git tags, not dates.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow that's a helpful script. I'll adjust this PR in a bit to reflect this info. Thanks, Ewoud!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ekohl is there a way to run this script with the Katello repo? Is katello an option for --with-repo? I'd be happy to add it to the release process but unfortunately did not have enough time to figure this out.

@@ -32,7 +32,7 @@
<% unless is_rc && !full_version.end_with?('1') -%>
- Add `topics/katello-<%= version %>.adoc` to `guides/doc-Release_Notes/master.adoc`: `sed '/x.y.z releases here/a include::topics/katello-<%= version %>.adoc[leveloffset=+1]' master.adoc`
<% end -%>
- Make sure [katello-contributors.adoc](https://github.com/theforeman/foreman-documentation/blob/<%= foreman_version %>/guides/doc-Release_Notes/topics/katello-contributors.adoc) is updated
- Update [katello-contributors.adoc](https://github.com/theforeman/foreman-documentation/blob/<%= foreman_version %>/guides/doc-Release_Notes/topics/katello-contributors.adoc) with the list of contributors using `git log --since="<YYYY-MM-DD of previous major release branching>" --format="%an" | sort | uniq`. Manually clean up any erroneous entries.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance we could standardize things by using the same script or reuse as much as possible?

@qcjames53 qcjames53 changed the title Add contributors shell command to Foreman and Katello release process Fix small typos in Katello branching and release processes; add helpful clarifications Mar 4, 2025
@qcjames53 qcjames53 force-pushed the master branch 2 times, most recently from 61c2649 to f2d69b0 Compare March 4, 2025 22:48
@qcjames53
Copy link
Contributor Author

I kept track of every minor issue with the Katello branching and release processes and added the tweaks to this PR.

I would be happy to clone the parts that make sense to the Foreman script in the not too distant future but I unfortunately don't have the time for that today.

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

Successfully merging this pull request may close these issues.

2 participants