critpath.txt lists critical path packages [1]. Currently it is referenced as
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<CURRENT DATE>>/logs/critpath.txt
}}}
or
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<YESTERDAY DATE>>/logs/critpath.txt
}}}
depending on which page. Similarly for branched releases.

This is not optimal. Very often the url just doesn't work. For example at the time of writing critpath.txt on F13 Alpha Release Criteria page [2] references rawhide-20100407/ directory, where critpath.txt is not available. Nor it is available in rawhide-20100406/ directory. Only in rawhide-20100405/ it is finally available.

The very page Critical Path Packages [1] references critpath.txt for Branched release, which is available ATM, but also references critpath.txt for Rawhide, which is again not available.

Let's imagine other use case - some automated tool must decide whether package in the critical path. It can't rely on path which are constantly changing and sometimes are not available.

critpath.txt is created dynamically, so we probably must have the contents created every day or so. But we should devise such mechanism that the location is stable and the file is always available (if new contents fails to create, the old contents is still available). That will also allow third-party tools to rely on it.

[1] https://fedoraproject.org/wiki/Critical_Path_Packages [[BR]]
[2] https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria