[matplotlib-devel] release: stalled again?

[Eric Firing]

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, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[Benjamin Root]

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 have on hand an older,
stock Macbook Pro with Snow Leopard and a relatively new iMac with Snow
Leopard (one is 32 bits while the other is 64, I think).

As a side note, the macbook can be used for automated build/test machine as
it really isn't useful for anything else for me.

Ben Root
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[Christoph Gohlke]

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 installation and
> documents for the installation is solid.  I will have on hand an older,
> stock Macbook Pro with Snow Leopard and a relatively new iMac with Snow
> Leopard (one is 32 bits while the other is 64, I think).
>
> As a side note, the macbook can be used for automated build/test machine
> as it really isn't useful for anything else for me.
>
> Ben Root
>

That sounds to me as if the master branch is at release quality, or very 
close to. I could test it on Windows this weekend if that's true.

Christoph

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[John Hunter]

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 before?  I suggest we
branch on the cut, but don't merge anything in before the 23rd that is
not release ready (eg Ben when you advised holding off on the
projection merge because it touched hairy parts of the code).

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[Benjamin Root]

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 changes)
>
> Works for me; should we branch on the rc cut or before?  I suggest we
> branch on the cut,

Agreed.  We still have some pull requests that point to master.  If we
branch before the cut, re-pulling just delays things.

> but don't merge anything in before the 23rd that is
> not release ready (eg Ben when you advised holding off on the
> projection merge because it touched hairy parts of the code).

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" section...

Ben Root
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[John Hunter]

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" section...

While you are working on 'what's new" could you consider adding a
section on the new sankey module and maybe inline one example from the
api/sankey_demo.py?  I think they are pretty snazzy.

https://github.com/matplotlib/matplotlib/pull/465

JDH

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] 3 test failures

[Eric Firing]

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 being 
generated with interpolation, even though the call to imshow has 
interpolation="none".  I don't know what is going on.  When I simply 
make an image with that kwarg and save to svg, it's fine.  But it is not 
working that way in the test.

Eric

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[Eric Firing]

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)
>>
>> In particular, for the RC, I want to make sure that installation and
>> documents for the installation is solid.  I will have on hand an older,
>> stock Macbook Pro with Snow Leopard and a relatively new iMac with Snow
>> Leopard (one is 32 bits while the other is 64, I think).
>>
>> As a side note, the macbook can be used for automated build/test machine
>> as it really isn't useful for anything else for me.
>>
>> Ben Root
>>
>
> That sounds to me as if the master branch is at release quality, or very
> close to. I could test it on Windows this weekend if that's true.

Christoph,

It should be close.  There are still three test failures, which I noted 
in a separate message to matplotlib-devel.

Eric

>
> Christoph
>
> --
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] release: stalled again?

[Christoph Gohlke]

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.
>>> (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 have on hand an older,
>>> stock Macbook Pro with Snow Leopard and a relatively new iMac with Snow
>>> Leopard (one is 32 bits while the other is 64, I think).
>>>
>>> As a side note, the macbook can be used for automated build/test machine
>>> as it really isn't useful for anything else for me.
>>>
>>> Ben Root
>>>
>>
>> That sounds to me as if the master branch is at release quality, or very
>> close to. I could test it on Windows this weekend if that's true.
>
> Christoph,
>
> It should be close.  There are still three test failures, which I noted
> in a separate message to matplotlib-devel.
>
> Eric
>
>>
>> Christoph
>>

The master branch builds OK on Windows and so far almost everything 
worked well.

I have trouble receiving the sample_data from github via cbook.py. There 
are frequent HTTP 304 (Not Modified) and 500 (Internal Server Error) 
exceptions and redirection to 
.

Christoph

--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel