Radio silence about the 1.4.0 release...

I'm well aware that we were scheduled to get a 1.4.0 release out in January. Unfortunately, other work commitments and travel have kept me from matplotlib over recent weeks, and it doesn't look like it's going to get much better in the short term either. If anyone wants to volunteer to take up the release manager role this time around, I, for one, would certainly be appreciative. But if no one else is available, I'd be glad for any help "around the edges".

The time consuming part of making the release is triaging all of the pending bugs and pull requests. It looks like we have 62 for 1.4.x and another 12 on 1.3.x at the moment. Then ideally we make sure all important changes are in What's New.

Beyond that, the release is essentially mechanical and pretty well documented (though the new wrinkle this time around is uploading files to PyPI since pip is no longer trusting of files on SourceForge).

Mike

···

--
                    _

\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
>>(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |

http://www.droettboom.com

Unless someone else really wants to do this, I will volunteer.

Tom

···

On Tue, Feb 18, 2014 at 9:36 AM, Michael Droettboom <mdroe@...31...> wrote:

I'm well aware that we were scheduled to get a 1.4.0 release out in
January. Unfortunately, other work commitments and travel have kept me
from matplotlib over recent weeks, and it doesn't look like it's going
to get much better in the short term either. If anyone wants to
volunteer to take up the release manager role this time around, I, for
one, would certainly be appreciative. But if no one else is available,
I'd be glad for any help "around the edges".

The time consuming part of making the release is triaging all of the
pending bugs and pull requests. It looks like we have 62 for 1.4.x and
another 12 on 1.3.x at the moment. Then ideally we make sure all
important changes are in What's New.

Beyond that, the release is essentially mechanical and pretty well
documented (though the new wrinkle this time around is uploading files
to PyPI since pip is no longer trusting of files on SourceForge).

Mike

--
                    _
>\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
> >>(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |

http://www.droettboom.com

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

--
Thomas Caswell
tcaswell@...149...

To this end, I have renamed the current 1.4.x milestone -> 1.4.0 and
created a new 1.4.x mile stone. Issues that are bug
fixes/enhancements that should target the _next_ maintenance release,
but may not get into shape in the very near future should be moved to
the new mile stone.

Do we want to do a 1.3.2 at the same time?

Tom

···

On Tue, Feb 18, 2014 at 9:36 AM, Michael Droettboom <mdroe@...31...> wrote:

I'm well aware that we were scheduled to get a 1.4.0 release out in
January. Unfortunately, other work commitments and travel have kept me
from matplotlib over recent weeks, and it doesn't look like it's going
to get much better in the short term either. If anyone wants to
volunteer to take up the release manager role this time around, I, for
one, would certainly be appreciative. But if no one else is available,
I'd be glad for any help "around the edges".

The time consuming part of making the release is triaging all of the
pending bugs and pull requests. It looks like we have 62 for 1.4.x and
another 12 on 1.3.x at the moment. Then ideally we make sure all
important changes are in What's New.

Beyond that, the release is essentially mechanical and pretty well
documented (though the new wrinkle this time around is uploading files
to PyPI since pip is no longer trusting of files on SourceForge).

Mike

--
                    _
>\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
> >>(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |

http://www.droettboom.com

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

--
Thomas Caswell
tcaswell@...149...