From Fedora Project Wiki
Monthly Stakeholder Meetings
- Atomic stakeholder meetings
- Matt Miller notes (representing RHEL, Council, etc)
- Fedora QE
- Workgroups: Workstation, Server, Cloud, Base, Env & Stacks - contacts TBD
Priorities
Immediate Priorites
- 2 week Atomic content
- Documented policy and process for contributing to upstream tools
- Design Only: Re-design atomic release process
- 2 week Atomic improvements
- Development & Deployment Process Improvement / Standardization
F24 Commitments
| Deliverable | Approval Status | Dev Status | Notes |
|---|---|---|---|
| Layered image builds | Peer Review | Not Started | Includes work for OpenShift in Fedora below |
| OpenShift in Fedora | Peer Review | In Progress | |
| PDC deployed & populated with product / release data | Accepted | Not Started | |
| Pungi 4 upgrade and Pungi roadmap | Peer Review | Not Started | |
| Move to livemedia-creator for live cds & disk images | Peer Review | Not Started | |
| Content signing can be automated through Sigul or another tool | Planning | Not Started | |
| Signed repos in koji | Submitted | In Progress |
Backlog
Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team!
- Documentation of rel-eng process so that internal release engineers can contribute
- Atomic redesigned workflow & toolchain
- Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc (probably needed for F25)
- Move to createrepo_c (probably for F25)
- Method for releasing zero day fixes quickly - https://fedorahosted.org/rel-eng/ticket/5886
- Docker images can be built in Oz / ImageFactory for all supported arches
- Second tier PDC use case implementation
- Bodhi support for non-rpm content
- Consolidate hubs for primary and secondary arches
- RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc)
- Taskotron (cluster testing for Atomic in Taskotron)
- Koji 2.0
- ET / Bodhi alignment
- RHEL.next support
- Ability to create embargoed builds in tools (at least koji & bodhi) and lift the embargo after release so that security can get embargoed changes out quickly
- Any opportunities for leveraging Level 1 support
- rel-eng scripts cleanup
- rel-eng tools are not easily testable or contributed to
- changes can be tested in an integrated environment before releasing to production
- Critical system / use case integration with gilmsg where appropriate in release tooling
- Development release gating with sanity testing / stability
- Fedora Rings / Alephs
- Layered images _not_ from RPMs — source-to-image or other
- Releng CI (on Jenkins)