release?

I'm still learning how to reply-to with my new-fangled gmail. I'm
forwarding this response on to the list....

···

---------- Forwarded message ----------
From: John Hunter <jdh2358@...149...>
Date: Feb 5, 2007 9:46 AM
Subject: Re: [matplotlib-devel] release?
To: Eric Firing <efiring@...229...>
Cc: cwmoad@...149...

On 2/5/07, Eric Firing <efiring@...229...> wrote:

It has been quite a while since 0.87.7, and I note that the ubuntu
feisty upstream version freeze date is Feb. 8. Is it time for a new mpl
release? If it were done within the next few days, would it get into
feisty? I acknowledge that I can offer no help with the release
process, and I don't know what it takes to get a release into
ubuntu--presumably the debian maintainer has to get it into debian
first--but I thought I would raise the question anyway.

I'm severely ham-strung at the moment since my build box died and I
haven't resurrected a new one yet. Charlie has been doing the win32
builds and may be able to do them for this release. That's the hard
part. Other than that, the main thing that needs to be done is to get
a fresh svn co and build, run backend_driver and memleak_hawaii and
make sure everything looks OK. If you can do that Eric, and Charlie
can do the win32 build, I'm all for it.

I just googled ubuntu matplotlib and got a page pointing to the old
debian 0.82 version. I know that is the main debian package people
are using but is it also the most recent ubuntu version. If so, just
getting them onto 0.87.7 would be a major advance. I thought ubuntu
was better about keeping up with current releases.

JDH

John Hunter wrote:

I'm still learning how to reply-to with my new-fangled gmail. I'm
forwarding this response on to the list....

From: John Hunter <jdh2358@...149...>
Date: Feb 5, 2007 9:46 AM
Subject: Re: [matplotlib-devel] release?
To: Eric Firing <efiring@...229...>
Cc: cwmoad@...149...

It has been quite a while since 0.87.7, and I note that the ubuntu
feisty upstream version freeze date is Feb. 8. Is it time for a new mpl
release? If it were done within the next few days, would it get into
feisty? I acknowledge that I can offer no help with the release
process, and I don't know what it takes to get a release into
ubuntu--presumably the debian maintainer has to get it into debian
first--but I thought I would raise the question anyway.

I'm severely ham-strung at the moment since my build box died and I
haven't resurrected a new one yet. Charlie has been doing the win32
builds and may be able to do them for this release. That's the hard
part. Other than that, the main thing that needs to be done is to get
a fresh svn co and build, run backend_driver and memleak_hawaii and
make sure everything looks OK. If you can do that Eric, and Charlie
can do the win32 build, I'm all for it.

OK, I did the fresh co and build and the checking, and I don't see any problems. (There is a deprecation warning in unicode_demo.py--not a show-stopper.)

I just googled ubuntu matplotlib and got a page pointing to the old
debian 0.82 version. I know that is the main debian package people
are using but is it also the most recent ubuntu version. If so, just
getting them onto 0.87.7 would be a major advance. I thought ubuntu
was better about keeping up with current releases.

Edgy appears to be offering 0.87.5, which is not quite so bad. I have no idea what will happen in Feisty, however.

Eric

···

---------- Forwarded message ----------
On 2/5/07, Eric Firing <efiring@...229...> wrote:

I'm listening, and I can do the windows builds. I'll run those tests
tonight and get back to the list.

- Charlie

···

On 2/5/07, Eric Firing <efiring@...229...> wrote:

John Hunter wrote:
> I'm still learning how to reply-to with my new-fangled gmail. I'm
> forwarding this response on to the list....
>
> ---------- Forwarded message ----------
> From: John Hunter <jdh2358@...149...>
> Date: Feb 5, 2007 9:46 AM
> Subject: Re: [matplotlib-devel] release?
> To: Eric Firing <efiring@...229...>
> Cc: cwmoad@...149...
>
> On 2/5/07, Eric Firing <efiring@...229...> wrote:
>> It has been quite a while since 0.87.7, and I note that the ubuntu
>> feisty upstream version freeze date is Feb. 8. Is it time for a new mpl
>> release? If it were done within the next few days, would it get into
>> feisty? I acknowledge that I can offer no help with the release
>> process, and I don't know what it takes to get a release into
>> ubuntu--presumably the debian maintainer has to get it into debian
>> first--but I thought I would raise the question anyway.
>
> I'm severely ham-strung at the moment since my build box died and I
> haven't resurrected a new one yet. Charlie has been doing the win32
> builds and may be able to do them for this release. That's the hard
> part. Other than that, the main thing that needs to be done is to get
> a fresh svn co and build, run backend_driver and memleak_hawaii and
> make sure everything looks OK. If you can do that Eric, and Charlie
> can do the win32 build, I'm all for it.

