long term schedule

Hey folks,

For the feed back I think the consensus is go with the proprosed schedule,
but commit to not breaking any APIs in 3.0.

2016-09/10 : 2.1
  what we have on master is probably good enough for a release already but
target
  - traitlets
  - the gui overhaul
  if we miss them, tag in late september anyway

2017-07 : 2.2 LTS
- last feature release with 2.7 support
- critical bug fixes on mpl 2.2.x branch until 2020
- solicit a dedicated py2.7 maintainer

2018-07 : 3.0
  - only support py3.4+
  - do not break back-compatible API

There has been no protest to publishing this on the pyhon3 statement web
page (and this is already public) so I will ask them to include us in the
list.

Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160520/5be7d41c/attachment.html>

How does "not breaking any APIs" influence the deprecation and removal timeline for the gui overhaul?? I thought perhaps deprecate in 2.2 and remove in 3.0?? Or does such a timeline go too fast?

···

From: Thomas Caswell <tcaswell at gmail.com>
To: matplotlib development list <matplotlib-devel at python.org>
Sent: Friday, 20 May 2016, 19:31
Subject: [Matplotlib-devel] long term schedule
   
Hey folks,
For the feed back I think the consensus is go with the proprosed schedule, but commit to not breaking any APIs in 3.0.

2016-09/10 : 2.1? what we have on master is probably good enough for a release already buttarget? - traitlets? - the gui overhaul? if we miss them, tag in late september anyway
2017-07 : 2.2 LTS?- last feature release with 2.7 support?- critical bug fixes on mpl 2.2.x branch until 2020?- solicit a dedicated py2.7 maintainer
2018-07 : 3.0? - only support py3.4+? - do not break back-compatible API
There has been no protest to publishing this on the pyhon3 statement web page (and this is already public) so I will ask them to include us in the list.
Tom
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160520/0edfb264/attachment.html>

Along the same lines, I think this might be too much of a straitjacket.
This is a vague sense of unease--I don't have a specific example. It
just seems like having to keep *everything* 100% intact until a 4.0
release in 2019 or 2020 might be going too far. This is especially so
since "API" is not so well defined. Does every attribute lacking a
leading underscore have to be maintained for several more years? Maybe
"API" needs a qualifier, like "major API".

Eric

···

On 2016/05/20 8:18 AM, OceanWolf via Matplotlib-devel wrote:

How does "not breaking any APIs" influence the deprecation and removal
timeline for the gui overhaul? I thought perhaps deprecate in 2.2 and
remove in 3.0? Or does such a timeline go too fast?

I should have said "no more api breakage than normal between point
releases".

We do not want to get in to a situation where major down stream packages
that is mpl (yt, skimage, pandas, etc) pin a maximum matplotlib version.

Tom

···

On Fri, May 20, 2016, 14:32 Eric Firing <efiring at hawaii.edu> wrote:

On 2016/05/20 8:18 AM, OceanWolf via Matplotlib-devel wrote:
> How does "not breaking any APIs" influence the deprecation and removal
> timeline for the gui overhaul? I thought perhaps deprecate in 2.2 and
> remove in 3.0? Or does such a timeline go too fast?
>
Along the same lines, I think this might be too much of a straitjacket.
This is a vague sense of unease--I don't have a specific example. It
just seems like having to keep *everything* 100% intact until a 4.0
release in 2019 or 2020 might be going too far. This is especially so
since "API" is not so well defined. Does every attribute lacking a
leading underscore have to be maintained for several more years? Maybe
"API" needs a qualifier, like "major API".

Eric

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160520/b58c04cd/attachment-0001.html>