From: Harlan Stenn Date: Sun, 9 Apr 2006 09:25:08 +0000 (-0400) Subject: README* updates X-Git-Tag: NTP_4_2_1P10_RC~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=eb3908db4e40875066d61f7a1fdcd86c5b5ef7d2;p=thirdparty%2Fntp.git README* updates bk: 4438d2f4mRPVld3CtLxvVK6xkfY0JA --- diff --git a/README b/README index f9eeabcc5..186caa882 100644 --- a/README +++ b/README @@ -1,7 +1,7 @@ Submit patches, bug reports, and enhancement requests via - http://bugzilla.ntp.org + http://bugs.ntp.isc.org The ntp Distribution Base Directory diff --git a/README.bk b/README.bk index fa92b52bf..dc867b52e 100644 --- a/README.bk +++ b/README.bk @@ -1,55 +1,7 @@ -In order to use the BitKeeper repository version of NTP you will have -to have the following tools installed: +In order to use the BitKeeper repository version of NTP you should visit - autoconf 2.58 or later - automake 1.8 or later - lynx + http://ntp.isc.org/Main/SoftwareDevelopment -Lynx is used to generate the COPYRIGHT file. Don't ask. - -You can get bitkeeper by visiting: - - http://www.bitkeeper.com/ - -We are using bitkeeper under their free license program. You can use -bitkeeper for free to access NTP, too. If you have questions about this, -please ask. The license is pretty easy to read. - -Once you have installed bitkeeper, you can clone any NTP repository. - -You can get the ntp-stable repository by either of the following commands: - - bk clone bk://www.ntp.org/home/bk/ntp-stable ntp-stable - - bk clone bk://ntp.bkbits.net/ntp-stable ntp-stable - -You can get the ntp-dev repository by either of the following commands: - - bk clone bk://www.ntp.org/home/bk/ntp-dev ntp-dev - - bk clone bk://ntp.bkbits.net/ntp-dev ntp-dev - -If you are stuck behind a firewall that blocks access to the default port -used by bitkeeper (14690) but you can use port 80 instead, you can use -http as a bk transport mechanism. Just use: - - bk clone http://ntp.bkbits.net/REPO REPO - -Finally, it's possible to use SMTP as a bk transport mechanism. So far, we -haven't tried this. - -Once you have obtained the sources, do the following: - - cd REPO - bk -r edit to check out the files - autoreconf -f -i generates configure and Makefile.in's - -and you should be ready to go. You will get some warning messages from -autoreconf. Ignore these messages. - -You can update your repository by incanting: - - cd REPO - bk pull +for important information. If you want to submit patches, please see the README.hackers file. diff --git a/README.versions b/README.versions index 550925015..0fb23e5bb 100644 --- a/README.versions +++ b/README.versions @@ -1,35 +1,27 @@ NTP uses A.B.C - style release numbers. -The third (C) part of the version number can be: - - 0-69 for patches/bugfixes to the A.B.C series. - 70-79 for alpha releases of the A.B+1.0 series. - 80+ for beta releases of the A.B+1.0 series. - At the moment: A is 4, for ntp V4. - B is the minor release number. - C is the patch/bugfix number, and may have extra cruft in it. + B is the major release number. + C is the minor release number. Even numbers are 'stable' releases and + odd numbers are "development" releases. -Any extra cruft in the C portion of the number indicates an "interim" release. +Following the release number may be the letter 'p' followed by a number. +This indicates a point (or patch) release. -Interim releases almost always have a C portion consisting of a number -followed by an increasing letter, optionally followed by -rcX, where X -is an increasing number. The -rcX indicates a "release candidate". +Release candidates have -RC in the release number. Here are some recent versions numbers as an example: - 4.1.0 A production release (from the ntp-stable repository) - 4.1.0b-rc1 A release candidate for 4.1.1 (from the ntp-stable repo) - 4.1.71 An alpha release of 4.2.0, from the ntp-dev repo + 4.2.2 A production release (from the ntp-stable repository) + 4.2.2p2 A production release (from the ntp-stable repository) + 4.2.3p12 A development release + 4.2.3p15-rc1 A release candidate for 4.2.2 Note that after the ntp-dev repo produces a production release it will be copied into the ntp-stable and the cycle will repeat. -The goal of this scheme is to produce version numbers that collate -"properly" with the output of the "ls" command. - Feel free to suggest improvements...