From db7a55cd76098755426bc1e72b744349ea494801 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 5 Sep 2007 09:05:15 +0000 Subject: added some links to in-depth info on the web --- doc/features.html | 13 ++++++++--- doc/version_naming.html | 61 ++++++++++++++++++++++++++----------------------- 2 files changed, 42 insertions(+), 32 deletions(-) diff --git a/doc/features.html b/doc/features.html index 725c3d7d..f451c857 100644 --- a/doc/features.html +++ b/doc/features.html @@ -43,7 +43,8 @@ is going on, you can also subscribe to the RFC 3195 as a sender - this is currently unlikely to happen, because there is no real demand for it. Any work on RFC 3195 has been suspend until we see some real interest in it. It is probably much better to use TCP-based syslog, - which is interoprable with a large number of applications. + which is interoperable with a large number of applications. You may also + read my blog post on the future of liblogging, which contains interesting + information about the + + future of RFC 3195 in rsyslog.

To see when each feature was added, see the rsyslog change log (online only).

diff --git a/doc/version_naming.html b/doc/version_naming.html index a1923fc2..31fe056e 100644 --- a/doc/version_naming.html +++ b/doc/version_naming.html @@ -1,30 +1,33 @@ - - -rsyslog bugs and annoyances - - -

Version Naming

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.

The major version is incremented whenever a considerate, major features have -been added. This is expected to happen quite infrequently.

The minor version number is incremented whenever there is "sufficient need" -(at the discretion of the developers). There is a notable difference between -stable and instable branches. The stable branch 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.

For the instable branch, 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.

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.

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.

- - + + +rsyslog bugs and annoyances + + +

Version Naming

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.

Please note that version naming is currently being changed. There is a +blog +post about future rsyslog versions.

The major version is incremented whenever a considerate, major features have +been added. This is expected to happen quite infrequently.

The minor version number is incremented whenever there is "sufficient need" +(at the discretion of the developers). There is a notable difference between +stable and instable branches. The stable branch 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.

For the instable branch, 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.

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.

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.

+ + \ No newline at end of file -- cgit