Skip to content

Add blog post about release synchronization under the hood#1149

Open
nforro wants to merge 2 commits into
packit:mainfrom
nforro:release-sync
Open

Add blog post about release synchronization under the hood#1149
nforro wants to merge 2 commits into
packit:mainfrom
nforro:release-sync

Conversation

@nforro

@nforro nforro commented Jul 10, 2026

Copy link
Copy Markdown
Member

No description provided.

@centosinfra-prod-github-app

Copy link
Copy Markdown
Contributor

@centosinfra-prod-github-app

Copy link
Copy Markdown
Contributor

@nforro nforro moved this from New to In review in Packit pull requests Jul 10, 2026

@majamassarini majamassarini left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nice! Thank you!
I was wondering if we should create a diagram from this document and link it at the bottom. I think it could be useful, to have something more visual.

a [release-monitoring.org](https://release-monitoring.org) event, configured in dist-git
- action - list of commands that can replace the default Packit implementation of a certain step
of the process
- hook - action that does nothing by default

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
- hook - action that does nothing by default
- hook - action that does nothing by default and is meant to be customized by the users

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Why? Isn't it implied?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

not a big deal, from my point of view, for a new user, it is not so explicit.

<!--truncate-->

`propose_downstream` and `pull_from_upstream` share most of the implementation. One notable
difference is that `pull_from_upstream` always uses the downstream spec file as a base for

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we add that it takes the specfile in the rawhide branch? Or is it too much detail?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Did you mean config file?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I could mention it, on the other hand, it feels a bit out of scope, this isn't an onboarding document.

@lbarcziova lbarcziova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

very nice work!!

Comment thread posts/release-synchronization/index.md Outdated
@nforro

nforro commented Jul 10, 2026

Copy link
Copy Markdown
Member Author

I was wondering if we should create a diagram from this document and link it at the bottom. I think it could be useful, to have something more visual.

Let me try to add something.

nforro added 2 commits July 10, 2026 16:50
Signed-off-by: Nikola Forró <nforro@redhat.com>
Assisted-by: Claude Opus 4.6 via Claude Code
It is not actually called and it only confuses users.

Signed-off-by: Nikola Forró <nforro@redhat.com>
Assisted-by: Claude Opus 4.6 via Claude Code
@centosinfra-prod-github-app

Copy link
Copy Markdown
Contributor

@nforro

nforro commented Jul 10, 2026

Copy link
Copy Markdown
Member Author

I was wondering if we should create a diagram from this document and link it at the bottom. I think it could be useful, to have something more visual.

I've added a mermaid diagram at the end, not sure if that's what you meant, but I think it brings some value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

4 participants