re lease schedule for next version

Hi,
There's a number of bugs fixed that would be nice to have without running
git versions.
Is there a release schedule for the next version?

···

--
View this message in context: http://old.nabble.com/release-schedule-for-next-version-tp33378272p33378272.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

There is not one in place right now. In about a month, I will be starting up my new job, which I hope will allow me to devote more time and effort to this project. There are a number of features I have in mind to get added and there are many pull requests that needs evaluating.

Even if you are not a developer, members of this community can still help us out by trying out pull requests and letting us know if it works for them.

Cheers!

Ben Root

···

On Thursday, February 23, 2012, RuiDC wrote:

Hi,

There’s a number of bugs fixed that would be nice to have without running

git versions.

Is there a release schedule for the next version?

I would be interested in accelerating the schedule. Since this is a bug-fix release and not a major release, we can presume the tree is pretty stable. How about we aim for an release candidate rc1 the week after next? Are there any issues or pull requests that should hold the release? If so, let’s tag them with release-critical.

After we get the bugfix out I’d like to gear up for a major python3 release.

···

On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben.root@…553…> wrote:

On Thursday, February 23, 2012, RuiDC wrote:

Hi,

There’s a number of bugs fixed that would be nice to have without running

git versions.

Is there a release schedule for the next version?

There is not one in place right now. In about a month, I will be starting up my new job, which I hope will allow me to devote more time and effort to this project. There are a number of features I have in mind to get added and there are many pull requests that needs evaluating.

Even if you are not a developer, members of this community can still help us out by trying out pull requests and letting us know if it works for them.

The QT4 event handling bugs needs a qt expert on them. I tried looking into them and there is no obvious reason to me why they aren’t working.

I would be amendable to a bug-fix release soon to hold everybody over for the next major release.

Ben Root

···

On Saturday, February 25, 2012, John Hunter wrote:

On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben.root@…553…> wrote:

On Thursday, February 23, 2012, RuiDC wrote:

Hi,

There’s a number of bugs fixed that would be nice to have without running

git versions.

Is there a release schedule for the next version?

There is not one in place right now. In about a month, I will be starting up my new job, which I hope will allow me to devote more time and effort to this project. There are a number of features I have in mind to get added and there are many pull requests that needs evaluating.

Even if you are not a developer, members of this community can still help us out by trying out pull requests and letting us know if it works for them.

I would be interested in accelerating the schedule. Since this is a bug-fix release and not a major release, we can presume the tree is pretty stable. How about we aim for an release candidate rc1 the week after next? Are there any issues or pull requests that should hold the release? If so, let’s tag them with release-critical.

After we get the bugfix out I’d like to gear up for a major python3 release.

            Hi,
            There's a number of bugs fixed that would be nice to have
            without running
            git versions.
            Is there a release schedule for the next version?

        There is not one in place right now. In about a month, I will
        be starting up my new job, which I hope will allow me to devote
        more time and effort to this project. There are a number of
        features I have in mind to get added and there are many pull
        requests that needs evaluating.

        Even if you are not a developer, members of this community can
        still help us out by trying out pull requests and letting us
        know if it works for them.

    I would be interested in accelerating the schedule. Since this is a
    bug-fix release and not a major release, we can presume the tree is
    pretty stable. How about we aim for an release candidate rc1 the
    week after next? Are there any issues or pull requests that should
    hold the release? If so, let's tag them with release-critical.

    After we get the bugfix out I'd like to gear up for a major python3
    release.

The QT4 event handling bugs needs a qt expert on them. I tried looking
into them and there is no obvious reason to me why they aren't working.

Are you referring to 771, 707, and 525? 771 would appear to be the most urgent.

I would be amendable to a bug-fix release soon to hold everybody over
for the next major release.

Agreed.

Eric

···

On 02/25/2012 08:34 AM, Benjamin Root wrote:

On Saturday, February 25, 2012, John Hunter wrote:
    On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben.root@...553... > <javascript:_e({}, 'cvml', 'ben.root@...553...');>> wrote:
        On Thursday, February 23, 2012, RuiDC wrote:

Ben Root

711 and 707. Didn’t even notice 525, but it is probably related to 707. If true, then 707 and 525 are likely focus issues (maybe window-manager dependent?). 711 definitely seem to be release blocking.

Ben Root

···

On Saturday, February 25, 2012, Eric Firing wrote:

On 02/25/2012 08:34 AM, Benjamin Root wrote:

On Saturday, February 25, 2012, John Hunter wrote:

On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben.root@...553... >  > >     <javascript:_e({}, 'cvml', 'ben.root@...553...');>> wrote:
    On Thursday, February 23, 2012, RuiDC wrote:
        Hi,
        There's a number of bugs fixed that would be nice to have
        without running
        git versions.
        Is there a release schedule for the next version?
    There is not one in place right now.  In about a month, I will
    be starting up my new job, which I hope will allow me to devote
    more time and effort to this project.  There are a number of
    features I have in mind to get added and there are many pull
    requests that needs evaluating.
    Even if you are not a developer, members of this community can
    still help us out by trying out pull requests and letting us
    know if it works for them.
I would be interested in accelerating the schedule.  Since this is a
bug-fix release and not a major release, we can presume the tree is
pretty stable.  How about we aim for an release candidate rc1 the
week after next?  Are there any issues or pull requests that should
hold the release?  If so, let's tag them with release-critical.
After we get the bugfix out I'd like to gear up for a major python3
release.

The QT4 event handling bugs needs a qt expert on them. I tried looking

into them and there is no obvious reason to me why they aren’t working.

Are you referring to 771, 707, and 525? 771 would appear to be the

most urgent.

Hi Pierre, we are still having trouble with the close event in mpl figure windows not being emitted. I see you posted on this subject in 2009 and did some monkey patching to work around the problem for spyder

http://old.nabble.com/Qt4-backend%3A-critical-bug-with-PyQt4-v4.6%2B-td26205716.html

This was a while ago so I don’t know if your suggestions are still appropriate for recent pyqt and mpl. Would you have a minute to take a look at this mpl issue

https://github.com/matplotlib/matplotlib/issues/711

and advise us on a fix?

Thanks,

JDH

···

On Sat, Feb 25, 2012 at 1:54 PM, Benjamin Root <ben.root@…553…> wrote:

I would be interested in accelerating the schedule.  Since this is a
bug-fix release and not a major release, we can presume the tree is
pretty stable.  How about we aim for an release candidate rc1 the
week after next?  Are there any issues or pull requests that should
hold the release?  If so, let's tag them with release-critical.
After we get the bugfix out I'd like to gear up for a major python3
release.

The QT4 event handling bugs needs a qt expert on them. I tried looking

into them and there is no obvious reason to me why they aren’t working.

Are you referring to 771, 707, and 525? 771 would appear to be the

most urgent.

711 and 707. Didn’t even notice 525, but it is probably related to 707. If true, then 707 and 525 are likely focus issues (maybe window-manager dependent?). 711 definitely seem to be release blocking.

Hi John,

Replacing this (backend_qt4.py, class "FigureCanvasQT", line 141):

        QtCore.QObject.connect(self, QtCore.SIGNAL('destroyed()'),

                               self.close_event)

by this:

        QtCore.QObject.connect(self, QtCore.SIGNAL('destroyed()'),

                               lambda: self.close_event())

will solve this issue.

The reason is that PyQt fails (silently) to call a method of this

object just before detroying it. Using a lambda function will work,
exactly the same as using a function (which is not bound to the
object to be destroyed).

Side note: I'm not sure that it's the intended behavior for PyQt...

HTH,

Pierre
···

Le 25/02/2012 22:59, John Hunter a écrit :

    On Sat, Feb 25, 2012 at 1:54 PM, Benjamin > Root <ben.root@...553...> >         wrote:
            >     I would be interested in accelerating the

schedule. Since this is a

            >     bug-fix release and not a major release, we can

presume the tree is

            >     pretty stable.  How about we aim for an release

candidate rc1 the

            >     week after next?  Are there any issues or pull

requests that should

            >     hold the release?  If so, let's tag them with

