From Fedora Project Wiki
Monthly References
Note: meeting notes aren't regularly updated.
- Status Report
- Atomic stakeholder meetings
- Matthew Miller notes (representing RHEL, Council, etc)
- Fedora QE
Priorities
General guidelines
- Significant features should be targeted to Spring releases due to heavy travel during summer
F26 Proposed Tools Changes
F26 Nice to Have Changes
- Metadata for split composes
- OSBS multi arch support (for scratch initially)
- ARM Disk Images, aarch64 and PXE2Live are created using LMC
Backlog
Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team!
- DVD ISO support in Koji - F27
- Move to createrepo_c (required before python3) - F27
- Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc - F27
- Bodhi: Support for non-rpm content
- Move base image builds to OSBS - F27 (dependent on Multi-arch support)
- Automate security updates (in addition to 2 week updates) for containers using automated workflow - Review for F27
- Rel-eng: Segment nightly composes more logically
- flatpak prototype
- Rocket base images
- Documentation of rel-eng process so that internal release engineers can contribute
- Development & Deployment Process Improvement / Standardization
- 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
- RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc)
- 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
- 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
- Layered images _not_ from RPMs — source-to-image or other
- Releng CI (on Jenkins)
Completed
F26
F25
- Layered image builds
- Content signing can be automated
- Koji: Koji hub consolidation groundwork
- Move to secondary: i686
- New Releng Deliverable: Windows & OSX tools in Fedora
- Container Signing in Sigul
F24