From Fedora Project Wiki

There's a 404 on the critpath.txt for branched. The latest critpath.txt that I could find was created on May 18, 2010. I pointed the 404'd link to that file, but this is most assuredly a hack. Dafrito 17:49, 19 June 2010 (UTC)

Critical Path Comps Groups

IMHO it is a very annoying idea to use the core group as a critical path group, because it makes selecting all critical path groups more complicated and unintuitive. E.g. on fedora-devel I assumed that all critical path updates can be installed using yum groupinstall critical-path\* and nobody objected. But with using the core group, it has to be yum groupinstall critical-path\* core. Therefore please use a critical-path-core group that contain all the core packages. --Till 08:31, 4 July 2010 (UTC)

jlaska 13:10, 8 July 2010 (UTC) - Maintaining multiple groups with the same content seems like a bad idea. First, I'm not familiar with your use case of installing all critical path packages by using the comps group name. I don't know if that was ever considered. My understanding is core, as the name implies, is core to everything. If you wanted to propose a comps.xml patch that adds a <groupreq>core</groupreq> to the existing critical-path-base group, that might help frame discussion on I don't know whether this is something we want to do, but that would be a good discussion to then have on list.
The use case is to be able to install only critical path updates or to query whether or not there are critical path updates. It just makes every use of the comps groups regarding critical path updates easier. I will write a mail to devel@l.fpo. --Till 14:23, 8 July 2010 (UTC)

Also it does not make sense to have two pages that list the critical path comps groups, this one and Critical_Path_Packages_Proposal. Redundancy of such information is bad, because it is not properly synced and therefore people may only get the out of date information. -- Till 08:44, 4 July 2010 (UTC)

jlaska 14:50, 7 July 2010 (UTC) - There is only one page that details the critical path status and implementation, and that is Critical_path_package. The Critical_Path_Packages_Proposal page is not intended for ongoing maintenance and was used to outline the problem space and manage the first-round implementation. If there is information you are missing on Critical_path_package, we can address it (as you have initiated above).
How about moving the Proposal page to the Archive namespace or apply some other wiki-procedure to indicate that the page is deprecated?
jlaska 13:10, 8 July 2010 (UTC) - I don't think we need to do anything more. The page is called Proposal and has clear text at the top indicating For information on the implementation and the current state of critical path, see Critical path packages.
And what about the comps groups? Will this be addressed? --Till 11:59, 8 July 2010 (UTC)
jlaska 13:10, 8 July 2010 (UTC) - No one has responded to that comment yet. While I'm not the authority on this, I'll respond there now.