Wed 11/11/2009 2:04 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Michael Foord wrote:
> Keith J. Farmer wrote:
>> While technically true -- I can't *stop* them -- I can tell them "I
>> told you so" when support is righ
sion of IronPython
*Subject:* Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Keith J. Farmer wrote:
> Well, perhaps because I don't see the upside in breaking things,
either. Where I see an upside is in keeping people from taking
inappropriate dependencies. :)
>
You won't
either. It's simply common
sense.
*From:* users-boun...@lists.ironpython.com on behalf of Michael Foord
*Sent:* Wed 11/11/2009 1:20 PM
*To:* Discussion of IronPython
*Subject:* Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Keith J. Farmer wrote:
> Well, perhaps becaus
IronPython
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Keith J. Farmer wrote:
> Well, perhaps because I don't see the upside in breaking things, either.
> Where I see an upside is in keeping people from taking inappropriate
> dependencies. :)
>
You won't sto
1:32 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Hmm... I certainly don't suggest that the dynamic languages team
*support* obsolete versions, but in my experience it is 'unusual' for an
open source project to make previously released cod
ython] IronPython 2.6 RC 1 Release Hidden
Hmm... I certainly don't suggest that the dynamic languages team
*support* obsolete versions, but in my experience it is 'unusual' for an
open source project to make previously released code / binaries
*completely* unavailable - support n
n light of the above, then, I'd propose keeping the following versions:
>
> max(x).y.max(z)[.max(b)]
>
> and strongly consider keeping:
>
> [max(x)-1].y.max(z)[.max(b)]
>
> ------------------------
> *From:* users-boun...@lists.ironpython.c
caption "the version you are requesting has been obsoleted and is no
longer supported -- use at your own risk" be an acceptable approach? :)
From: users-boun...@lists.ironpython.com on behalf of Michael Foord
Sent: Tue 11/10/2009 12:34 PM
To: Discussion
Of Tony Meyer
> Sent: Tuesday, November 10, 2009 12:37 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
>
> > I'm not in blanket agreement here. I'd agree for some releases to be
> > valid dependency points, but th
Tony Meyer wrote:
I'm not in blanket agreement here. I'd agree for some releases to be valid
dependency points, but things like RCs, betas, obsoleted third-level
versions -- not really.
Couldn't someone in the IronPython team talk to someone in the
CodePlex team and figure out a way for a
> I'm not in blanket agreement here. I'd agree for some releases to be valid
> dependency points, but things like RCs, betas, obsoleted third-level
> versions -- not really.
Couldn't someone in the IronPython team talk to someone in the
CodePlex team and figure out a way for all releases to be pe
[max(x)-1].y.max(z)[.max(b)]
*From:* users-boun...@lists.ironpython.com on behalf of Michael Foord
*Sent:* Tue 11/10/2009 11:25 AM
*To:* Discussion of IronPython
*Subject:* Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Keith J. Farmer wrote:
> "making releases that
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Keith J. Farmer wrote:
> "making releases that people / projects may have depended on is an
> unacceptable cost"
>
> You wanna rephrase that there, Michael? :)
>
Ha. :-)
making unavailable releases that p
users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Michael Foord
Sent: Monday, November 09, 2009 1:47 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Jimmy Schementi wrote:
I agree, but I think the desire it to keep that "
ovember 09, 2009 1:47 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython 2.6 RC 1 Release Hidden
Jimmy Schementi wrote:
> I agree, but I think the desire it to keep that "Releases" list clean.
> Otherwise it would have every release ever in there. It's a CodeP
th Beta
1.0 7th Beta
~Jimmy
-Original Message-
From: users-boun...@lists.ironpython.com [mailto:users-
boun...@lists.ironpython.com] On Behalf Of Michael Foord
Sent: Monday, November 09, 2009 1:28 AM
To: Discussion of IronPython
Subject: [IronPython] IronPython 2.6 RC 1 Release Hid
nPython
Subject: [IronPython] IronPython 2.6 RC 1 Release Hidden
Hello guys,
IronPython 2.6 Release Candidate 2 supersedes Release Candidate 1, so the RC
1 download has been set to hidden. This means that it is no longer available
to choose from the list of downloads and links to the download page are
[mailto:users-
> boun...@lists.ironpython.com] On Behalf Of Michael Foord
> Sent: Monday, November 09, 2009 1:28 AM
> To: Discussion of IronPython
> Subject: [IronPython] IronPython 2.6 RC 1 Release Hidden
>
> Hello guys,
>
> IronPython 2.6 Release Candidate 2 supersedes Release Candidate 1,
Hello guys,
IronPython 2.6 Release Candidate 2 supersedes Release Candidate 1, so
the RC 1 download has been set to hidden. This means that it is no
longer available to choose from the list of downloads and links to the
download page are now effectively broken.
If you have wiki admin rights
19 matches
Mail list logo
