From Fedora Project Wiki
Line 37: | Line 37: | ||
Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team! | Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team! | ||
* [http://taiga. | * [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=documentation Documentation of rel-eng process so that internal release engineers can contribute] | ||
* [http://taiga. | * [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=process&statuses=145,146,147,151,182 Development & Deployment Process Improvement / Standardization] | ||
* [http://taiga. | * [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=container_release Docker container automated 2 week releases - F25 Candidate] | ||
** Including Bodhi support for non-rpm content | ** Including Bodhi support for non-rpm content | ||
* Atomic redesigned workflow & toolchain - F25 Candidate | * Atomic redesigned workflow & toolchain - F25 Candidate |
Revision as of 15:47, 1 December 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
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 | Planning | In Progress | |
Move to livemedia-creator for live cds & disk images | Submitted | Not Started | |
Signed repos in koji | Submitted | In Progress | |
Content signing can be automated through Sigul or another tool | Planning | Not Started |
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
- Development & Deployment Process Improvement / Standardization
- Docker container automated 2 week releases - F25 Candidate
- Including Bodhi support for non-rpm content
- Atomic redesigned workflow & toolchain - F25 Candidate
- Move to createrepo_c - F25 Candidate
- DVD ISO support in Koji - F25 Candidate
- Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
- Requires roadmap for testability so that we can verify our migration
- Atomic ostree repo management
- 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
- 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)