From friedl at hq.adiscon.com  Tue Feb  7 17:03:00 2012
From: friedl at hq.adiscon.com (Florian Riedl)
Date: Tue, 7 Feb 2012 17:03:00 +0100
Subject: [Lognorm] liblognorm 0.3.3 released
Message-ID: <9B6E2A8877C38245BFB15CC491A11DA728188F@GRFEXC.intern.adiscon.com>

We have just released liblognorm 0.3.3.

This release is for bugfixing purposes only.

Changes:

Version 0.3.3 (rgerhards), 2012-02-06

-  required header file was not installed, resulting in compile error
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=307
    Thanks to Andreis Vinogradovs for alerting us on this bug.

Download:
http://www.liblognorm.com/files/download/liblognorm-0.3.3.tar.gz

As always, feedback is appreciated.

Best regards,
Florian Riedl

From friedl at hq.adiscon.com  Tue Feb 21 17:11:19 2012
From: friedl at hq.adiscon.com (Florian Riedl)
Date: Tue, 21 Feb 2012 17:11:19 +0100
Subject: [Lognorm] libee 0.4.0 released
Message-ID: <9B6E2A8877C38245BFB15CC491A11DA7281926@GRFEXC.intern.adiscon.com>

Hi all,

We have just released libee 0.4.0.

This version most importantly provides the ability to decode JSON and create
a libee representation out of it. This is vital functionality to build the
latest rsyslog, which supports structured logging via JSON-enhanced syslog.

Changes:

Version 0.4.0 (rgerhards), 2012-02-21

    rename convert tool to prevent name clash with ImageMagick's tool
    support for decoding json added
    bugfix: ee_newFieldFromNV() did not work correctly
    value was set, but number of values were not corrected, this the
    value could not be used (looked like non-present)

Download:
http://www.libee.org/download/libee-0-4-0/

As always, feedback is appreciated.

Best regards,
Florian Riedl

From rgerhards at hq.adiscon.com  Wed Feb 22 08:34:29 2012
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Wed, 22 Feb 2012 08:34:29 +0100
Subject: [Lognorm] libee/lognorm - APIs used?
Message-ID: <9B6E2A8877C38245BFB15CC491A11DA728192D@GRFEXC.intern.adiscon.com>

Hi all,

as you have probably noticed, I have begun to do some more work on libee.
This will be very substantial work as it will be enhanced to support upcoming
new versions of the standard. This will probably include a need to do API
changes. As such, I would appreciate if you could let me know which actual
API calls you are using, so that I can evaluate the risk in changing parts of
the API.

Thanks,
Rainer