From Fedora Project Wiki
(init mission)
(hint MVP, add simple workflow)
Line 18: Line 18:
  
 
Updating "simple" packages in rawhide should be as easy as merging a PR in dist-git if all tests and checks pass.
 
Updating "simple" packages in rawhide should be as easy as merging a PR in dist-git if all tests and checks pass.
 +
 +
===== Workflow =====
 +
 +
1. Set up a source-git repository manually on a packit-supported platform (github.com, gitlab.com)
 +
  * This includes creating a specific branch and setting up jobs for packit-service to handle events.
 +
  * CI is set up (such as [https://packit.dev/docs/testing-farm/ Testing Farm]).
 +
2. Anyone in the community is able to interact with this repository the same way with any other open-source project.
 +
3. Packit-service should accept an event when a new upstream release is done (via [https://release-monitoring.org/ Upstream Release Monitoring]).
 +
4. Packit-service creates a pull request which contains the new release in the repository.
 +
  * A dist-git PR is created in parallel. Downstream checks are synchronized to the source-git PR.
 +
5. The owner of the source-git repository reviews and updates the pull request as needed.
 +
6. Once approved, dist-git PR is merged first and packit-service triggers a build. If the build passes, source-git PR is merged as well. If the build fails, source-git PR is updated a new dist-git PR is created and this step happens again.
  
 
==== More convenient way to work on downstream patches ====
 
==== More convenient way to work on downstream patches ====
  
 
Track patches as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.
 
Track patches as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.
 +
 +
 +
==== MVP ====
 +
 +
The "product" of this SIG should be implementation of a following MVP. Once that's done, we'll evaluate where we want to head next.
  
 
== Members ==
 
== Members ==

Revision as of 14:29, 24 March 2021

Mission

This SIG is a work in progress and will be announced properly once we're ready, stay tuned.

We would like to offer and alternative way to maintain Fedora Linux packages in comparison to the traditional way via dist-git.

Rules

  • Whatever we produce here, it MUST NOT violate Fedora Packaging Guidelines (we should strive to change them if needed).
  • Maintainers HAVE TO be able to step in for automation and replace some of its actions if needed.
  • Proven packagers and rel-eng still needs to be able to do their work in dist-git: their workflows NEED to keep working the same way.

Goals

For start, we would love to focus on two areas:

Easier maintenance for rawhide

Updating "simple" packages in rawhide should be as easy as merging a PR in dist-git if all tests and checks pass.

Workflow

1. Set up a source-git repository manually on a packit-supported platform (github.com, gitlab.com)

 * This includes creating a specific branch and setting up jobs for packit-service to handle events.
 * CI is set up (such as Testing Farm).

2. Anyone in the community is able to interact with this repository the same way with any other open-source project. 3. Packit-service should accept an event when a new upstream release is done (via Upstream Release Monitoring). 4. Packit-service creates a pull request which contains the new release in the repository.

 * A dist-git PR is created in parallel. Downstream checks are synchronized to the source-git PR.

5. The owner of the source-git repository reviews and updates the pull request as needed. 6. Once approved, dist-git PR is merged first and packit-service triggers a build. If the build passes, source-git PR is merged as well. If the build fails, source-git PR is updated a new dist-git PR is created and this step happens again.

More convenient way to work on downstream patches

Track patches as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.


MVP

The "product" of this SIG should be implementation of a following MVP. Once that's done, we'll evaluate where we want to head next.

Members

Status

We have been in a planning stage of the SIG: bringing interested people together to flesh out the who, what, where, when, and how.

Communication

  • #packit on Freenode IRC
  • Mailing list - user-cont-team@redhat.com

Important links