infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 5 Projects Releases Packages Wiki Activity Actions

Update Final Release SOP #371

Open
patrikp wants to merge 1 commit from sop_update into master
pull from: sop_update
merge into: infrastructure:master
Conversation 8 Commits 1 Files changed 1 +193 -32
patrikp commented 2025-04-12 10:05:52 +00:00
Contributor
Copy link

Signed-off-by: Patrik Polakovič patrik@alphamail.org

Signed-off-by: Patrik Polakovič <patrik@alphamail.org>
jnsamyak commented 2025-04-14 08:56:32 +00:00
Contributor
Copy link

Looks good to me. In the beginning, there are some indentation changes that will render a similar result, I guess, but it's good to maintain the clarity of the document.

Otherwise, the changes seem right. There was an introduction of a checksum file and the stag-release file, which was actually the splitter script of the latter.

Additional Notes

Just make sure to include the following in your changes (some are already there, but I wanted to ensure everything is covered):

  • For this process, Sigul setup is required.
  • The respective script should be run with the correct mount and on a machine that has Sigul configured.
  • For the Bodhi commands:
    • Ensure your Bodhi client configuration is properly set up.
    • You need the right ACLs (I think sysadmin-bodhi will do the trick).

Verification

At the end, verification is done to check for the tag. For example:

name: f42-updates
success: True

Make sure to check if there are any pending updates to the section. This might be misleading since we also do a final push. It is generally run as part of cron later, but if someone wants to avoid weekend hiccups, they should do it manually on stage release day, which often falls on Friday.

Looks good to me. In the beginning, there are some indentation changes that will render a similar result, I guess, but it's good to maintain the clarity of the document. Otherwise, the changes seem right. There was an introduction of a checksum file and the `stag-release` file, which was actually the splitter script of the latter. ## Additional Notes Just make sure to include the following in your changes (some are already there, but I wanted to ensure everything is covered): - For this process, **Sigul** setup is required. - The respective script should be run with the correct mount and on a machine that has **Sigul** configured. - For the **Bodhi** commands: - Ensure your Bodhi client configuration is properly set up. - You need the right ACLs (I think `sysadmin-bodhi` will do the trick). ## Verification At the end, verification is done to check for the tag. For example: ``` name: f42-updates success: True ``` Make sure to check if there are any pending updates to the section. This might be misleading since we also do a final push. It is generally run as part of `cron` later, but if someone wants to avoid weekend hiccups, they should do it manually on **stage release day**, which often falls on **Friday**.
jnsamyak commented 2025-04-14 08:58:59 +00:00
Contributor
Copy link

Add one more section:

Release Day (Tuesday @ 14:00 UTC)

On release day (usually Tuesday, 14:00 UTC), make sure to:

  • Check that torrents are published and seeding properly.
  • Unhide the directories that were hidden as part of the stage-release script — these should now be made available to the public.
  • This step ensures that the content officially becomes public and everything is accessible after the release GO decision.
Add one more section: ### Release Day (Tuesday @ 14:00 UTC) On release day (usually Tuesday, 14:00 UTC), make sure to: - **Check that torrents are published and seeding properly.** - **Unhide the directories** that were hidden as part of the `stage-release` script — these should now be made available to the public. - This step ensures that the content officially becomes public and everything is accessible after the **release GO** decision.
patrikp commented 2025-04-14 12:15:23 +00:00
Author
Contributor
Copy link

rebased onto b52b32f2d9

rebased onto b52b32f2d93ebb7e65aa72998b9ca0ec72f1b80a
kevin commented 2025-04-14 18:02:13 +00:00
Contributor
Copy link

Only the signing one needs sigul. The other one can be run on any compose machine with /pub rw (typically compose-x86-01, but I suppose it could also be bodhi-backend01)

Only the signing one needs sigul. The other one can be run on any compose machine with /pub rw (typically compose-x86-01, but I suppose it could also be bodhi-backend01)
kevin commented 2025-04-14 18:04:49 +00:00
Contributor
Copy link

This should be moved to Monday, the day before release. We want to have the torrents up in advance so people can download the content to seed it to other users.
We don't typically announce this widely, just to those folks who normally seed torrents.

This should be moved to Monday, the day before release. We want to have the torrents up in advance so people can download the content to seed it to other users. We don't typically announce this widely, just to those folks who normally seed torrents.
kevin commented 2025-04-14 18:06:36 +00:00
Contributor
Copy link

This should be moved to monday night (late) before the release. This is to allow mirrors that are not tier1 (and don't have access to pre-release content) to start syncing up, so that more of them are in sync by the time of the actual release announcement.
We typically don't announce this widely either. Mirrors will just start syncing it, we don't need to tell users about it.

This should be moved to monday night (late) before the release. This is to allow mirrors that are not tier1 (and don't have access to pre-release content) to start syncing up, so that more of them are in sync by the time of the actual release announcement. We typically don't announce this widely either. Mirrors will just start syncing it, we don't need to tell users about it.
kevin commented 2025-04-14 18:07:14 +00:00
Contributor
Copy link

A few minor comments, but otherwise looks good! Thanks for updating this!

A few minor comments, but otherwise looks good! Thanks for updating this!
patrikp commented 2025-04-15 10:03:34 +00:00
Author
Contributor
Copy link

rebased onto b52b32f2d9

rebased onto b52b32f2d93ebb7e65aa72998b9ca0ec72f1b80a
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin sop_update:sop_update
git checkout sop_update

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff sop_update
git checkout sop_update
git rebase master
git checkout master
git merge --ff-only sop_update
git checkout sop_update
git rebase master
git checkout master
git merge --no-ff sop_update
git checkout master
git merge --squash sop_update
git checkout master
git merge --ff-only sop_update
git checkout master
git merge sop_update
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
rerwite-required

   
SOP

   
untriaged
No labels
rerwite-required
SOP
untriaged
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/infra-docs-fpo#371
No description provided.
Delete branch "sop_update"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?