• Changes
      • Changes policy
        • Change Process Milestones
      • Change submission guidance
        • Section-by-section guidance
      • Changes process rationale and history
    • Elections
      • Elections Guide
      • Upcoming elections
      • Elections process
      • Historical elections
    • Prioritized Bugs
    • Resources
    • PgM Guide
      • Changes
      • Release process
      • Prioritized bugs
      • Elections
      • Schedule management
      • PgM communications
      • Council meetings and processes
      • Inactive provenpackagers
      • Bugzilla admin
      • Getting started
      • SOPs
        • Release steps
          • New releases
          • Branching
          • Go/No-Go Meeting
          • Release delay
          • Release go
          • Release no-go
          • Release day
          • EOL warning
          • EOL day
        • Changes
          • Announcing Changes
          • Submitting Changes
          • Processing Changes
          • Evaluating Changes contingency plans
          • Deferring Changes
          • Dropping Changes
        • Prioritized bugs
        • Blocker status email
        • Spins keepalive
        • Inactive maintainers
        • Inactive provenpackagers
        • Friday’s Fedora Facts
        • Elections
          • Election opening
          • Nomination closing
          • Election interview processing
          • Election app setup
          • Election results

    • Управление на Програмата Fedora
    • ARM Single Board Computers
    • Ask Fedora SOPs
    • Community Architecture (CommArch)
    • Community Linux Engineering
    • Defensive Coding Guide
    • Emerging Fedora Desktops
    • Engineering Teams
    • EPEL
    • Fedora Accessibility (a11y) WG
    • Fedora Accounts
    • Fedora Asahi Remix
    • Fedora Badges
    • Fedora CI
    • Fedora Community Ops
    • Fedora Container Docs
    • Fedora CoreOS
    • Fedora Council
    • Fedora Diversity, Equity, and Inclusion (DEI)
    • Fedora Docs Team
    • Fedora ELN
    • Fedora Gaming
    • Fedora i3 S.I.G.
    • Fedora Infrastructure & Release Engineering
    • Fedora Internet Of Things
    • Fedora IoT Working Group
    • Fedora Join SIG
    • Fedora Kinoite
    • Fedora Legal
    • Fedora Linux Releases
    • Fedora Localization Team
    • Fedora Magazine
    • Fedora Marketing Team
    • Fedora Mentored Projects
    • Fedora Mindshare Committee
    • Fedora Project
    • Fedora Quality Docs
    • Fedora Rawhide Gating
    • Fedora Robotics SIG
    • Fedora Server Documentation
    • Fedora Server Working Group
    • Fedora Silverblue
    • Fedora Spins & Labs
    • Fedora Sway Atomic
    • Fedora TeleIRC SIG
    • Fedora Tools
    • Fedora User Docs
      • rawhide
      • f41
      • f40
      • f39
      • f38
      • f37
      • f36
      • f35
      • f34
      • f33
      • f32
      • f31
      • f30
      • f29
      • f28
      • f27
      • f26
    • Fedora Websites & Apps
    • Fedora Workstation Documentation
    • Fedora Workstation Working Group
    • Fedora Документация
    • Fedora/CentOS bootc
    • FESCo
    • Flatpak
    • Java Packaging HOWTO
    • Localization help and stats
    • Mindshare Teams
    • Minimization
    • Modularity
    • NeuroFedora User Documentation
    • Package Maintainers
    • Packaging Guidelines
    • Quick Docs
    • Remix Docs
    • Reproducible Builds
      • PgM Guide
      • Changes
      en-US ar ast az be bg bn ca cs de el es es_419 fa fi fil fr fur ga he hi hr hu id it ja jp ka kab ko mr ms my nb_NO ne nl nn or pl pt pt_BR pt_PT ro ru si sk sq sv sw te tr tzm uk ur ur_PK uz zh_CN zh_Hans zh_Hant zh_TW

      Changes Process

      Fedora’s Change Process is important to coordinate the development of the next Fedora release. We need to know about disrupting changes coming to the next release to set the scope of release, but it also helps as marketing tool even for leaf changes. For more details on Change Process, see the Changes Policy.

      Responsibilities

      The Program Manager’s key responsibility is to maintain the Changes Process — announcements, submission, processing, tracking, deferring, dropping. Completed Changes are closed as part of the Release Day SOP. One of the main responsibilities is helping Change owners through the submission process. The Program Manager works on the Changes Policy with the Fedora Engineering Steering Committee (FESCo), Working Groups and other Fedora teams and bodies (documentation, marketing, etc.).

      Want to help? Learn how to contribute to Fedora Docs ›

    All Fedora Documentation content available under CC BY-SA 4.0 or, when specifically noted, under another accepted free and open content license.

    Fedora Logo
    • Privacy Statement
    • Legal
    • Code of Conduct
    • Sponsors

    Last build: 2024-12-16 23:00:13 UTC

    Sponsored by Red Hat Logo

    Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora.