From Fedora Project Wiki

m (Add link to FAS group.)
(update for storage of critpath data in PDC, not pkgdb)
 
(23 intermediate revisions by 11 users not shown)
Line 1: Line 1:
= Summary =
+
{{for|information on the proposal|Critical Path Packages Proposal}}
  
The ''critical path'' defines a set of packages that require special care when updating in [[Releases/Rawhide|rawhide]], [[Releases/Branched|branched]] and exiting Fedora releases.  
+
A '''critical path package''' is a specially managed package in [[Fedora]] that provides some essential or core functionality. Updates for critical path packages must undergo additional verification before they can be distributed to the community at large.
  
 
= Background =
 
= Background =
  
The critical path was proposed and defined as part of a [[FAD]].  For background information, see [[Critical_Path_Packages_Proposal]].
+
Previously, documented policy treated every package the same.  While good for uniformity, in reality certain packages require extra attention and care when updating and testing.  These packages have potential to break the critical path of use of our Fedora distribution.  As part of a [[Fedora Activity Day]], several contributors proposed a critical set of actions that must not be brokenThe packages required to sustain these actions make up the ''critical path''.
  
= Scope =
+
= Actions =
  
 
Packages within the ''critical path'' are required to perform the most fundamental actions on a system.  Those actions include:
 
Packages within the ''critical path'' are required to perform the most fundamental actions on a system.  Those actions include:
Line 34: Line 34:
 
@critical-path-xfce</pre>
 
@critical-path-xfce</pre>
  
More information on {{filename|comps.xml}} is available at [[How_to_use_and_edit_comps.xml_for_package_groups]].
+
You can list the packages in these groups with the following command, replacing 'critical-path-base' with the name of the group you're interested in. For Fedora 22 and later versions use [[dnf|DNF]]:
  
= Maintainer Responsibilities =
+
<pre>dnf group info critical-path-base</pre>
  
{{admon/important|FIXME|This section needs to be updated.}}
+
Or with Yum for older releases:
 +
<pre>yum groupinfo critical-path-base</pre>
  
If a package is added to the critical path list as a result of normal package dependency the package maintainer will be notified through direct email and the extra processes they have to go through. (IS THIS TRUE)
+
For more information on {{filename|comps.xml}} see [[how to use and edit comps.xml for package groups]].
  
If they do not wish to maintain the packages with these extra processes then they have to orphan the package. A new maintainer will need to be found.
+
= Where can I find the ''critical path''? =
 +
 
 +
The critical path package list for all releases is stored in [https://pdc.fedoraproject.org/ PDC].
  
= Tester Responsibilities =
+
The most recent lists of critical path packages are available at:
  
The [https://admin.fedoraproject.org/accounts/group/view/proventesters ''proventesters'' FAS group] is responsible for ensuring minimal disruption to the critical actions listed above. If you would like to join ''proventesters'', check out [[QA/JoinProvenTesters]].  General test instructions for ''proventesters'' is available at [[User:Adamwill/Draft_proventesters_instructions]].
+
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=master&active=true&critical_path=true&type=rpm Rawhide]
 +
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=f{{FedoraVersionNumber|next}}&active=true&critical_path=true&type=rpm {{FedoraVersion|long|next}} (if branched)]
 +
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=f{{FedoraVersionNumber}}&active=true&critical_path=true&type=rpm {{FedoraVersion|long}}]
  
= Where can I find the ''critical path''? =
+
Read API documentation [https://pdc.fedoraproject.org/rest_api/v1/component-branches/ here].
  
The critical path package list is generated daily during the mash process for both [[Releases/Rawhide|rawhide]] and [[Releases/Branched|branched]].  
+
<!--
 +
SAMPLE USAGE of the Parser Function #time -- See http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23time
  
The most recent list of critical path packages are available at:
+
{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}
 
* Branched (aka {{FedoraVersion|long|next}}) - [http://kojipkgs.fedoraproject.org/mash/branched-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt http://kojipkgs.fedoraproject.org/mash/branched-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt]
 
* Branched (aka {{FedoraVersion|long|next}}) - [http://kojipkgs.fedoraproject.org/mash/branched-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt http://kojipkgs.fedoraproject.org/mash/branched-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt]
 
* Rawhide - [http://kojipkgs.fedoraproject.org/mash/rawhide-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt http://kojipkgs.fedoraproject.org/mash/rawhide-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt]
 
* Rawhide - [http://kojipkgs.fedoraproject.org/mash/rawhide-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt http://kojipkgs.fedoraproject.org/mash/rawhide-{{CURRENTYEAR}}{{CURRENTMONTH}}{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}/logs/critpath.txt]
 
<!--
 
{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}
 
 
-->
 
-->

Latest revision as of 19:50, 7 September 2017

For information on the proposal, see Critical Path Packages Proposal.

A critical path package is a specially managed package in Fedora that provides some essential or core functionality. Updates for critical path packages must undergo additional verification before they can be distributed to the community at large.

Background

Previously, documented policy treated every package the same. While good for uniformity, in reality certain packages require extra attention and care when updating and testing. These packages have potential to break the critical path of use of our Fedora distribution. As part of a Fedora Activity Day, several contributors proposed a critical set of actions that must not be broken. The packages required to sustain these actions make up the critical path.

Actions

Packages within the critical path are required to perform the most fundamental actions on a system. Those actions include:

  • graphical network install
  • post-install booting
  • decrypt encrypted filesystems
  • graphics
  • login
  • networking
  • get updates
  • minimal buildroot
  • compose new trees
  • compose live

Implementation

A set of groups are defined in the comps.xml file to include packages required for the critical use cases listed above. Since package dependencies change regularly, the comps.xml groups are then used to dynamically generate the list of packages.

The critical path package groups in comps.xml are listed below:

@core
@critical-path-base
@critical-path-gnome
@critical-path-apps
@critical-path-kde
@critical-path-lxde
@critical-path-xfce

You can list the packages in these groups with the following command, replacing 'critical-path-base' with the name of the group you're interested in. For Fedora 22 and later versions use DNF:

dnf group info critical-path-base

Or with Yum for older releases:

yum groupinfo critical-path-base

For more information on comps.xml see how to use and edit comps.xml for package groups.

Where can I find the critical path?

The critical path package list for all releases is stored in PDC.

The most recent lists of critical path packages are available at:

Read API documentation here.