On Wed, Apr 6, 2011 at 4:19 PM, Tomas Matousek
wrote:
> I think having the V2 build there but not actively tested works fine. Anybody
> who wants to use the latest IPy 3.0 build on V2 could submit a patch that
> fixes v2 specific issues if there are any.
> What about "officially" declaring we do
On Wed, Apr 6, 2011 at 4:00 PM, Tomas Matousek
wrote:
> I'd be fine with dropping support for *Desktop* v2.0. We need to support
> Silverlight 3 builds though so that we continue running on Windows Phone 7.
> This essentially means we can't get rid of the inner ring just yet. Do you
> consider
n place and not intentionally remove v2 specific code. Sounds
good?
Tomas
-Original Message-
From: Jeff Hardy [mailto:jdha...@gmail.com]
Sent: Wednesday, April 06, 2011 3:10 PM
To: ironruby-core@rubyforge.org
Cc: Tomas Matousek
Subject: Re: [Ironruby-core] Dropping .NET 2.0 Support for I
day, April 06, 2011 2:27 PM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] Dropping .NET 2.0 Support for IronRuby
Right now, the plan is for IronPython to drop support for .NET 2.0 and be .NET
4 only for the 3.0 release (which is probably still a year or more away). Are
there any similar p
Right now, the plan is for IronPython to drop support for .NET 2.0 and
be .NET 4 only for the 3.0 release (which is probably still a year or
more away). Are there any similar plans for IronRuby? IP can drop 2.0
support without impacting IR at all (I think), but if there plans to
drop it from IR as