On Thu, Sep 15, 2011 at 1:38 PM, Stefan Behnel wrote:
> Robert Bradshaw, 15.09.2011 22:31:
>>
>> On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote:
>>>
>>> Yaroslav Halchenko, 15.09.2011 17:08:
On Tue, 13 Sep 2011, Robert Bradshaw wrote:
>>
>> I guess we're set for a release t
Robert Bradshaw, 15.09.2011 22:31:
On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote:
Yaroslav Halchenko, 15.09.2011 17:08:
On Tue, 13 Sep 2011, Robert Bradshaw wrote:
I guess we're set for a release then, right?
+1. Should we send a release candidate around, or just cut it (as it
is b
On Thu, Sep 15, 2011 at 8:28 AM, Stefan Behnel wrote:
> Yaroslav Halchenko, 15.09.2011 17:08:
>>
>> On Tue, 13 Sep 2011, Robert Bradshaw wrote:
I guess we're set for a release then, right?
>>
>>> +1. Should we send a release candidate around, or just cut it (as it
>>> is bugfix-only and
Yaroslav Halchenko, 15.09.2011 17:08:
On Tue, 13 Sep 2011, Robert Bradshaw wrote:
I guess we're set for a release then, right?
+1. Should we send a release candidate around, or just cut it (as it
is bugfix-only and hasn't been too long since the last one)?
Also, is there a parameterized je
just to make sure -- 0.15.1 would come out from 'release' branch, right?
(there is motion to get fresh cython into debian and I am arguing that
it would be better to take post 0.15 snapshot)
On Tue, 13 Sep 2011, Robert Bradshaw wrote:
> > I guess we're set for a release then, right?
> +1. Should
On Tue, Sep 13, 2011 at 10:01 PM, Stefan Behnel wrote:
> Robert Bradshaw, 13.09.2011 05:49:
>>
>> On Mon, Sep 12, 2011 at 12:23 AM, Vitja Makarov wrote:
>>>
>>> 2011/9/11 Stefan Behnel:
Stefan Behnel, 11.09.2011 15:08:
>
> I see two ways to get a release out: create a branch from
Robert Bradshaw, 13.09.2011 05:49:
On Mon, Sep 12, 2011 at 12:23 AM, Vitja Makarov wrote:
2011/9/11 Stefan Behnel:
Stefan Behnel, 11.09.2011 15:08:
I see two ways to get a release out: create a branch from the current
master and remove from it what we don't consider stable (or 'right' for
tha
On Mon, Sep 12, 2011 at 12:23 AM, Vitja Makarov wrote:
> 2011/9/11 Stefan Behnel :
>> Stefan Behnel, 11.09.2011 15:08:
>>>
>>> I see two ways to get a release out: create a branch from the current
>>> master and remove from it what we don't consider stable (or 'right' for
>>> that release), or mer
2011/9/11 Stefan Behnel :
> Stefan Behnel, 11.09.2011 15:08:
>>
>> I see two ways to get a release out: create a branch from the current
>> master and remove from it what we don't consider stable (or 'right' for
>> that release), or merge the most important and easily mergeable changes
>> over to t
mark florisson, 11.09.2011 16:35:
On 11 September 2011 11:33, Stefan Behnel wrote:
Robert Bradshaw, 11.09.2011 07:54:
+1 to another release soon. Is there anything in the devel branch
that's not ready to go out?
Yes, the current state of my decorator changes breaks code in Sage. I
wouldn't kn
On 11 September 2011 11:33, Stefan Behnel wrote:
> Robert Bradshaw, 11.09.2011 07:54:
>>
>> On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
>>>
>>> Are we going to make a bugfix release?
>>>
>>> There are some critical bugs in 0.15, T725 for example.
>
> Yes, and some others.
>
>
>>> Think
Vitja Makarov, 11.09.2011 16:13:
2011/9/11 Stefan Behnel:
A problem with the current master branch is that we already dropped support
for Py2.3 in it...
I see two ways to get a release out: create a branch from the current master
and remove from it what we don't consider stable (or 'right' for
2011/9/11 Stefan Behnel :
> Stefan Behnel, 11.09.2011 13:33:
>>
>> Robert Bradshaw, 11.09.2011 07:54:
>>>
>>> On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
Are we going to make a bugfix release?
There are some critical bugs in 0.15, T725 for example.
>>
>> Yes, and some othe
Stefan Behnel, 11.09.2011 15:08:
I see two ways to get a release out: create a branch from the current
master and remove from it what we don't consider stable (or 'right' for
that release), or merge the most important and easily mergeable changes
over to the current release branch for 0.15.1 and
Stefan Behnel, 11.09.2011 13:33:
Robert Bradshaw, 11.09.2011 07:54:
On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
Are we going to make a bugfix release?
There are some critical bugs in 0.15, T725 for example.
Yes, and some others.
Think we should port fixes back to 0.15 and then re
Stefan Behnel, 11.09.2011 13:33:
Robert Bradshaw, 11.09.2011 07:54:
Is there anything in the devel branch that's not ready to go out?
Yes, the current state of my decorator changes breaks code in Sage. I
wouldn't know of anything else, so maybe it's enough to back those changes
out from a bran
Robert Bradshaw, 11.09.2011 07:54:
On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
Are we going to make a bugfix release?
There are some critical bugs in 0.15, T725 for example.
Yes, and some others.
Think we should port fixes back to 0.15 and then release it as 0.15.1
+1
+1 to
On 11 September 2011 07:54, Robert Bradshaw
wrote:
> +1 to another release soon. Is there anything in the devel branch
> that's not ready to go out? (I was also thinking of doing a release as
> soon as fused functions and memory views got in.)
>
> On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov
+1 to another release soon. Is there anything in the devel branch
that's not ready to go out? (I was also thinking of doing a release as
soon as fused functions and memory views got in.)
On Sat, Sep 10, 2011 at 10:32 PM, Vitja Makarov wrote:
> Are we going to make a bugfix release?
>
> There are
19 matches
Mail list logo
