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 1.41.1 #3478

Merged
merged 2 commits into from
Jan 27, 2025
Merged

Release 1.41.1 #3478

merged 2 commits into from
Jan 27, 2025

Conversation

thrix
Copy link
Collaborator

@thrix thrix commented Jan 23, 2025

Hotfix Checklist

  • Create a new branch from the fedora branch
  • Use git cherry-pick to apply the selected change
  • Mention the hotfix release on the release page
  • Add a Release x.y.z commit, empty if needed: git commit --allow-empty -m "Release x.y.z"
  • Create a new pull request with the target branch set to fedora
  • Make sure that tests pass and merge the pull request
  • Tag the commit and publish the release in the same way as for regular release
  • Create a pull request with the hotfix release notes changes, see Add 1.41.1 release notes #3479

Create a new github release based on the tag above

  • Mention the most important changes in the name, do not include version
  • Use ; as a delimiter, when multiple items are mentioned in the name
  • Push the “Generate release notes” button to create the content
  • Prepend the “See the release notes for the list of interesting changes.” line Publish the release, check Fedora pull requests, make sure tests pass and merge

Finally, if everything went well:

  • Close the corresponding release milestone
  • Once the non development copr build is completed, move the quay branch to point to the release commit as well to build fresh container images.

Handle manually what did not went well:

  • If the automation triggered by publishing the new github release was not successful, publish the fresh code to the pypi repository manually using make wheel && make upload
  • If there was a problem with creating Fedora pull requests, you can trigger them manually using /packit propose-downstream in any open issue.

Fedora Rawhide moved files under `/usr/bin`, therefore paths no longer
work. Let's hope packages will work, everywhere, and that the required
files are not shipped by some other packages on an obscure distro
release.
Signed-off-by: Miroslav Vadkerti <[email protected]>
@thrix thrix self-assigned this Jan 23, 2025
@thrix
Copy link
Collaborator Author

thrix commented Jan 23, 2025

/packit test

@thrix
Copy link
Collaborator Author

thrix commented Jan 23, 2025

/packit rebuild-failed

@psss psss added the packaging Changes related to the rpm packaging label Jan 24, 2025
@thrix thrix added the ci | full test Pull request is ready for the full test execution label Jan 24, 2025
@thrix
Copy link
Collaborator Author

thrix commented Jan 24, 2025

/packit test

@thrix
Copy link
Collaborator Author

thrix commented Jan 26, 2025

/packit retest

@thrix
Copy link
Collaborator Author

thrix commented Jan 26, 2025

/packit retest-failed

@thrix
Copy link
Collaborator Author

thrix commented Jan 27, 2025

/packit build

@thrix
Copy link
Collaborator Author

thrix commented Jan 27, 2025

All tests failures are caused by #3487 and rawhide needs this fix.

Merging.

@thrix thrix merged commit a3a8b33 into fedora Jan 27, 2025
12 of 17 checks passed
@thrix thrix deleted the release-1.41.1 branch January 27, 2025 07:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci | full test Pull request is ready for the full test execution packaging Changes related to the rpm packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants