On 10 May 2012 21:21, Stefan Behnel wrote:
> mark florisson, 10.05.2012 21:13:
>> On 9 May 2012 08:49, Stefan Behnel wrote:
>>> Stefan Behnel, 09.05.2012 08:41:
Robert Bradshaw, 09.05.2012 00:16:
> If we're looking at doing 0.17 soon, lets just do that.
I think it's close enough to b
mark florisson, 10.05.2012 21:13:
> On 9 May 2012 08:49, Stefan Behnel wrote:
>> Stefan Behnel, 09.05.2012 08:41:
>>> Robert Bradshaw, 09.05.2012 00:16:
If we're looking at doing 0.17 soon, lets just do that.
>>> I think it's close enough to be released.
>>
>> ... although one thing I just not
On 9 May 2012 08:49, Stefan Behnel wrote:
> Stefan Behnel, 09.05.2012 08:41:
>> Robert Bradshaw, 09.05.2012 00:16:
>>> If we're looking at doing 0.17 soon, lets just do that.
>> I think it's close enough to be released.
>
> ... although one thing I just noticed is that the "numpy_memoryview" test
Stefan Behnel, 09.05.2012 10:51:
> Stefan Behnel, 09.05.2012 08:41:
>> Robert Bradshaw, 09.05.2012 00:16:
>>> If we're looking at doing 0.17 soon, lets just do that.
>>
>> I think it's close enough to be released. I'll try to get around to list
>> the changes in the release notes (and maybe even ad
Stefan Behnel, 09.05.2012 08:41:
> Robert Bradshaw, 09.05.2012 00:16:
>> If we're looking at doing 0.17 soon, lets just do that.
>
> I think it's close enough to be released. I'll try to get around to list
> the changes in the release notes (and maybe even add a note about alpha
> quality PyPy sup
On 9 May 2012 08:49, Stefan Behnel wrote:
> Stefan Behnel, 09.05.2012 08:41:
>> Robert Bradshaw, 09.05.2012 00:16:
>>> If we're looking at doing 0.17 soon, lets just do that.
>> I think it's close enough to be released.
>
> ... although one thing I just noticed is that the "numpy_memoryview" test
On 9 May 2012 07:41, Stefan Behnel wrote:
> Robert Bradshaw, 09.05.2012 00:16:
>> On Tue, May 8, 2012 at 12:04 PM, Vitja Makarov wrote:
>>> 2012/5/8 mark florisson:
On 8 May 2012 19:36, mark florisson wrote:
> Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
> picks
Stefan Behnel, 09.05.2012 08:41:
> Robert Bradshaw, 09.05.2012 00:16:
>> If we're looking at doing 0.17 soon, lets just do that.
> I think it's close enough to be released.
... although one thing I just noticed is that the "numpy_memoryview" test
is still disabled because it lead to crashes in rec
Robert Bradshaw, 09.05.2012 00:16:
> On Tue, May 8, 2012 at 12:04 PM, Vitja Makarov wrote:
>> 2012/5/8 mark florisson:
>>> On 8 May 2012 19:36, mark florisson wrote:
Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
picks over its own fixes into the release branch (at le
On Tue, May 8, 2012 at 12:04 PM, Vitja Makarov wrote:
> 2012/5/8 mark florisson :
>> On 8 May 2012 19:36, mark florisson wrote:
>>> Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
>>> picks over its own fixes into the release branch (at least Stefan,
>>> since your fixes perta
2012/5/8 mark florisson :
> On 8 May 2012 19:36, mark florisson wrote:
>> Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
>> picks over its own fixes into the release branch (at least Stefan,
>> since your fixes pertain to your newly merged branches and sometimes
>> to the mast
On 8 May 2012 19:36, mark florisson wrote:
> Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
> picks over its own fixes into the release branch (at least Stefan,
> since your fixes pertain to your newly merged branches and sometimes
> to the master branch itself). This branch s
Ok, so for the bugfix release 0.16.1 I propose that everyone cherry
picks over its own fixes into the release branch (at least Stefan,
since your fixes pertain to your newly merged branches and sometimes
to the master branch itself). This branch should not be merged back
into master, and any additi
13 matches
Mail list logo