Information
There are two websites that needs to be maintained for GLIBC.
The wiki and bugzilla are not considered part of the website.
The first website is hosted on sourceware.org at http://sourceware.org/glibc/ and the second on savannah.gnu.org at http://www.gnu.org/software/libc/libc.html.
As of 2023-10-13 the sourceware.org website and the FSF website are unique and we no longer redirect from one to the other. The goal is for the FSF website to be a static website pointing to the project website.
When to update for version X.Y.Z?
When the release branch for X.Y.Z has been created, and the tarballs uploaded, then the websites should also be updated to reflect the availability of the release.
Check out sources for the sourceware.org website
- Checkout via git the glibc-htdocs web sources (must have a sourceware.org account.
git clone ssh://sourceware.org/git/glibc-htdocs.git
- Modify website.
Modify libc.html to adjust wording for a newer release e.g. 2.29 vs. 2.30.
Modify sources.html to use the newer version in the working e.g. 2.29 vs. 2.30.
Modify started.html to use the newer version in the working e.g. 2.29 vs. 2.30.
- Automatically update the manual using your GNU Savannah account.
Read README.txt for instructions to build, upload, and update the online manuals.
Check out sources for the savannah.gnu.org website
Checkout via CVS the libc web sources (must have savannah account and be a member of libc team, see: http://savannah.gnu.org/projects/libc/):
export CVS_RSH=ssh cvs -z3 -d:ext:<membername>@cvs.savannah.gnu.org:/web/libc co libc
- Modify static website as required.