Critical path package

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Where can I find the critical path?)
(Reorganize page)
Line 1: Line 1:
 +
= Summary =
 +
 +
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'' is defined as the set of packages required to perform the most fundamental actions on a Fedora system.  The list of actions is available at [[Critical_Path_Packages_Proposal#What_is_the_critical_path_of_actions.3F]].
+
The critical path was proposed and defined as part of a [[FAD]].  For background information, see [[Critical_Path_Packages_Proposal]].
 +
 
 +
= Scope =
 +
 
 +
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 {{filename|comps.xml}} file to include packages required for the critical use cases listed above.  Since package dependencies change regularly, the {{filename|comps.xml}} groups are then used to dynamically generate the list of packages.
 +
 
 +
The critical path package groups in {{filename|comps.xml}} are listed below:
 +
<pre>@core
 +
@critical-path-base
 +
@critical-path-gnome
 +
@critical-path-apps
 +
@critical-path-kde
 +
@critical-path-lxde
 +
@critical-path-xfce</pre>
 +
 
 +
More information on {{filename|comps.xml}} is available at [[How_to_use_and_edit_comps.xml_for_package_groups]].
 +
 
 +
= Maintainer Responsibilities =
 +
 
 +
{{admon/important|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 ''proventester'' group is responsible for ensuring minimal disruption to the critical actions listed above.  Information on testing critical path updates is available at [[User:Adamwill/Draft_proventesters_instructions]].
  
 
= Where can I find the ''critical path''? =
 
= Where can I find the ''critical path''? =
  
The list of critical path packages is a dynamically generated list of packages based on package dependencies.  The list is generated daily during the mash process for both [[Releases/Rawhide|Rawhide]] and [[Releases/Branched/Branched]].  For more information on how the list is generated, see [[Critical_Path_Packages_Proposal#When_and_how_to_determine_packages_within_the_path]].
+
The critical path package list is generated daily during the mash process 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:

Revision as of 20:00, 14 June 2010

Contents

Summary

The critical path defines a set of packages that require special care when updating in rawhide, branched and exiting Fedora releases.

Background

The critical path was proposed and defined as part of a FAD. For background information, see Critical_Path_Packages_Proposal.

Scope

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

More information on comps.xml is available at 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 proventester group is responsible for ensuring minimal disruption to the critical actions listed above. Information on testing critical path updates is available at User:Adamwill/Draft_proventesters_instructions.

Where can I find the critical path?

The critical path package list is generated daily during the mash process for both rawhide and branched.

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