-
Notifications
You must be signed in to change notification settings - Fork 80
Small improvements for the hotfix SOP #4126
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
Open
FrostyX
wants to merge
3
commits into
fedora-copr:main
Choose a base branch
from
FrostyX:doc-hotfix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,57 +12,59 @@ Preparation | |
|
|
||
| This is required if you are doing the first hotfix since last regular release. If somebody already did the hotfix, you can skip this section. | ||
|
|
||
| Create hotfix branch ($DATE is date of last release): | ||
| Create hotfix branch ($DATE is date of last release):: | ||
|
|
||
| git branch hotfix-$DATE | ||
| git checkout hotfix-$DATE | ||
|
|
||
| Return in history to commit that points to latest commit tagging packages for the release. If multiple packages were tagged during the release, choose the commit related to latest package in the release: | ||
| Return in history to commit that points to latest commit tagging packages for the release. If multiple packages were tagged during the release, choose the commit related to latest package in the release:: | ||
|
|
||
| git reset --hard $SHA1 | ||
|
|
||
| Push the branch to remote: | ||
| Push the branch to remote:: | ||
|
|
||
| git push origin hotfix-$DATE:hotfix-$DATE | ||
|
|
||
| Commit the changes: | ||
| Commit the changes:: | ||
|
|
||
| git commit -a -m 'set up hotfix branch' | ||
|
|
||
| Backport fix | ||
| ------------ | ||
|
|
||
| If you skipped previous part because the branch exists then do: | ||
| If you skipped previous part because the branch exists then do:: | ||
|
|
||
| git checkout hotfix-$DATE | ||
|
|
||
| Apply the fix from `main` branch. $SHA1 is commit you want to backport. | ||
| Apply the fix from `main` branch. $SHA1 is commit you want to backport:: | ||
|
|
||
| git cherry-pick -x $SHA1 | ||
|
|
||
| Run: | ||
| Run:: | ||
|
|
||
| tito report --untagged-commits | ||
|
|
||
| and walk the directories of packages listed. For every SPEC file make sure that `Version` tag has `.hotfix.0` at the end. | ||
| This ensure that the hotfix version is higher than any rebuild in Fedora. | ||
| This ensure that the hotfix version is higher than any rebuild in Fedora:: | ||
|
|
||
| 1.1-5 < 1.1.hotfix.0-1 | ||
|
|
||
| Tag every package that was listed in the step above: | ||
| Tag every package that was listed in the step above:: | ||
|
|
||
| # TODO This should increment to .hotfix.1-1 but for me it did .hotfix.0-2 | ||
| # Which is a problem because `tito release fedora-git` couldn't handle it | ||
| tito tag | ||
| # workarounded by | ||
| tito tag --use-version 1.1.hotfix.1 --use-release "1%{?dist}" | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
|
|
||
| Push the changes: | ||
| Push the changes:: | ||
|
|
||
| git push --follow-tags origin | ||
|
|
||
| Build packages | ||
| -------------- | ||
|
|
||
| At this point in time, we have those files most likely patched in production. So you can take a time and follow | ||
| how to `build packages`_. | ||
| how to :ref:`build packages<build_packages_for_production>` | ||
|
|
||
| When packages are build, you should run the Ansible playbook and make sure everything runs smoothly. | ||
|
|
||
| .. _`build_packages`: https://docs.pagure.org/copr.copr/how_to_release_copr.html#build-packages-for-production | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.