From Fedora Project Wiki
< Changes
Pungi Refactor
Summary
Changing how pungi works to make composes more distributed and transparent.
Owner
- Name: Dennis Gilmore
- Email: dennis@ausil.us
- Release notes owner:
Current status
Detailed Description
Changing how pungi works to make composes, we aim to achieve a few goals.
- Always do a complete compose, including rawhide and branched. Essentially we will have TC composes daily.
- Make sure that the tools used to make Fedora translate directly to making RHEL
- Enable more people to be involved in the development of compose tools
- Farm off compose tasks to hosts in koji
Benefit to Fedora
- Faster composes
- More frequent composes
- Nightly composes will look the same as a release compose
- More transparent and publicly visible logs.
- More people able to work on the tools used to make Fedora
Scope
- Proposal owners: Extend the functionality of pungi and koji
- Other developers: NA
- Release engineering: This will be a major change in how releng does composes
- List of deliverables: N/A
- Policies and guidelines: releng docs on how to do composes will need updating
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
There will be no changes to existing installs, The release tree will probably look a little differently and some files will have different names
How To Test
TODO
User Experience
Fedora Composes may look a bit different to previously but have all the same functionality.
Dependencies
livemedia-creator change
Contingency Plan
If we are unable to get the compose process changed before Alpha Change freeze we will revert to using the old method of composing Fedora.
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: Alpha Change freeze
- Blocks release? Yes
- Blocks product? All
Documentation
https://pagure.io/docs/releng/ https://pagure.io/docs/pungi/