release-critical.

            >

            >     After we get the bugfix out I'd like to gear up

for a major python3

            >     release.

            >

            >

            > The QT4 event handling bugs needs a qt expert on

them. I tried looking

            > into them and there is no obvious reason to me why

they aren’t working.

            Are you referring to  771, 707, and 525?  771 would

appear to be the

            most urgent.
        711 and 707.  Didn't even notice 525, but it is probably

related to 707. If true, then 707 and 525 are likely focus
issues (maybe window-manager dependent?). 711 definitely
seem to be release blocking.

      Hi Pierre, we are still having trouble with the close event

in mpl figure windows not being emitted. I see you posted on
this subject in 2009 and did some monkey patching to work
around the problem for spyder

http://old.nabble.com/Qt4-backend%3A-critical-bug-with-PyQt4-v4.6%2B-td26205716.html

      This was a while ago so I don't know if your suggestions

are still appropriate for recent pyqt and mpl. Would you have
a minute to take a look at this mpl issue

https://github.com/matplotlib/matplotlib/issues/711

and advise us on a fix?

Thanks,

JDH

I found out that a similar issue was reported for Spyder the same day
as this one...

So I just posted something about this bug on PyQt mailing list:
http://www.riverbankcomputing.com/pipermail/pyqt/2012-February/031166.html

-Pierre

···

Le 26 février 2012 12:23, Pierre Raybaut <pierre.raybaut@...149...> a écrit :

Le 25/02/2012 22:59, John Hunter a écrit :

On Sat, Feb 25, 2012 at 1:54 PM, Benjamin Root <ben.root@...553...> wrote:

> I would be interested in accelerating the schedule. Since this is
> a
> bug-fix release and not a major release, we can presume the tree is
> pretty stable. How about we aim for an release candidate rc1 the
> week after next? Are there any issues or pull requests that should
> hold the release? If so, let's tag them with release-critical.
>
> After we get the bugfix out I'd like to gear up for a major python3
> release.
>
>
> The QT4 event handling bugs needs a qt expert on them. I tried looking
> into them and there is no obvious reason to me why they aren't working.

Are you referring to 771, 707, and 525? 771 would appear to be the
most urgent.

711 and 707. Didn't even notice 525, but it is probably related to 707.
If true, then 707 and 525 are likely focus issues (maybe window-manager
dependent?). 711 definitely seem to be release blocking.

Hi Pierre, we are still having trouble with the close event in mpl figure
windows not being emitted. I see you posted on this subject in 2009 and did
some monkey patching to work around the problem for spyder

http://old.nabble.com/Qt4-backend%3A-critical-bug-with-PyQt4-v4.6%2B-td26205716.html

This was a while ago so I don't know if your suggestions are still
appropriate for recent pyqt and mpl. Would you have a minute to take a look
at this mpl issue

https://github.com/matplotlib/matplotlib/issues/711

and advise us on a fix?

Thanks,
JDH

Hi John,

Replacing this (backend_qt4.py, class "FigureCanvasQT", line 141):
QtCore.QObject.connect(self, QtCore.SIGNAL('destroyed()'),
self.close_event)
by this:
QtCore.QObject.connect(self, QtCore.SIGNAL('destroyed()'),
lambda: self.close_event())
will solve this issue.

The reason is that PyQt fails (silently) to call a method of this object
just before detroying it. Using a lambda function will work, exactly the
same as using a function (which is not bound to the object to be destroyed).

Side note: I'm not sure that it's the intended behavior for PyQt...

HTH,
Pierre

I added your fix in pull request https://github.com/matplotlib/matplotlib/pull/716 so it should come out in the bug fix release we are preparing.

Also, something you might be interested in for your qt apps: I exposed the default mpl key handling to embedded applications

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

Thanks a bunch for the suggested fix – this was a vexing issue and particularly bad for the animation examples which caused all of my demos to explode is a sea of C++ warnings when I closed the window.

JDH

···

On Sun, Feb 26, 2012 at 9:26 AM, Pierre Raybaut <pierre.raybaut@…149…> wrote:

