On 2015-08-10, Jeremiah Gowdy wrote:
What’s the release schedule for log4net 1.3.0 look like?
I'm afraid we've managed to move us in state where trunk isn't ready to
get released and we don't find the time to finish it. And even if we
did, we wouldn't be creating the log4net people want today
What’s the release schedule for log4net 1.3.0 look like? The defects fixed in
LOG4NET-455 and LOG4NET-437 are pretty severe for anyone trying to use
async/await extensively. We were so desperate for a fix, we backported the
patches into 1.2.13 here:
https://github.com/freedomvoice/log4net
On 2013-11-07, Dominik Psenner wrote:
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see
On 2013-11-07, Dominik Psenner wrote:
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship
with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see
If there is, I'd be happy to wait anouther week, otherwise I'd proceed
with the release process and rather try to get trunk back into a
releasable state for a quick 1.3.0 afterwards.
Not anytime soon, sorry.
Understood. I'll have to re-tag anyway as my fix for what became
LOG4NET-404 was
Guys,
LOG4NET-393 is causing us some problems at $work. It's fixed as of 1.3.0, which
doesn't appear to be released yet. Is there an expected date for it to be
released, and if not what can I do to help make this happen?
And while I have your attention, I noticed that we released the log4net
On 2013-11-06, Nick Williams wrote:
LOG4NET-393 is causing us some problems at $work. It's fixed as of
1.3.0, which doesn't appear to be released yet. Is there an expected
date for it to be released, and if not what can I do to help make this
happen?
If you need anything fast, then it is
On 2013-11-06, Dominik Psenner wrote:
Since LOG4NET-393 is a blocker for people who work a lot with lambda
expressions and right now we have absolutely no idea as of when 1.3 will be
ready we might better release 1.2.13 containing the fix for the issue.
Yeah, no problem with that, I'll try to
Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: 06 November 2013 17:28
To: Log4NET Dev
Subject: Re: Log4Net 1.3.0
On 2013-11-06, Nick Williams wrote:
LOG4NET-393 is causing us some problems at $work. It's fixed as of
1.3.0, which doesn't appear to be released yet
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
2013/11/6 Stefan Bodewig bode...@apache.org
On 2013-11-06, Dominik Psenner wrote:
Since LOG4NET-393 is a blocker for people who work a lot with lambda
expressions and right now we have absolutely no idea as
Subject: Re: Log4Net 1.3.0
On 2013-11-06, Nick Williams wrote:
LOG4NET-393 is causing us some problems at $work. It's fixed as of
1.3.0, which doesn't appear to be released yet. Is there an expected
date for it to be released, and if not what can I do to help make this
happen?
If you
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see anything
you feel fits and we'll go from
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see anything
you feel fits and we'll go from
13 matches
Mail list logo
