2015-08-19 15:16 GMT+02:00 Thomas D. <[email protected]>: > Hi, > > David Lang wrote: >>> Another change in 1.1.2 that may bite people is that it introduces the >>> capability for rules to be multiline by allowing newlines inside a tag >>> definition. If someone has a bad config (uneven number of % on a line), the >>> newline will no longer terminate that bad rule, all rules follwoing it will >>> not be parsed (until it hits the next line with an uneven number of % on >>> the line) >>> >>> [...] >>> >>> Personally, I would probably concentrate on testing liblognorm-2.0 >> > and the upgrade process to it rather than spending much effort on >>> 1.1.2 > > Well, liblognorm-1.1.1 to 1.1.2 is a *minor* bump according to the > version number.
Well, we (rsyslog project) still use the "rsyslog traditional versioning scheme" for this version of liblognorm, and this means 1.1.2 was just not yet ready for 1.2, because all 1.1 goals were not reached. It doesn't mean its a bugfixing relaese only. That's of course different from your expectation, but no point in arguing on it -- that's how it is. In v2, we can change that, and will probably move to the new rsyslog scheme (a new release every 6 weeks with incrementing x version (as in 2.x.y)). I released 1.1.2 because people asked about the many new parsers that were already avaiable in the v1 codebase while I was working towards v2. So if you want to hold it back, feel free to do so until v2 is released, which probably is soon the case ). Rainer > > This shouldn't require any test to be rewritten or break any software > which was working with liblognorm-1.1.1. If it does, it isn't a minor > bump and the version number/SONAME is wrong ;) > > We bumped liblognorm because we thought it is just a bugfix release... > > Regarding your first paragraph: You said "has a bad config"... if that > mean that the user wrote something which was violating specs but was > working due to a bug and now because the bug is fixed in v1.1.2 it will > break like it should from the beginning, that's ok. If it is a changed > behavior, it isn't OK. > > > I created a PR (https://github.com/rsyslog/rsyslog/pull/492) which > enables mmnormalize in Travis to keep track. > > > -Thomas > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of > sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