I found out that a similar issue was reported for Spyder the same day

as this one…

So I just posted something about this bug on PyQt mailing list:

http://www.riverbankcomputing.com/pipermail/pyqt/2012-February/031166.html

Huge +1.

I understand that the majority of Python and hence matplotlib people work on *nix boxes, so if you'd like a hand with testing, or anything else come to think of it, on my Windows Vista box feel free to ask, as I've been using matplotlib for around seven years and don't mind trying to put a bit back in.

···

On 25/02/2012 17:13, John Hunter wrote:

After we get the bugfix out I'd like to gear up for a major python3 release.

--
Cheers.

Mark Lawrence.

That would be great-- you can cut your teeth testing the release candidates for the bugfix release in the current cycle, familiarize yourself with how to run the tests, etc.

We definitely have a shortage of OSX and windows testing, especially the latter, because few people run from git HEAD on windows, but lots of people do on linux.

Just chime in when you see the announcements for “rc” release candidates on the users or devel lists.

Thanks!

JDH

···

On Sun, Feb 26, 2012 at 6:16 PM, Mark Lawrence <breamoreboy@…705…> wrote:

On 25/02/2012 17:13, John Hunter wrote:

After we get the bugfix out I’d like to gear up for a major python3 release.

Huge +1.

I understand that the majority of Python and hence matplotlib people

work on *nix boxes, so if you’d like a hand with testing, or anything

else come to think of it, on my Windows Vista box feel free to ask, as

I’ve been using matplotlib for around seven years and don’t mind trying

to put a bit back in.

I'll be more than happy to provide similar help testing on Windows 7.
-paul

···

On Sun, Feb 26, 2012 at 5:52 PM, John Hunter <jdh2358@...149...> wrote:

On Sun, Feb 26, 2012 at 6:16 PM, Mark Lawrence <breamoreboy@...705...> > wrote:

On 25/02/2012 17:13, John Hunter wrote:

> After we get the bugfix out I'd like to gear up for a major python3
> release.

Huge +1.

I understand that the majority of Python and hence matplotlib people
work on *nix boxes, so if you'd like a hand with testing, or anything
else come to think of it, on my Windows Vista box feel free to ask, as
I've been using matplotlib for around seven years and don't mind trying
to put a bit back in.

That would be great-- you can cut your teeth testing the release candidates
for the bugfix release in the current cycle, familiarize yourself with how
to run the tests, etc.

We definitely have a shortage of OSX and windows testing, especially the
latter, because few people run from git HEAD on windows, but lots of people
do on linux.

Just chime in when you see the announcements for "rc" release candidates on
the users or devel lists.

Thanks!
JDH

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

same for me for RC’s on win7x64 and XPx32

···

From: Paul Hobson <pmhobson@…149…>
To: John Hunter <jdh2358@…149…>
Cc: matplotlib-devel@lists.sourceforge.net
Sent: Friday, 2 March 2012, 23:15
Subject: Re: [matplotlib-devel] re lease
schedule for next version

I’ll be more than happy to provide similar help testing on Windows 7.
-paul

On Sun, Feb 26, 2012 at 5:52 PM, John Hunter <jdh2358@…149…> wrote:

On Sun, Feb 26, 2012 at 6:16 PM, Mark Lawrence <breamoreboy@…705…> > wrote:

On 25/02/2012 17:13, John Hunter wrote:

After we get the bugfix out I’d like to gear up for a major python3
release.

Huge +1.

I understand that the majority of Python and hence matplotlib people
work on *nix boxes, so if you’d like a hand with testing, or anything
else come to think of it, on my Windows Vista box feel free to ask,
as

I’ve been using matplotlib for around seven years and don’t mind trying
to put a bit back in.

That would be great-- you can cut your teeth testing the release candidates
for the bugfix release in the current cycle, familiarize yourself with how
to run the tests, etc.

We definitely have a shortage of OSX and windows testing, especially the
latter, because few people run from git HEAD on windows, but lots of people
do on linux.

Just chime in when you see the announcements for “rc” release candidates on
the users or devel lists.

Thanks!
JDH


Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual
Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2


Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/


Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel