From Fedora Project Wiki

Monthly References

Note: meeting notes aren't regularly updated.

Priorities

General guidelines

  • Significant features should be targeted to Spring releases due to heavy travel during summer

F25 Planned Rel-Eng Deliverable Changes

Change Status Notes
New: Cockpit container Early builds planned for week of Sept 12 (delayed to Sept 19; delayed again to ???) Pending OSBS update after Beta freeze
New: WS OSTree Pending beta builds to verify configs Discussion on mailing list; issues with packages that need to be fixed by WS team
New: Atomic for Power Not started -
Windows & OSX Tools Bugfix period after test day; pending signed builds Beta release

F25 Committed Tools Changes

Deliverable Change? Infra Ticket? Approval Status Dev Status Notes
Layered image builds Y N Accepted Done
Content signing can be automated Y ? n/a Done
Koji: Koji hub consolidation groundwork N Y n/a Done -
New Releng Deliverable: Windows & OSX tools in Fedora Y Y Change Incomplete Done
Container Signing in Sigul N N n/a Done
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 -
OSBS has redundancy and support for multi-master / multi-node N Y n/a In Progress -

F25 Nice to Have Tools Changes

Deliverable Approval Status Dev Status Notes
ARM Disk Images, aarch64 and PXE2Live are created using LMC n/a Not started Hope to look into arm & aarch64 in October
Atomic ostree repo management - In progress Pending input from DGilmore

Backlog

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

F26 Planned Tools Changes

Deliverable Change? Infra Ticket? Approval Status Dev Status Notes
Distgit: Check when people add Exclude/ExclusiveArch to packages, notify the arch teams (full implementation) ? N ? In progress
Updated layered image repo structure (Container naming, koji tags, etc) ? N ? Not started
Deploy koji signed repo support - scope work for Pungi & Bodhi to use it ? N ? In progress
Pungi changes to allow non-blocking artifacts to fail without failing the compose ? N ? Not started
OSBS: Fedora Docker Registry ? Y ? Not started
add index.asc files for cloud images for virt-builder ? N ? Not started
Kerberos support in koji, fedpkg, OSBS ? ? ? In progress
Fedora dockerfiles support for Beta ? N ? Not started
Ansible: Atomic 2 week build/test/release workflow automated ? N ? Not started
DVD ISO support in Koji ? N ? Not started
F26 Hub consolidation: aarch64 & Power64 koji merged; prep to import s390x in F27 ? Y ? Not started
Bodhi: Design for supporting for containers ? N ? Not started
Public hardware for AutoCloud ? Y ? In progress
Move from yum to dnf (required before python3) - Needs detail about specific changes ? N ? Not started

F26 Nice to Have Changes


==
  • 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

F24

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