Is it time to move to 2.0?

[Stefan Bodewig <bo...@apache.org>]

Hi all,

not sure whether I find an audience big enough or whether we need to
expand this to the user list.

One option to get out of the oldkey/newkey problems mentioned in
https://issues.apache.org/jira/browse/LOG4NET-397 would be to make the
move to a log4net2 assembly.

The short term plan would be:

* branch off a 1.x branch from trunk in case we want to do a 1.2.13
  release one day

* remove the 1.x, Mono 1.x and compact framework builds

* start ripping out the .NET 1.x compatibility code as well as all
  NET_20 conditionals

* rename assembly to log4net2 - only sign it with the "new key"

* create log4net assemblies holding type forwarders to log4net2 -
  provide two versions with either key

* release soon

Pros:

* allows us to build all of log4net on Windows7 - right now I must keep
  an XP VM around and we all know XP will see an end of live soon.

* fixes the binding problems

Cons:

* lognet4 2.x would look like log4j 1.x not 2.x - this might confuse
  people.  Then again I don't envision us to port log4j2 any time soon
  because of our sheer lack of manpower.

* we'd lose an opportunity to remove more stuff we'd like to break
  backwards compatibility on - at least if "release soon" was taken
  seriously

WDYT?

Stefan

Re: Is it time to move to 2.0?

[d_k <ma...@gmail.com>]

If log4net2.x will imply a port of log4j2 then I think we should do log4net
1.3 and remove the .NET 1.x support.


On Tue, Oct 8, 2013 at 4:13 PM, Dominik Psenner <dp...@gmail.com> wrote:

> >> 1.2.11 already contained breaking changes and so did 1.2.12. Thus I
> would
> >> not mind breaking backwards compatibility within 1.X even further. The
> next
> >> good milestone could be 1.3 RC1 since we won't be compatible with log4j2
> >and
> >> we should go to 2.X only if we port log4j2 features into log4net.
> >
> >At least in JIRA I've set the expectation 2.x would be the version that
> >drops .NET 1.x support.  But that can be rectified easily.
> >
> >Would you also drop .NET 1.x support in 1.3.x then?
>
> +1
>
>

AW: Is it time to move to 2.0?

[Dominik Psenner <dp...@gmail.com>]

>> 1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
>> not mind breaking backwards compatibility within 1.X even further. The
next
>> good milestone could be 1.3 RC1 since we won't be compatible with log4j2
>and
>> we should go to 2.X only if we port log4j2 features into log4net.
>
>At least in JIRA I've set the expectation 2.x would be the version that
>drops .NET 1.x support.  But that can be rectified easily.
>
>Would you also drop .NET 1.x support in 1.3.x then?

+1

Re: Is it time to move to 2.0?

[Stefan Bodewig <bo...@apache.org>]

On 2013-10-08, Dominik Psenner wrote:

> 1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
> not mind breaking backwards compatibility within 1.X even further. The next
> good milestone could be 1.3 RC1 since we won't be compatible with log4j2 and
> we should go to 2.X only if we port log4j2 features into log4net.

At least in JIRA I've set the expectation 2.x would be the version that
drops .NET 1.x support.  But that can be rectified easily.

Would you also drop .NET 1.x support in 1.3.x then?

Stefan

AW: Is it time to move to 2.0?

[Dominik Psenner <dp...@apache.org>]

1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
not mind breaking backwards compatibility within 1.X even further. The next
good milestone could be 1.3 RC1 since we won't be compatible with log4j2 and
we should go to 2.X only if we port log4j2 features into log4net.