From Fedora Project Wiki
(Send off to Wrangler)
(Fix formatting and contingency plan)
Line 1: Line 1:
= Change Proposal Name =
= ELN-Extras =
ELN-Extras


== Summary ==
== Summary ==
Line 10: Line 9:
This should link to your home wiki page so we know who you are.  
This should link to your home wiki page so we know who you are.  
-->
-->
* Owner: ELN SIG <devel@lists.fedoraproject.org>
* Owner: [[User:Sgallagh| Stephen Gallagher]] <sgallagh@fedoraproject.org>
* Primary Contact: [[User:Sgallagh| Stephen Gallagher]] <sgallagh@fedoraproject.org>
* SIG: ELN SIG <devel@lists.fedoraproject.org>
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 154: Line 153:


== Contingency Plan ==
== Contingency Plan ==
* Contingency mechanism: We will not ship/advertise the existence of the ELN-Extras repository.
* Contingency deadline: Final freeze
* Blocks release? No


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* 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 ==
== Documentation ==

Revision as of 14:20, 11 November 2021

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: Stephen Gallagher <sgallagh@fedoraproject.org>
  • SIG: ELN SIG <devel@lists.fedoraproject.org>


Current status

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

  • 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: We will not ship/advertise the existence of the ELN-Extras repository.
  • Contingency deadline: Final freeze
  • Blocks release? No


Documentation

Documentation will be written as part of this Change.

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/ELN-Extras&oldid=630315"