diff --git a/MAINTAINING b/MAINTAINING index 12fc930cc..4b686b60c 100644 --- a/MAINTAINING +++ b/MAINTAINING @@ -253,15 +253,55 @@ Instructions on how to get the source code of Open Solaris can be found here (you'll need to install Mercurial ("hg")): http://dlc.sun.com/osol/on/downloads/hg-build-snapshots/ -The FreeBSD source code is avaiulable via anonymous CVS as described here: +The FreeBSD source code is available via anonymous CVS as described here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/anoncvs.html You'll want a command something like the following: cvs -d freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs co src +Making man-pages Releases +========================= + +Uploading files +--------------- + +New releases are copied (scp) to + + master.kernel.org:/pub/linux/docs/manpages + +All that needs to be copied there is the .tar.gz and the .lsm file. +Within a few minutes, automagic produces the .tar.bz2 files and +the .sign files, and eventually gets all of the files out to the +mirrors. + +I currently have my own script set up as a cron job to update the +LATEST-IS link, and update the links in the +/pub/linux/docs/manpages/Archive directory. + +The files copied to the above directory will be visible on the web at: + + http://www.kernel.org/pub/linux/docs/manpages + +Release notifications +--------------------- + +a) Contributors: Send a release message that includes the Change + log to all of the contributors of this release. + +b) Maintainers, translators, etc: A small group of people like + to get notification of *every* man-pages release. To do this + I manually maintain a list of those people, and send a + notification message to that list for each release. + One of the people on this list is Andries Brouwer, who + eventually copies the tarballs from kernel.org to + ftp://ftp.win.tue.nl/pub/linux-local/manpages. + +c) LKML: send a release note to lkml@vger.kernel.org, noting + those changes that are of special relevance to readers of LKML. + Release Philosophy -================== +------------------ If you make sweeping *formatting* changes on a large number of pages, separate them out into their own release that contains