From Fedora Project Wiki
Monthly Stakeholder Meetings
- Atomic stakeholder meetings
- Matthew Miller notes (representing RHEL, Council, etc)
- Fedora QE
- Workgroups: Workstation, Server, Cloud, Base, Env & Stacks - contacts TBD
Priorities
General guidelines
- Significant features should be targeted to Spring releases due to heavy travel during summer
F25 Planned Rel-Eng Deliverable Changes
| Change | Approval Status | Status | Notes |
|---|---|---|---|
| New: Cockpit container | - | - | - |
| New: WS OSTree | - | - | Blocked by mirror / rsync issue |
| New: Atomic for Power | - | - | Blocked by storage / rsync issue |
| Move to secondary: i686 | - | - | Need to get signoff from FESCO to move i686 to secondary instead of dropping Server media immediately; if approved, blocked on Pungi/Koji changes for non-blocking |
| Under Review: Windows & OSX Tools | - | - | - |
F25 Committed Tools Changes
| Deliverable | Change? | Infra Ticket? | Approval Status | Dev Status | Notes |
|---|---|---|---|---|---|
| Layered image builds | Y | N | Accepted | In Progress | Carried over from F24 |
| Taskotron: Support for container testing | Y | N | - | In Progress | - |
| Ansible: Docker 2 week build/test/release workflow automated via Ansible | Y | Y | Accepted | In progress | - |
| Content signing can be automated through Sigul or another tool | Y | ? | Submitted | In progress | |
| OSBS: Fedora Docker Registry | Y | Y | Accepted | In progress | Short term solution relying on second distribution instance expected for F25 |
| Koji: Koji hub consolidation groundwork | N | Y | n/a | In Progress | - |
| OSBS has redundancy and support for multi-master / multi-node | N | Y | n/a | In Progress | - |
| New Releng Deliverable: Windows & OSX tools in Fedora | Y | Y | Change Incomplete | In progress | At risk, needs status update |
F25 Nice to Have Tools Changes
| Deliverable | Approval Status | Dev Status | Notes |
|---|---|---|---|
| ARM Disk Images, ar64 and PXE2Live are created using LMC | n/a | - | - |
| DVD ISO support in Koji | Submitted | - | - |
| Ansible: Atomic 2 week build/test/release workflow automated | n/a | - | - |
| Atomic ostree repo management | - | - | - |
Backlog
Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team!
- Distgit: Check when people add Exclude/ExclusiveArch to packages, notify the arch teams - [Dropped from F25]
- LMC: Use LMC to create base images - [Dropped from F25]
- Rel-eng: Segment nightly composes more logically - [Dropped from F25]
- Modularity (potentially Pungi 5?) - [Dropped from F25]
- flatpak prototype - [Dropped from F25]
- OSBS on Power [F26 Candidate]
- Public hardware for AutoCloud (or full move to Taskotron)
- Assess building base images in OSBS
- Documentation of rel-eng process so that internal release engineers can contribute
- Development & Deployment Process Improvement / Standardization
- Move to createrepo_c (required before python3)
- Rocket base images
- Container test status results reported from Taskotron via fedmsg / email / UI
- Test automation for Atomic in Taskotron (?)
- Integration with UAT Framework
- Integration with Autocloud OR porting functionality & tests to Taskotron
- Integration with Tunir OR porting functionality & tests to Taskotron
- Integration with OpenQA
- Move ostree creation out of Bodhi
- Move from yum to dnf (required before python3)
- Docker images can be built in Oz / ImageFactory OR in OSBS to align with internal teams for all supported arches (F26 candidate)
- Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
- Requires roadmap for testability so that we can verify our migration
- add index.asc files for cloud images for virt-builder - https://fedorahosted.org/rel-eng/ticket/5805
- RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc)
- Koji 2.0
- ET / Bodhi alignment
- 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)
Completed
F25
F24