From Fedora Project Wiki

How We Prioritize

Monthly Stakeholder Meetings

* Atomic stakeholder meetings
* Matt Miller notes (representing RHEL, Council, etc)
* Fedora QE
* Workgroups: Workstation, Server, Cloud, Base, Env & Stacks  - contacts TBD
*

Priorities

Immediate Priorites

F24 Commitments

Backlog

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

  • Documentation of rel-eng process so that internal release engineers can contribute
  • Atomic redesigned workflow & toolchain
  • Docker images can be built in Oz / ImageFactory for all supported arches
  • Second tier PDC use case implementation
  • Bodhi support for non-rpm content
  • Consolidate hubs for primary and secondary arches
  • RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc)
  • Taskotron
  • Koji 2.0
  • ET / Bodhi alignment
  • RHEL.next support
  • 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
  • Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
  • Development release gating with sanity testing / stability
  • Fedora Rings / Alephs
  • Layered images _not_ from RPMs — source-to-image or other
  • Releng CI (on Jenkins)