1. Arbitrary Branching The Upstream Pivot Matt Prahl Presented by
Software Engineer, Red Hat

2. Topics 1. What is arbitrary branching?
2. Why was arbitrary branching implemented?
3. What tooling changes took place?
4. How to get an arbitrary branch?

3. What is an Arbitrary Branch?
Branches other than f26, f25, epel7, etc.
Usually something that maps to upstream such as a major version number
Branches that have their own “service levels”, not tied to the service level of a Fedora release

4. Current Service Levels

5. Why “Arbitrary Branching”?

6. Beneficial To Modularity
Modularity is an ongoing initiative to resolve the issue of divergent, occasionally conflicting lifecycles of different components.

7. Tooling Changes

8. Architectural Decisions
Option One: Modify PkgDB to support “arbitrary branching”
Option Two: Join up with the Pagure over dist-git efforts and supplement it with PDC APIs
Had to add Arbitrary Branching support while maintaining the old way

9. Pagure over dist-git

10. PDC

11. Changes This Caused... New tool: fedrepo-req
New branches in git require PDC entries
Forking and pull requests are allowed
ACLs:
Repo wide
Handled through the UI

12. Changes This Caused
Bugzilla default assignee overrides and monitoring are set in pagure.io/releng/fedora-scm- requests
Orphaned packages
Retired packages

13. How Do I Use This?

14. fedrepo-req Examples How to request a new repo
fedrepo-req reponame -t 12345
How to request a standard branch
fedrepo-req-branch reponame f26
How to request an arbitrary branch
fedrepo-req-branch reponame sl security_fixes: sl bug_fixes:

15. fedrepo-req-admin

16. fedrepo-req-admin Demo

17. Created Project

18. PDC Entry

19. Monitoring Entry

20. Summary
Arbitrary branches are branches that have service levels not tied to a Fedora release
Arbitrary branches enable Modularity
Pagure over dist-git is the new interface to dist-git
Packaging requests are done through fedrepo- req

21. Questions?
Contact: