From Fedora Project Wiki
| Line 18: | Line 18: | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/202 Immediate Sigul support] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/202 Immediate Sigul support] | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_improvements&statuses=145,146,147,151,182 2 week Atomic improvements] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_improvements&statuses=145,146,147,151,182 2 week Atomic improvements] | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=process Release Tooling Team Development & Deployment Process Improvement / Standardization] | |||
== F24 Commitments == | == F24 Commitments == | ||
Revision as of 20:17, 19 October 2015
How We Prioritize
Monthly Stakeholder Meetings
* Atomic stakeholder meetings - http://etherpad.corp.redhat.com/FedoraAtomicPriorities * Matt Miller (representing RHEL, Council, etc) - http://etherpad.corp.redhat.com/FedoraMattPriorities * Fedora QE (Adam Williamson, Tim Flink) - ? * 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 (to include compose based testing, something closer to continuous releases, alignment with internal process) * Immediate Sigul support * 2 week Atomic improvements * Release Tooling Team 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 * Content signing can be automated through Sigul or another tool
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 * Signed repos in koji * Atomic redesigned workflow & toolchain * 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 * 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 * Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc * Development release gating with sanity testing / stability * Fedora Rings / Alephs * Layered images _not_ from RPMs — source-to-image or other * Releng CI (on Jenkins)