Critical path package

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Added a reference to the proposal. Removed now-redundant reference in the article)
(Link to pkgdb critpath)
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
{{for|information on the proposal|Critical Path Packages Proposal}}
 
{{for|information on the proposal|Critical Path Packages Proposal}}
  
= Summary =
+
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.
 
+
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.  
+
  
 
= Background =
 
= Background =
  
The critical path was proposed and defined as part of a [[FAD]].
+
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''.
  
= 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 36: 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:
 +
 
 +
<pre>yum groupinfo critical-path-base</pre>
 +
 
 +
For more information on {{filename|comps.xml}} see [[how to use and edit comps.xml for package groups]].
  
 
= Maintainer Responsibilities =
 
= Maintainer Responsibilities =
Line 48: Line 50:
 
= Tester Responsibilities =
 
= Tester Responsibilities =
  
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]].
+
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 [[Proven_tester]], where you will also find instructions on the testing process.
  
 
= Where can I find the ''critical path''? =
 
= Where can I find the ''critical path''? =
  
The critical path package list is generated daily during the mash process for both [[Releases/Rawhide|rawhide]] and [[Releases/Branched|branched]].  
+
The critical path package list is stored in the packagedb for both [[Releases/Rawhide|rawhide]] and [[Releases/Branched|branched]].  
  
 
The most recent list of critical path packages are available at:
 
The most recent list of critical path packages are available at:
* [http://kojipkgs.fedoraproject.org/mash/branched-20100518/logs/critpath.txt Branched (aka {{FedoraVersion|long|next}})]
 
<!-- This is currently a dead link, so I hard-coded the most recent valid critpath.txt. Please uncomment when the latest link works. Dafrito 17:56, 19 June 2010 (UTC)
 
* 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]
 
  
 +
* [https://admin.fedoraproject.org/pkgdb/lists/critpath?tg_format=plain&collctn_list=f{{FedoraVersion||next}} Branched] (aka {{FedoraVersion|long|next}})
 +
* [https://admin.fedoraproject.org/pkgdb/lists/critpath?tg_format=plain&collctn_list=devel Rawhide] (aka {{FedoraVersion|long|next2}})
 
<!--
 
<!--
 +
SAMPLE USAGE of the Parser Function #time -- See http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23time
 +
 
{{#time: d | {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} - 1 day}}
 
{{#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]
 +
* 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]
 
-->
 
-->

Revision as of 16:57, 19 October 2012

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.

Contents

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:

yum groupinfo critical-path-base

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

Maintainer Responsibilities

Important.png
FIXME
This section needs to be updated.

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)

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.

Tester Responsibilities

The proventesters FAS group is responsible for ensuring minimal disruption to the critical actions listed above. If you would like to join proventesters, check out Proven_tester, where you will also find instructions on the testing process.

Where can I find the critical path?

The critical path package list is stored in the packagedb for both rawhide and branched.

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