On 9/17/2011 7:16 PM, Eric Firing wrote:
> On 09/17/2011 12:17 PM, Christoph Gohlke wrote:
>>
>>
>> On 9/17/2011 2:08 PM, Benjamin Root wrote:
>>> I think it will take a declaration of a firm deadline. How about this?
>>>
>>> Cut RC release Friday, Sept 23rd
>>> Release v1.1.0 Friday, Sept. 30th
On 09/17/2011 12:17 PM, Christoph Gohlke wrote:
>
>
> On 9/17/2011 2:08 PM, Benjamin Root wrote:
>> I think it will take a declaration of a firm deadline. How about this?
>>
>> Cut RC release Friday, Sept 23rd
>> Release v1.1.0 Friday, Sept. 30th.
>> (Barring any major significant changes)
>>
>> I
I tried running the nosetests, and got failures. I put in a pull
request to take care of one source, but three remain:
symlog2 svg
image_interp pdf
tight_layout5 svg
I have only looked into the last of these, which has nothing to do
directly with tight_layout; on my system, the svg file is bei
On Sat, Sep 17, 2011 at 7:01 PM, Benjamin Root wrote:
> Agreed. Let's declare a feature freeze at this point. Unless you already
> have a pull, no new features, and even those with existing pulls need to be
> carefully considered. I already have to make some updates to the "what's
> new" sectio
On Saturday, September 17, 2011, John Hunter wrote:
> On Sat, Sep 17, 2011 at 4:08 PM, Benjamin Root wrote:
>> I think it will take a declaration of a firm deadline. How about this?
>>
>> Cut RC release Friday, Sept 23rd
>> Release v1.1.0 Friday, Sept. 30th.
>> (Barring any major significant cha
On Sat, Sep 17, 2011 at 4:08 PM, Benjamin Root wrote:
> I think it will take a declaration of a firm deadline. How about this?
>
> Cut RC release Friday, Sept 23rd
> Release v1.1.0 Friday, Sept. 30th.
> (Barring any major significant changes)
Works for me; should we branch on the rc cut or befor
On 9/17/2011 2:08 PM, Benjamin Root wrote:
> I think it will take a declaration of a firm deadline. How about this?
>
> Cut RC release Friday, Sept 23rd
> Release v1.1.0 Friday, Sept. 30th.
> (Barring any major significant changes)
>
> In particular, for the RC, I want to make sure that installa
I think it will take a declaration of a firm deadline. How about this?
Cut RC release Friday, Sept 23rd
Release v1.1.0 Friday, Sept. 30th.
(Barring any major significant changes)
In particular, for the RC, I want to make sure that installation and
documents for the installation is solid. I will
What will it take to get a release out, so that debian, ubuntu, etc. can
have something better than 1.0.1? And so that the python 3 merge can
take place?
Eric
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, C
