[Matplotlib-devel] long term schedule

[OceanWolf]

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>