But I think we do intend to ensure that we still build on .NET 3.5 and above - we just won't be releasing those binaries ourselves. .NET 2.0 SP1 will be dropped completely and we won't be doing our normal extensive test passes on .NET 3.5.
> -----Original Message----- > From: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] On Behalf Of Dave Fugate > Sent: Thursday, June 24, 2010 10:38 AM > To: Discussion of IronPython > Subject: Re: [IronPython] IronPython 2.6 CodePlex Source Update > > That's our current thinking. > > Dave > > -----Original Message----- > From: users-boun...@lists.ironpython.com [mailto:users- > boun...@lists.ironpython.com] On Behalf Of Jeff Hardy > Sent: Thursday, June 24, 2010 9:01 AM > To: Discussion of IronPython > Subject: Re: [IronPython] IronPython 2.6 CodePlex Source Update > > > - .NET 4.0 is required for 2.7, not .NET 2.0 SP1 > > So does this mean there won't be a version of 2.7 for .NET 2.0? Fine by me - > supporting both for 2.6 is a pain. > > - Jeff > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
