Revision as of 20:57, 9 November 2021

Change Proposal Name

ELN-Extras

Summary

ELN-extras will be a new build target and compose similar in behavior to ELN, but closer to EPEL in function. It will be a place to prepare and maintain packages that may be desired for EPEL N+1 while RHEL N+1 is still being incubated in ELN.

Owner

Owner: ELN SIG <devel@lists.fedoraproject.org>
Primary Contact: Stephen Gallagher <sgallagh@fedoraproject.org>

Current status

Targeted release: Fedora Linux 36
Last updated: 2021-11-09
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

This will essentially be an extension of Fedora ELN, with the primary difference being that the content in ELN-Extras will be defined by the Fedora/EPEL community, while ELN's content is largely decided upon by Red Hat management. This will offer users the opportunity to make sure their applications will work on upcoming releases of RHEL as well as providing a bootstrapping mechanism for EPEL. It will be far easier and quicker to get a compose of EPEL N+1 out the door if the initial packages have already been built for ELN-Extras.

Feedback

Benefit to Fedora

This Change will enable application developers to keep up with impending changes in RHEL even before CentOS Stream becomes available for that release. Additionally, it provides a bootstrapping mechanism for EPEL, which will mean a much shorter gap between the launch of a new RHEL major release and the availability of the EPEL repositories.

Scope

Proposal owners:

High-level tasks

1. Create the tags and targets in Koji (see the release engineering ticket below). 2. Add support to Content Resolver for addon repositories [DONE] 3. Update the DistroBuildSync configuration to support building for ELN-Extras. 4. Configure ODCS to produce an ELN-Extras variant compose.

Other developers:

Aside from the release engineering tasks, anyone who wants to have a package appear in ELN-Extras will need to add it to the content set. This is not mandatory for any packager and we can ship the ELN-Extras repository empty if we so choose.

Release engineering: #10378

Policies and guidelines: N/A (not needed for this Change)

Documentation on how to add packages to the ELN-Extras content set and how to consume its compose will be written as part of this Change.

Trademark approval: N/A (not needed for this Change)

Alignment with Objectives:

Not specifically aligned with the currently-active Objectives. Loosely related to the previous Minimization Objective.

Upgrade/compatibility impact

N/A, this will be an entirely new compose and thus has nothing from which to upgrade.

How To Test

No specific testing is required for this Change, though any general OS and software management testing would be most welcome.

User Experience

Fedora will make available a new add-on repository for ELN, maintained by the Fedora Community.

Dependencies

This should be self-contained from a dependency perspective. The groundwork was already laid by ELN.

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

We will not ship/advertise the existence of the ELN-Extras repository and resubmit for F37.

Documentation

Documentation will be written as part of this Change.

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 = Change Proposal Name =
-<!-- The name of your change proposal -->
+ELN-Extras
 == Summary ==
-<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
+ELN-extras will be a new build target and compose similar in behavior to ELN, but closer to EPEL in function. It will be a place to prepare and maintain packages that may be desired for EPEL N+1 while RHEL N+1 is still being incubated in ELN.
 == Owner ==
@@ Line 16: / Line 10: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Owner: ELN SIG <devel@lists.fedoraproject.org>
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
+* Primary Contact: [[User:Sgallagh| Stephen Gallagher]] <sgallagh@fedoraproject.org>
-* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
@@ Line 31: / Line 24: @@
 <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
-<!-- Select proper category, default is Self Contained Change -->
+[[Category:SystemWideChange]]
-[[Category:SelfContainedChange]]
-<!-- [[Category:SystemWideChange]] -->
-* Targeted release: [[Releases/<number> | Fedora Linux <number> ]]
+* Targeted release: [[Releases/36 | Fedora Linux 36 ]]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 48: / Line 39: @@
 == 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. -->
+This will essentially be an extension of Fedora ELN, with the primary difference being that the content in ELN-Extras will be defined by the Fedora/EPEL community, while ELN's content is largely decided upon by Red Hat management. This will offer users the opportunity to make sure their applications will work on upcoming releases of RHEL as well as providing a bootstrapping mechanism for EPEL. It will be far easier and quicker to get a compose of EPEL N+1 out the door if the initial packages have already been built for ELN-Extras.
 == Feedback ==
@@ Line 81: / Line 72: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+This Change will enable application developers to keep up with impending changes in RHEL even before CentOS Stream becomes available for that release. Additionally, it provides a bootstrapping mechanism for EPEL, which will mean a much shorter gap between the launch of a new RHEL major release and the availability of the EPEL repositories.
 == Scope ==
 * Proposal owners:
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+High-level tasks
+. Create the tags and targets in Koji (see the release engineering ticket below).
+. Add support to Content Resolver for addon repositories [DONE]
+. Update the DistroBuildSync configuration to support building for ELN-Extras.
+. Configure ODCS to produce an ELN-Extras variant compose.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+Aside from the release engineering tasks, anyone who wants to have a package appear in ELN-Extras will need to add it to the content set. This is not mandatory for any packager and we can ship the ELN-Extras repository empty if we so choose.
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: [https://pagure.io/releng/issues #10378] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 95: / Line 96: @@
 * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
+Documentation on how to add packages to the ELN-Extras content set and how to consume its compose will be written as part of this Change.
 * Trademark approval: N/A (not needed for this Change)
@@ Line 101: / Line 104: @@
 * Alignment with Objectives:
 <!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
+Not specifically aligned with the currently-active Objectives. Loosely related to the previous Minimization Objective.
 == Upgrade/compatibility impact ==
@@ Line 106: / Line 111: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A, this will be an entirely new compose and thus has nothing from which to upgrade.
@@ Line 124: / Line 130: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+No specific testing is required for this Change, though any general OS and software management testing would be most welcome.
 == User Experience ==
@@ Line 137: / Line 143: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Fedora will make available a new add-on repository for ELN, maintained by the Fedora Community.
 == Dependencies ==
@@ Line 143: / Line 151: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+This should be self-contained from a dependency perspective. The groundwork was already laid by ELN.
 == Contingency Plan ==
@@ Line 153: / Line 162: @@
 * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+We will not ship/advertise the existence of the ELN-Extras repository and resubmit for F37.
 == Documentation ==
@@ Line 158: / Line 168: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+Documentation will be written as part of this Change.
 == Release Notes ==

Search

Changes/ELN-Extras: Difference between revisions