I've just finished preparations for the release of syslog-ng 2.0.3 and now I consider the 2.0.x branch feature complete. As far as I know there's no feature that was present in 1.6.x and missing from the 2.0.x rewrite. The last missing bits were spoof-source and TCP wrapper support, but as those are present in 2.0.3 I consider syslog-ng 2.0 feature complete. I don't plan to add further code that would cause destabilization.
Now some plans about the newly opened 2.1 branch: we (as BalaBit) played with an idea of creating a commercial fork of syslog-ng which could increase the amount of resources that I can allocate to developing syslog-ng code. From 2.1 on, two parallel editions of syslog-ng will become available:
In the first release, the difference between the two editions are as follows:
Now some plans about the newly opened 2.1 branch: we (as BalaBit) played with an idea of creating a commercial fork of syslog-ng which could increase the amount of resources that I can allocate to developing syslog-ng code. From 2.1 on, two parallel editions of syslog-ng will become available:
- syslog-ng 2.1 Open Source Edition: the same as syslog-ng 2.0, available under the GPL
- syslog-ng 2.1 Premium Edition: a commercial fork of syslog-ng,
In the first release, the difference between the two editions are as follows:
- TLS support,
- Support for a Windows agent, capable of sending log messages in syslog-ng's extended log format and TLS encryption.
- New, updated manual (also covering the Open Source Edition).
Comments