OK, I did the fresh co and build and the checking, and I don't see any
problems. (There is a deprecation warning in unicode_demo.py--not a
show-stopper.)

>
> I just googled ubuntu matplotlib and got a page pointing to the old
> debian 0.82 version. I know that is the main debian package people
> are using but is it also the most recent ubuntu version. If so, just
> getting them onto 0.87.7 would be a major advance. I thought ubuntu
> was better about keeping up with current releases.

Edgy appears to be offering 0.87.5, which is not quite so bad. I have
no idea what will happen in Feisty, however.

Eric

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Eric Firing wrote:

John Hunter wrote:

I'm still learning how to reply-to with my new-fangled gmail. I'm
forwarding this response on to the list....

From: John Hunter <jdh2358@...149...>
Date: Feb 5, 2007 9:46 AM
Subject: Re: [matplotlib-devel] release?
To: Eric Firing <efiring@...229...>
Cc: cwmoad@...149...

It has been quite a while since 0.87.7, and I note that the ubuntu
feisty upstream version freeze date is Feb. 8. Is it time for a new mpl
release? If it were done within the next few days, would it get into
feisty? I acknowledge that I can offer no help with the release
process, and I don't know what it takes to get a release into
ubuntu--presumably the debian maintainer has to get it into debian
first--but I thought I would raise the question anyway.

I'm severely ham-strung at the moment since my build box died and I
haven't resurrected a new one yet. Charlie has been doing the win32
builds and may be able to do them for this release. That's the hard
part. Other than that, the main thing that needs to be done is to get
a fresh svn co and build, run backend_driver and memleak_hawaii and
make sure everything looks OK. If you can do that Eric, and Charlie
can do the win32 build, I'm all for it.

OK, I did the fresh co and build and the checking, and I don't see any
problems. (There is a deprecation warning in unicode_demo.py--not a
show-stopper.)

I just googled ubuntu matplotlib and got a page pointing to the old
debian 0.82 version. I know that is the main debian package people
are using but is it also the most recent ubuntu version. If so, just
getting them onto 0.87.7 would be a major advance. I thought ubuntu
was better about keeping up with current releases.

Edgy appears to be offering 0.87.5, which is not quite so bad. I have
no idea what will happen in Feisty, however.

Yes, matplotlib version in edgy is 0.87.5, in feisty it is 0.87.7, see:

  http://packages.ubuntu.com/

Manuel

···

---------- Forwarded message ----------
On 2/5/07, Eric Firing <efiring@...229...> wrote:

--
---------------------------------------
  Manuel Metz ............ Stw@...468...
  Argelander Institut fuer Astronomie
  Auf dem Huegel 71 (room 3.06)
  D - 53121 Bonn

  E-Mail: mmetz@...459...
  Web: www.astro.uni-bonn.de/~mmetz
  Phone: (+49) 228 / 73-3660
  Fax: (+49) 228 / 73-3672
---------------------------------------

rev3002 works great for me. I can push the windows releases this
Saturday. I could push a source release sooner. Is anyone opposed to
me pushing a source release Friday with the binaries following up on
Saturday? If there are no objections, let's avoid major commits until
after then.

- Charlie

···

On 2/5/07, Charlie Moad <cwmoad@...149...> wrote:

I'm listening, and I can do the windows builds. I'll run those tests
tonight and get back to the list.

- Charlie

On 2/5/07, Eric Firing <efiring@...229...> wrote:
> John Hunter wrote:
> > I'm still learning how to reply-to with my new-fangled gmail. I'm
> > forwarding this response on to the list....
> >
> > ---------- Forwarded message ----------
> > From: John Hunter <jdh2358@...149...>
> > Date: Feb 5, 2007 9:46 AM
> > Subject: Re: [matplotlib-devel] release?
> > To: Eric Firing <efiring@...229...>
> > Cc: cwmoad@...149...
> >
> > On 2/5/07, Eric Firing <efiring@...229...> wrote:
> >> It has been quite a while since 0.87.7, and I note that the ubuntu
> >> feisty upstream version freeze date is Feb. 8. Is it time for a new mpl
> >> release? If it were done within the next few days, would it get into
> >> feisty? I acknowledge that I can offer no help with the release
> >> process, and I don't know what it takes to get a release into
> >> ubuntu--presumably the debian maintainer has to get it into debian
> >> first--but I thought I would raise the question anyway.
> >
> > I'm severely ham-strung at the moment since my build box died and I
> > haven't resurrected a new one yet. Charlie has been doing the win32
> > builds and may be able to do them for this release. That's the hard
> > part. Other than that, the main thing that needs to be done is to get
> > a fresh svn co and build, run backend_driver and memleak_hawaii and
> > make sure everything looks OK. If you can do that Eric, and Charlie
> > can do the win32 build, I'm all for it.
>
> OK, I did the fresh co and build and the checking, and I don't see any
> problems. (There is a deprecation warning in unicode_demo.py--not a
> show-stopper.)
>
> >
> > I just googled ubuntu matplotlib and got a page pointing to the old
> > debian 0.82 version. I know that is the main debian package people
> > are using but is it also the most recent ubuntu version. If so, just
> > getting them onto 0.87.7 would be a major advance. I thought ubuntu
> > was better about keeping up with current releases.
>
> Edgy appears to be offering 0.87.5, which is not quite so bad. I have
> no idea what will happen in Feisty, however.
>
> Eric
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Let's do the source release ASAP -- I'll update the website for win32
users to point to the older release so they can find it until the
win32 binaries are out. That way if ubuntu wants to use this for
their next release before the Feb 8th upstream freeze they can (and it
will give us one day to do a point bugfix release if the whole world
blows up). Just be sure that you use the same svn revision for the
src release and the win32 builds which will help us with user errors.
And email us when the new source is up so I'll know to make the
website change.

