modularity

#175 Identify suitable modules
Opened by msuchy. Modified

Open
Close Issue

In a world where Fedora, CentOS, RHEL, Copr has each hundred or even thousands of modules, I as a developer of the layered application, need to identify which modules are suitable for the needs of my application and on top of which modules I can build my applications.
I need to easily compare different attributes that can affect my decision. Like life-cycle (aka EOL date), level of support.

Here is link for draft https://docs.google.com/document/d/1ZvO_MXSJVxqz19VK7QgHBakqh0uAmtntGvpISQafFm8/edit?usp=sharing

Fedora keeps EOL dates in PDC service (https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch_type=module&global_component=perl&branch=5.32). RHEL keeps EOL dates on a web page (https://access.redhat.com/support/policy/updates/rhel8-app-streams-life-cycle). Copr probably does not maintain EOLs.

In Fedora we will maybe get EOL dates into YUM repository and relengs will decommission PDC (https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL). Then the data will be available to DNF.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

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

© Red Hat, Inc. and others.