summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2005-09-07 10:25:53 +0000
committerRainer Gerhards <rgerhards@adiscon.com>2005-09-07 10:25:53 +0000
commit8c1d2ef916b12c55604b4c7360597573ba03783f (patch)
tree62a0c7788a469a7185fc55f87158ec0a496961d6
parente4e8ca92341518ad9eb72b2655e814fb6f272d80 (diff)
downloadrsyslog-8c1d2ef916b12c55604b4c7360597573ba03783f.tar.gz
rsyslog-8c1d2ef916b12c55604b4c7360597573ba03783f.tar.xz
rsyslog-8c1d2ef916b12c55604b4c7360597573ba03783f.zip
added doc on version naming conventions
-rw-r--r--doc/status.html3
-rw-r--r--doc/version_naming.html30
2 files changed, 32 insertions, 1 deletions
diff --git a/doc/status.html b/doc/status.html
index 40d254ec..a1346ca8 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -7,7 +7,8 @@
<p>This page reflects the status as of 2005-09-05.</p>
<h2>Current Release</h2>
<p>0.9.8 - <a href="http://www.rsyslog.com/Article28.phtml">change log</a> -
-<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-14.phtml">download</a></p>
+<a href="http://www.rsyslog.com/Downloads-index-req-getit-lid-14.phtml">download</a>
+(<a href="version_naming.html">How are versions named?</a>)</p>
<h2>Platforms</h2>
<ul>
<li>Linux [tested on Red Hat &amp; Debian]</li>
diff --git a/doc/version_naming.html b/doc/version_naming.html
new file mode 100644
index 00000000..a1923fc2
--- /dev/null
+++ b/doc/version_naming.html
@@ -0,0 +1,30 @@
+<html>
+<head>
+<title>rsyslog bugs and annoyances</title>
+</head>
+<body>
+<h1>Version Naming</h1>
+<p>This document briefly outlines the strategy for naming versions. It applies
+to versions 1.0.0 and above. Versions below that are all instable and have a
+different naming schema.</p>
+<p>The major version is incremented whenever a considerate, major features have
+been added. This is expected to happen quite infrequently.</p>
+<p>The minor version number is incremented whenever there is &quot;sufficient need&quot;
+(at the discretion of the developers). There is a notable difference between
+stable and instable branches. The <b>stable branch</b> always has a minor
+version number in the range from 0 to 9. It is expected that the stable branch
+will receive bug and security fixes only. So the range of minor version numbers
+should be quite sufficient.</p>
+<p>For the <b>instable branch</b>, minor version numbers always start at 10 and
+are incremented as needed (again, at the discretion of the developers). Here,
+new minor versions include both fixes as well as new features (hopefully most of
+the time). They are expected to be released quite often.</p>
+<p>The patch level (third number) is incremented whenever a really minor thing
+must be added to an existing version. This is expected to happen quite
+infrequently.</p>
+<p>In general, the instable branch carries all new development. Once it
+concludes with a sufficiently-enhanced, quite stable version, a new major stable
+version is assigned.</p>
+
+</body>
+</html> \ No newline at end of file