|Deletions are marked like this.||Additions are marked like this.|
|Line 15:||Line 15:|
|=== Check out sources for the svannah.gnu.org website ===||=== Check out sources for the savannah.gnu.org website ===|
|Line 27:||Line 27:|
* Check it back in. Update is delayed by a script that makes things live.
There are two websites that needs to be maintained for GLIBC.
The first website is hosted on sourceware.org (sources.redhat.com) and the second on savannah.gnu.org.
Currently the two websites are different, the sourceware.org version is glibc developer centric.
As of 2011-01-31 the plan is to merge the websites into a single website hosted on savannah.gnu.org. At that point the sourceware.org website becomes a redirect.
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 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 website.
Modify libc.html to adjust wording for a newer release e.g. 2.11 vs. 2.12.
Check out sources for the sourceware.org website
Checkout via CVS the libc web sources (must have a sourceware.org account and have read and write privileges to the /cvs/glibc/htdocs directory.)
export CVS_RSH=ssh cvs -z 9 -d :ext:<membername>@sourceware.org:/cvs/glibc co htdocs
- Modify website.
Modify index.html to adjust wording for a newer release e.g. 2.11 vs. 2.12 or to add news entries.
- Check it back in. Update is instantaneous.