And let's call it 0.90 god-doggy. I'm getting tired of 0.87. There
is at least one signficant API breaking new feature (the pick API)
which alone justifies not making this a point release. There are also
several new features sampled below

2007-01-22 Extended the new picker API to text, patches and patch
           collections. Added support for user customizable pick hit
           testing and attribute tagging of the PickEvent - Details
           and examples in examples/pick_event_demo.py -

2007-01-11 Added Axes.xcorr and Axes.acorr to plot the cross
           correlation of x vs y or the autocorrelation of x. pylab
           wrappers also provided. See examples/xcorr_demo.py

2007-01-10 Added "Subplot.label_outer" method. It will set the
           visibility of the ticklabels so that yticklabels are only
           visible in the first column and xticklabels are only
           visible in the last row

2006-12-09 Replaced spy and spy2 with the new spy that combines
           marker and image capabilities

2006-12-19 Added Tim Leslie's spectral patch

2006-11-19 Added semi-automatic docstring generation detailing all the
           kwargs that functions take using the artist introspection
           tools; eg 'help text now details the scatter kwargs
           that control the Text properties

2006-11-05 Added broken_barh function for makring a sequence of
           horizontal bars broken by gaps -- see examples/broken_barh.py

Thanks!
JDH

···

On 2/6/07, Charlie Moad <cwmoad@...149...> wrote:

rev3002 works great for me. I can push the windows releases this
Saturday. I could push a source release sooner. Is anyone opposed to
me pushing a source release Friday with the binaries following up on
Saturday? If there are no objections, let's avoid major commits until
after then.

Ok, I'll try to get it posted on SF tonight.

···

On 2/6/07, John Hunter <jdh2358@...149...> wrote:

On 2/6/07, Charlie Moad <cwmoad@...149...> wrote:
> rev3002 works great for me. I can push the windows releases this
> Saturday. I could push a source release sooner. Is anyone opposed to
> me pushing a source release Friday with the binaries following up on
> Saturday? If there are no objections, let's avoid major commits until
> after then.

Let's do the source release ASAP -- I'll update the website for win32
users to point to the older release so they can find it until the
win32 binaries are out. That way if ubuntu wants to use this for
their next release before the Feb 8th upstream freeze they can (and it
will give us one day to do a point bugfix release if the whole world
blows up). Just be sure that you use the same svn revision for the
src release and the win32 builds which will help us with user errors.
And email us when the new source is up so I'll know to make the
website change.

And let's call it 0.90 god-doggy. I'm getting tired of 0.87. There
is at least one signficant API breaking new feature (the pick API)
which alone justifies not making this a point release. There are also
several new features sampled below

2007-01-22 Extended the new picker API to text, patches and patch
           collections. Added support for user customizable pick hit
           testing and attribute tagging of the PickEvent - Details
           and examples in examples/pick_event_demo.py -

2007-01-11 Added Axes.xcorr and Axes.acorr to plot the cross
           correlation of x vs y or the autocorrelation of x. pylab
           wrappers also provided. See examples/xcorr_demo.py

2007-01-10 Added "Subplot.label_outer" method. It will set the
           visibility of the ticklabels so that yticklabels are only
           visible in the first column and xticklabels are only
           visible in the last row

2006-12-09 Replaced spy and spy2 with the new spy that combines
           marker and image capabilities

2006-12-19 Added Tim Leslie's spectral patch

2006-11-19 Added semi-automatic docstring generation detailing all the
           kwargs that functions take using the artist introspection
           tools; eg 'help text now details the scatter kwargs
           that control the Text properties

2006-11-05 Added broken_barh function for makring a sequence of
           horizontal bars broken by gaps -- see examples/broken_barh.py

Thanks!
JDH