From Fedora Project Wiki

Monthly Stakeholder Meetings

Priorities

F24 Commitments

Deliverable Approval Status Dev Status Notes
Layered image builds Accepted In Progress Includes work for OpenShift in Fedora below
OpenShift in Fedora Accepted Done
PDC deployed & populated with product / release data Accepted Done
Pungi 4 upgrade and Pungi roadmap Accepted Done
Move to livemedia-creator for live cds Accepted Done
Signed repos in koji Accepted In Progress

F25 Planned Rel-Eng Deliverable Changes

Change Approval Status Status Notes
New: Cockpit - - -
New: WS OSTree - - -
New: Atomic for Power - - -
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 - - -
Under Review: Modules - - -

F25 Tier 1 Planning

Deliverable Change? Infra Ticket? Approval Status Dev Status Notes
Taskotron: Support for container testing Y N - In Progress -
Content signing can be automated through Sigul or another tool Y ? Planning Not Started
Jenkins: Docker 2 week build/test/release workflow automated via Jenkins Y Y - - -
Pungi & Koji: Mark an arch / artifact non-blocking N N - - https://pagure.io/pungi/issue/128
Pungi: Split output into different namespaces N N - - -
Pungi: Better checking of config file N N - - https://pagure.io/pungi/issue/91
OSBS: Integration with Pulp Y Y - - -
ARM Disk Images, ar64 and PXE2Live are created using LMC Y N - - -
New Releng Deliverable: Atomic for Power ? ? - - Are there tools changes required here?
New Releng Deliverable: Workstation OSTree N N - - Blocked by ostree storage / rsync issues
Need More Info
Modularity (potentially Pungi 5?) - - - - -
xdg app prototype - - - - -
New Releng Deliverable: Windows & OSX tools in Fedora - - Blocked on hardware availability - Jiri Eischman - -

F25 Tier 2 / non-blocking Planning

Deliverable Approval Status Dev Status Notes
DVD ISO support in Koji - - -
Jenkins: Atomic 2 week build/test/release workflow automated - - -
Bodhi: Support for non-rpm content - - -
Koji: Deploy moonshot chassis (July) - - -
Koji: Roadmap & proposal for consolidation of Koji hubs - - -
Distgit: Check when people add Exclude/ExclusiveArch to packages, notify the arch teams - - need to see if anyone is interested in picking this up
LMC: Use LMC to create base images - - -
Rel-eng: Segment nightly composes more logically (like we've done for Atomic, but for other logical areas so that we have more flexibility) - - -
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!

  • OSBS on Power [F26 Candidate]
  • Public hardware for AutoCloud (or full move to Taskotron)
  • Documentation of rel-eng process so that internal release engineers can contribute
  • Development & Deployment Process Improvement / Standardization
  • Move to createrepo_c (required before python3)
  • 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

Retrieved from "https://fedoraproject.org/w/index.php?title=ReleaseEngineering/PriorityPipeline&oldid=447617"