A delay seems reasonable. On Tue, May 24, 2016 at 7:06 AM, Thomas D. <[email protected]> wrote:
> Hi, > > if it is not ready, don't release it. > > If you think that this release is important for the next rsyslog release > (i.e. the rsyslog master already contains changes which require current > libfastjson master so you would have to revert code from rsyslog just for > the planned release) feel free to delay the rsyslog release too when you > know you only need 1-2 more weeks: That's what I was talking about when > proposing the current release scheme... the 6 weeks aren't carved in stone. > > It should _help_ you by removing stress like "Oh, I don't get this into the > upcoming release but I don't have to worry because the next release is > already in sight" and not "Oh, if I don't get this done by date we will > have > to wait 6 more weeks..." > > > -- > Regards, > 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.
