10000 Release Responsible · Issue #825 · packit/agile · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Release Responsible #825

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.

Sign up for GitHub

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

Jump to bottom
Open
5 tasks
usercont-release-bot opened this issue May 30, 2025 · 0 comments
Open
5 tasks

Release Responsible #825

usercont-release-bot opened this issue May 30, 2025 · 0 comments
Assignees
@lachmanfrantisek
Labels
kind/role Regular chore for the role rotation

Comments

@usercont-release-bot
Copy link
Collaborator

Caution

DO NOT release Packit ≥ 1.0.0 to any of the Fedora releases that already reached the stable by the time of the 1.0.0 release, i.e., Packit CANNOT be released to any Fedora ≤ 41 and EPEL ≤ 9.

Check if there are changes worth releasing for all our RPM-packaged projects:

TODO

Note

Packit is used as an example package below.

  • Before creating new releases make sure that pending updates got to stable in Bodhi (if not, ask the team members for karma and wait for it).
  • Run Prepare a new release workflow via Run workflow button: choose main branch and type the correct version number for the new release. In a while, you should see the action running and creating a pull request in the repository.
  • Review the created PR - you can ask other team members to help you with changelog grammar, if needed. You can check out the PR locally, update it and push it back to the upstream.
    • If the Check release notes required check doesn't run, do a force-push or edit the PR description, that should trigger it.
  • Merge the pull request once you're fine with the content (and there are no pending review requests).
  • The merge of the PR should trigger an action that creates a draft release in the releases list. Edit the release, make sure the content is correct and then publish the release by clicking Publish release.
  • Make sure the package is uploaded to PyPI.

Caution

Do not merge dist-git PRs for Packit project and older releases (F40, F41, EPEL9), they are opened due to this bug.

  • Wait a few minutes, check and merge PRs in dist-git created by Packit.
    • Check that both services proposed the same set of changes.
    • Merge those created by the stage instance via pull_from_upstream (this will automatically close the Bugzilla from Upstream Release Monitoring)
    • Close the ones created by the production instance.
  • If you haven't released all 3 packages, make sure to tag the latest builds of those that weren't released into corresponding sidetags by commenting /packit-stg koji-tag --all-branches in any dist-git PR of the respective packages. This will trigger Koji build of packit and/or Bodhi update.
  • Wait a few minutes and verify that RPMs are built in Koji.
  • Wait a bit and verify that updates have been created in Bodhi.
  • Celebrate another release 🚀🎉
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lachmanfrantisek lachmanfrantisek

483F
Labels
kind/role Regular chore for the role rotation
Projects
Packit Kanban Board
Status: new
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lachmanfrantisek @usercont-release-bot
0