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.

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

Write a blog post about downstream jobs targeting Fedora package maintainers #802

Closed
6 tasks
nforro opened this issue Jan 10, 2024 · 2 comments · Fixed by #838
Closed
6 tasks

Write a blog post about downstream jobs targeting Fedora package maintainers #802

nforro opened this issue Jan 10, 2024 · 2 comments · Fixed by #838
Assignees
@lbarcziova
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/documentation Documentation needs updates.

Comments

@nforro
Copy link
Member

nforro commented Jan 10, 2024

We do have Fedora releases guide but Fedora maintainers are still getting confused by seeing upstream jobs mentioned. Write a blog post that:

  • demonstrates a basic configuration (pull_from_upstream, koji_build, bodhi_update) in dist git
  • explains how to verify the config with CLI, how to test/run locally
  • explains how/when the jobs are triggered by the service, how to trigger them manually
  • explains issue_repository
  • does not mention propose_downstream or any other upstream jobs

As a bonus:

  • explains why upstream_project_url is needed (and upstream_tag_template)
@nforro nforro added the kind/documentation Documentation needs updates. label Jan 10, 2024
@lachmanfrantisek lachmanfrantisek added complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. area/fedora Related to Fedora ecosystem labels Jan 11, 2024
@lachmanfrantisek lachmanfrantisek moved this from new to ready-to-refine in Packit Kanban Board Jan 11, 2024
@lachmanfrantisek lachmanfrantisek moved this from ready-to-refine to priority-backlog in Packit Kanban Board Jan 25, 2024
@majamassarini majamassarini moved this from priority-backlog to refined in Packit Kanban Board Feb 1, 2024
@lbarcziova
Copy link
Member

I would lean towards having this as a part of "regular docs" and not a blogpost, probably as a subsection of Fedora releases guide.

@nforro
Copy link
Member Author

nforro commented Feb 1, 2024

Making it part of the docs definitely makes sense, a blogpost was just the first thing that came to mind.

@lbarcziova lbarcziova moved this from refined to in-progress in Packit Kanban Board Feb 20, 2024
@lbarcziova lbarcziova self-assigned this Feb 20, 2024
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Feb 21, 2024
@lbarcziova
Restructure Fedora release guide
590dc3d 
Create a dedicated subsection for dist-git repository onboarding.
Include also new information suggested in packit#802

Fixes packit#802
@lbarcziova lbarcziova mentioned this issue Feb 21, 2024
Merged
3 tasks
@lachmanfrantisek lachmanfrantisek mentioned this issue Feb 22, 2024
Closed
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Feb 27, 2024
@lbarcziova
Restructure Fedora release guide
4840ea0 
Create a dedicated subsection for dist-git repository onboarding.
Include also new information suggested in packit#802

Fixes packit#802
@lbarcziova lbarcziova moved this from in-progress to in-review in Packit Kanban Board Feb 27, 2024
lbarcziova added a commit that referenced this issue Feb 27, 2024
@lbarcziova
Downstream guide (#838)
fccd4d7 
Fixes #802 
Fixes #825 
Fixes #665 

When reviewing, it is probably best to go commit by commit.

TODO:

- [ ] agree on the restructure
- [x] fix broken links (check also other repos)
- [x] create docs for CLI pull-from-upstream 

RELEASE NOTES BEGIN

N/A

RELEASE NOTES END
@github-project-automation github-project-automation bot moved this from in-review to done in Packit Kanban Board Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lbarcziova lbarcziova

Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/documentation Documentation needs updates.
Projects
Packit Kanban Board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Downstream guide lbarcziova/packit.dev
3 participants
@nforro @lachmanfrantisek @lbarcziova