Hi,
> Sure, but you could just make the 1.0 profile opt-in.
Every now and then somebody checks in code that doesn't build on the 1.0
profile (this happens several times a month).
If we make the 1.0 profile opt-in, these breakages won't get fixed
immediately, which will sooner or later lead to b
Hello,
> Personally, I think we'll waste more cycles on this than that it will bring
> benefit.
Well, it will happen in stages; Disabling the net_1_1 build will be the
first step, the second step will be the incremental removal of the
NET_1_1 removals and NET_2_0 as we transition into a world wh
Gert Driesen wrote:
>> -Original Message-
>> From: mono-list-boun...@lists.ximian.com
> [mailto:mono-list-boun...@lists.ximian.com] On Behalf Of Miguel de Icaza
>> Sent: dinsdag 21 juli 2009 17:50
>> To: Gert Driesen
>> Cc: 'mono-list'; 'Mono Announce'; 'mono-devel-list'
>> Subject: Re: [Mo
> -Original Message-
> From: mono-list-boun...@lists.ximian.com
[mailto:mono-list-boun...@lists.ximian.com] On Behalf Of Miguel de Icaza
> Sent: dinsdag 21 juli 2009 17:50
> To: Gert Driesen
> Cc: 'mono-list'; 'Mono Announce'; 'mono-devel-list'
> Subject: Re: [Mono-list] The Mono 1.0 profi
Hello Gert,
> Will you be removing all 1.0 specific code (paths)?
> Will support for building the net_1_1 profile be removed altogether (or will
> you just need to opt-in)?
Yes, I would like to do that: remove all the ifdefs for net_1_1 on post
Mono 2.6 releases, and remove all the tests for 1.1
Hi Miguel,
Can you be a little more specific?
Will you be removing all 1.0 specific code (paths)?
Will support for building the net_1_1 profile be removed altogether (or will
you just need to opt-in)?
Will you discourage packagers to include the net_1_1 profile?
I understand that Novell itself can
