3GPP 21.900 v20.0.0 — the document's own text
5.1 General
Taught in 4. The life of a 3GPP document, from blank page to published version (How standards actually get made, in depth), 1. Why anybody writes a standard down (How standards actually get made, overview), 7. Reading either body's paper trail yourself (How standards actually get made, overview), 3. One idea, from proposal to published text (How standards actually get made, quick start).
The Support Team shall make all approved versions of all specifications available as soon as possible after their approval (or after approval of CRs thereto) on a file server. The server shall allow anonymous access by any interested party.
The Support Team should also endeavour to make earlier drafts available on the server, even prior to approval, i.e. versions 0.y.z, 1.y.z and 2.y.z.
Such "availability" does not constitute formal "publication". Under the terms of the 3GPP partnership agreement, the Organizational Partners which are Standards Development Organizations will publish TSG-approved specifications in the form of their own standards. The modalities of such publication processes are specific to those individual Organizations and are beyond the scope of the present document.
The directory structure shall differentiate amongst approved and draft specifications, amongst versions of specifications approved at specific TSG meetings, amongst versions of specifications pertaining to different Releases, and between specifications relating to 2nd generation (GSM) only and 3rd generation (UMTS) systems.
A clear and unambiguous directory structure shall be adopted, and a guide to that structure provided on the server. A "status list" shall also be provided, showing the latest version of each Release of each specification.