From Fedora Project Wiki
No edit summary |
|||
| Line 11: | Line 11: | ||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/201 2 week Atomic content] | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/201 2 week Atomic content] | ||
* Documented policy and process for contributing to upstream tools | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/198 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) | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/203 Design Only: Re-design atomic release process (to include compose based testing, something closer to continuous releases, alignment with internal process)] | ||
* Immediate Sigul support | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/202 Immediate Sigul support] | ||
* 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] | ||
== F24 Commitments == | == F24 Commitments == | ||
* PDC deployed & populated with product / release data | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/215 PDC deployed & populated with product / release data] | ||
* 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] | ||
* Layered image builds | * [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?statuses=145,146,151,182&tags=layeredimage Layered image builds] | ||
* Move to livemedia-creator for live cds | * Move to livemedia-creator for live cds | ||
* 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] | ||
| Line 29: | Line 28: | ||
== Backlog == | == Backlog == | ||
Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team! | |||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=documentation Documentation of rel-eng process so that internal release engineers can contribute] | |||
* [http://taiga.cloud.fedoraproject.org/project/acarter-fedora-docker-atomic-tooling/us/211 Signed repos in koji] | |||
* Atomic redesigned workflow & toolchain | |||
* Docker images can be built in Oz / ImageFactory for all supported arches | * Docker images can be built in Oz / ImageFactory for all supported arches | ||
* | * Second tier PDC use case implementation | ||
* Consolidate hubs for primary and | * 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) | * RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc) | ||
* Taskotron | * Taskotron | ||
| Line 42: | Line 46: | ||
* rel-eng tools are not easily testable or contributed to | * rel-eng tools are not easily testable or contributed to | ||
* changes can be tested in an integrated environment before releasing to production | * 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) | |||
Revision as of 18:53, 14 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
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
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)