You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Nick Williams <ni...@nicholaswilliams.net> on 2013/11/06 16:57:26 UTC

Log4Net 1.3.0

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 NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12 were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as "2.0.2." Since I've only been with Apache Logging since the spring and I'm completely new to log4net, can someone shed some light on all of this for me? It doesn't make a whole lot of sense. Thanks.

Nick

Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-11-07, Stefan Bodewig wrote:

> I'll try to find some time for a short triage and come back.

Found one old bug that looked easy and relatively safe to fix, so I did
just that.  I don't intend to put more changes into the release myself.

Unless anybody else wants to do additional work, I'll cut the release
over the weekend.

Stefan

Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@apache.org>.
>> 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 incomplete (that's what you get for not even compiling
after a partial merge).

I'll try to find some time for a short triage and come back.

Stefan

AW: Log4Net 1.3.0

Posted by Dominik Psenner <dp...@gmail.com>.
>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 anything
>>> you feel fits and we'll go from there.
>
>> I may spare some time in the weekend, thus feel free to go on.
>
>Do you think you can have a quick look to see whether there is any
>"quick fix" kind of ticket - to me nothing jumps out right now.
>
>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.


Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@apache.org>.
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 anything
>> you feel fits and we'll go from there.

> I may spare some time in the weekend, thus feel free to go on.

Do you think you can have a quick look to see whether there is any
"quick fix" kind of ticket - to me nothing jumps out right now.

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.

Stefan

AW: Log4Net 1.3.0

Posted by Dominik Psenner <dp...@gmail.com>.
>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 there.

I may spare some time in the weekend, thus feel free to go on.


Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@apache.org>.
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 there.

Stefan

Re: Log4Net 1.3.0

Posted by Dominik Psenner <dp...@gmail.com>.
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.


2013/11/6 Stefan Bodewig <bo...@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 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 find time to cut a new release
> over the next few days.
>
> In addition it will contain fixes for LOGNET-394 and LOG4NET-399 as this
> os the state when I created the 1.2.x branch.
>
> Stefan
>



-- 
Dominik Psenner

Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@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 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 find time to cut a new release
over the next few days.

In addition it will contain fixes for LOGNET-394 and LOG4NET-399 as this
os the state when I created the 1.2.x branch.

Stefan

Re: Log4Net 1.3.0

Posted by Dominik Psenner <dp...@gmail.com>.
Hey Stefan

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.

Cheers


2013/11/6 Stefan Bodewig <bo...@apache.org>

> 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 probably easier to cut 1.2.13 from
> the 1.x branch - 1.3.x is still undergoing quite a bit of non-productive
> reshuffling.
>
> > And while I have your attention, I noticed that we released the
> > log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12
> > were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as
> > "2.0.2." Since I've only been with Apache Logging since the spring and
> > I'm completely new to log4net, can someone shed some light on all of
> > this for me? It doesn't make a whole lot of sense. Thanks.
>
> The NuGet package is not provided by us, we don't have any influence on
> or insight into it.
>
> <https://github.com/cincuranet/log4net-nuget>
>
> Stefan
>



-- 
Dominik Psenner

Re: Log4Net 1.3.0

Posted by Dominik Psenner <dp...@gmail.com>.
Ideally there would be two different packages for the strong name and the
new name, but this has to be discussed with the package maintainer.


2013/11/6 Joe <jo...@hotmail.com>

> > And while I have your attention, I noticed that we released the
> > log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12
> > were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as
> > "2.0.2." Since I've only been with Apache Logging since the spring and
> > I'm completely new to log4net, can someone shed some light on all of
> > this for me? It doesn't make a whole lot of sense. Thanks.
>
> The provider of the log4net package can provide more details, but the basic
> reason is that nugget packages are expected to use semantic versioning:
>
> http://semver.org/
>
> Since the Nuget package including log4net 1.2.11 ships the version with the
> new strong name key, it's a breaking change, and therefore a new major
> version is required by the semantic versioning rules.
>
> Personally I'd have preferred to see the old strong name key shipped, but
> that's a different issue...
>
>
>
> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@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. 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 probably easier to cut 1.2.13 from
> the
> 1.x branch - 1.3.x is still undergoing quite a bit of non-productive
> reshuffling.
>
> > And while I have your attention, I noticed that we released the
> > log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12
> > were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as
> > "2.0.2." Since I've only been with Apache Logging since the spring and
> > I'm completely new to log4net, can someone shed some light on all of
> > this for me? It doesn't make a whole lot of sense. Thanks.
>
> The NuGet package is not provided by us, we don't have any influence on or
> insight into it.
>
> <https://github.com/cincuranet/log4net-nuget>
>
> Stefan
>
>


-- 
Dominik Psenner

RE: Log4Net 1.3.0

Posted by Joe <jo...@hotmail.com>.
> And while I have your attention, I noticed that we released the 
> log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12 
> were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as 
> "2.0.2." Since I've only been with Apache Logging since the spring and 
> I'm completely new to log4net, can someone shed some light on all of 
> this for me? It doesn't make a whole lot of sense. Thanks.

The provider of the log4net package can provide more details, but the basic
reason is that nugget packages are expected to use semantic versioning:

http://semver.org/

Since the Nuget package including log4net 1.2.11 ships the version with the
new strong name key, it's a breaking change, and therefore a new major
version is required by the semantic versioning rules.

Personally I'd have preferred to see the old strong name key shipped, but
that's a different issue...



-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@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. 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 probably easier to cut 1.2.13 from the
1.x branch - 1.3.x is still undergoing quite a bit of non-productive
reshuffling.

> And while I have your attention, I noticed that we released the 
> log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12 
> were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as 
> "2.0.2." Since I've only been with Apache Logging since the spring and 
> I'm completely new to log4net, can someone shed some light on all of 
> this for me? It doesn't make a whole lot of sense. Thanks.

The NuGet package is not provided by us, we don't have any influence on or
insight into it.

<https://github.com/cincuranet/log4net-nuget>

Stefan


Re: Log4Net 1.3.0

Posted by Stefan Bodewig <bo...@apache.org>.
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 probably easier to cut 1.2.13 from
the 1.x branch - 1.3.x is still undergoing quite a bit of non-productive
reshuffling.

> And while I have your attention, I noticed that we released the
> log4net NuGet package for 1.2.10 as "1.2.10", but 1.2.11 and 1.2.12
> were "2.0.0" and "2.0.1," respectively. 1.2.12 was then re-released as
> "2.0.2." Since I've only been with Apache Logging since the spring and
> I'm completely new to log4net, can someone shed some light on all of
> this for me? It doesn't make a whole lot of sense. Thanks.

The NuGet package is not provided by us, we don't have any influence on
or insight into it.

<https://github.com/cincuranet/log4net-nuget>

Stefan