ReleaseEngineering/PriorityPipeline

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

Deliverable	Change?	Approval Status	Dev Status	Notes
Updated layered image repo structure (Container naming, koji tags, etc)	N	n/a	Done
Kerberos support in koji, fedpkg, OSBS	N	n/a	Done
Public hardware for AutoCloud	N	N	Done
Distgit: Check when people add Exclude/ExclusiveArch to packages, notify the arch teams	N	n/a	Done
Bodhi: Design for supporting for containers	N	n/a	Done
Taskotron: Support for container testing	Y	N	Done
Fedora dockerfiles support for Beta	Y	n/a	Done
F26 Hub consolidation: aarch64 & Power64 koji merged; prep to import s390x in F27	Y	Y	Done
Atomic ostree repo management	N	n/a	Done
Pungi changes to allow non-blocking artifacts to fail without failing the compose	N	n/a	Done
OSBS has redundancy and support for multi-master / multi-node	N	n/a	In Progress	Redundancy in place; pending scale testing
Ansible: Docker 2 week build/test/release workflow automated via Ansible	Y	Accepted	In progress	-
OSBS: Fedora Docker Registry	Y	?	In progress
Move releng, fedora-packager, mash & pungi from yum to dnf (required before python3)	N	n/a	Moved to F27
Support for non x86_64 ostrees as part of standard build & release process	N	n/a	Moved to F27
Move from Appliance Creator to Image Factory	N	n/a	Stalled
Module Build Service	Y	?	Slaying	Factory 2.0
Modular Compose	Y	?	Not started	Factory 2.0

Backlog

Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team!

F27 Candidates

• Support for accelerating the Fedora Atomic Host - F27
  • Consolidate ostree generation process for pre-GA and post-GA OSTree generation / support for multi arch ostrees / better versioning of ostrees
  • Investigative task: Bodhi is not a bottleneck for frequent releases
• Modularity support / integration - F27
  • Bodhi: Support for non-rpm content
• Move to createrepo_c (required before python3) - F27
• Port to python 3 - Koji, pungi, Mash, releng scripts, fedpkg, rpkg, etc - F27
• F27 no longer ships an alpha - F27
• Koji hub consolidation for s390 - F27
• flatpak prototype
• Deploy koji signed repo support - scope work for Pungi & Bodhi to use it - F27
• ostree versions that more closely match compose IDs

Other

• Metadata for split composes - F27
• Rich dependency support in DNF for Rust - F27
• ARM Disk Images, aarch64 and PXE2Live are created using LMC - F27
• add index.asc files for cloud images for virt-builder - F27
• Koji support for disk images - F27
• ostree mirroring - F27
• Imagebuilder plugin POC for layered image builds - F27
• Documented content retention & removal policies / old content moved to archival storage - F27
• DVD ISO support in Koji - F27
• OSBS multi arch support (for scratch initially) - F27
• 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
• Ansible: Atomic 2 week build/test/release workflow automated - F27
• Rel-eng: Segment nightly composes more logically
• 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)
• Behavioral testing in Bodhi
• Method for distributing fixes quickly

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

• Pungi 4 upgrade and Pungi roadmap
• Move to livemedia-creator for live cds
• PDC deployed & populated with product / release data
• OpenShift in Fedora
• Documented policy and process for contributing to upstream tools
• 2 week Atomic content
• Design Only: Re-design atomic release process