From Fedora Project Wiki
< Changes
mNo edit summary |
mNo edit summary |
||
| Line 58: | Line 58: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
The Fedora Server Working | The Fedora Server Working group is looking to elevate the current Fedora Server VM Image to be a full distribution media that will be able hold a release due to any blockers similar to the ISO Images. | ||
== Feedback == | == Feedback == | ||
| Line 65: | Line 66: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | ||
Be sure to include the following areas if relevant: | Be sure to include the following areas if relevant: | ||
| Line 91: | Line 94: | ||
https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | ||
--> | --> | ||
This allows the Fedora Server working group to reinforce its commitment to the highest quality Fedora Server experience possible. | |||
== Scope == | == Scope == | ||
Revision as of 17:11, 21 August 2024
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Guidance
For details on how to fill out this form, see the documentation.
For details on how to fill out this form, see the documentation.
Report issues
To report an issue with this template, file an issue in the pgm_docs repo.
To report an issue with this template, file an issue in the pgm_docs repo.
Mark Fedora Server VM Images as Release-Blocking
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Mark Fedora Server VM Images as Release Blocking
https://pagure.io/releng/issue/12163
Owner
- Name: Jason Blackwell
- Email: blackwell@disroot.org
Current status
- Targeted release: Fedora Linux 41
- Last updated: 2024-08-21
- [Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
The Fedora Server Working group is looking to elevate the current Fedora Server VM Image to be a full distribution media that will be able hold a release due to any blockers similar to the ISO Images.
Feedback
Benefit to Fedora
This allows the Fedora Server working group to reinforce its commitment to the highest quality Fedora Server experience possible.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
Early Testing (Optional)
Do you require 'QA Blueprint' support? Y/N
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)