summaryrefslogtreecommitdiffstats
path: root/doc/version_naming.html
blob: a685f5ff7bef38d7ea13f3694bac2f4ae9e01b08 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<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 unstable and have a 
different naming schema.</p>
<p><b>Please note that version naming is currently being changed. There is a
<a href="http://rgerhards.blogspot.com/2007/08/on-rsyslog-versions.html">blog 
post about future rsyslog versions</a>.</b></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 unstable 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>unstable 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 unstable 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>