From Fedora Project Wiki
| Line 20: | Line 20: | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?statuses=145,146,151,182&tags=pungi Pungi 4 upgrade and Pungi roadmap] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?statuses=145,146,151,182&tags=pungi Pungi 4 upgrade and Pungi roadmap] | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/315 Layered image builds] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/315 Layered image builds] | ||
** [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/355 OpenShift in Fedora] | |||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/303 Move to livemedia-creator for live cds & disk images] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/303 Move to livemedia-creator for live cds & disk images] | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?statuses=145,146,151,182&tags=auto_signing Content signing can be automated through Sigul or another tool] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?statuses=145,146,151,182&tags=auto_signing Content signing can be automated through Sigul or another tool] | ||
Revision as of 22:34, 11 November 2015
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
- PDC deployed & populated with product / release data
- Pungi 4 upgrade and Pungi roadmap
- Layered image builds
- Move to livemedia-creator for live cds & disk images
- Content signing can be automated through Sigul or another tool
- Signed repos in koji
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)
- 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
- 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)