[Matplotlib-devel] supported python versions

[Daniele Nicolodi]

On 27/09/15 21:58, Thomas Caswell wrote:
> To follow up the following is the matrix of possible 'supported python'
> tables for the next few releases:

Unfortunately, this is only a partial matrix, and as Nathaniel pointed
out is not self-consistent: supported means that we fix bugs and release
patched version, if the patched version does not maintain compatibility
promises we are breaking support.

> A
> 
>    v1.5.0 is supported in 2.7, 3.4, 3.5 and is known to work with 2.6,
> and 3.3
>    v2.0.0 is supported in 2.7, 3.4, 3.5 and is known to work with 2.6,
> and 3.3
>    v2.0.1 is supported in 2.7, 3.4, 3.5 and is known to work with 3.3
> 
> cons: 'known to work with' is controversial/confusing, may pick up
> incompatibilities on a micro release.
> pros: simple on dev side, lets 2.6/3.3 semi-gracefully fall away.
> 
> B
>    v1.5.0 is supported in 2.7, 3.4, 3.5
>    v2.0.0 is supported in 2.7, 3.4, 3.5 
>    v2.0.1 is supported in 2.7, 3.4, 3.5 
> 
> cons: under-documents the 'real' support, drops 2.6 without much warning
> pros: simple on dev side
> 
> C
>    v1.5.0 is supported in 2.6, 2.7, 3.3, 3.4, 3.5
>    v2.0.0 is supported in 2.7, 3.4, 3.5 
>    v2.0.1 is supported in 2.7, 3.4, 3.5 
> 
> cons: muddies the water on 2.0 being 'style only', under documents where
> 2.0 will work, implicitly commits us to a 2.6 compatible 1.5.x series
> but I do not anticipate us actually doing a 1.5.x series.
> 
> My preference is A > C > B.

Usually people votes on alternative proposals once all the different
options are laid down and agreed upon. I would like to add:

D
     v1.5 is supported in 2.6, 2.7, 3.3, 3.4, 3.5 (status quo)
     v2.0 is supported in 2.6, 2.7, 3.3, 3.4, 3.5 (status quo)
     v2.1 is supported in 2.7, 3.4, 3.5

This is with the assumption that v1.5.x bugfix releases happen only if
mayor bugs that make it unusable are found in 1.5, and v2.0.x bugfix
releases happen until 2.1 is released. 2.0 differs from 1.5 only for the
default styles, that (I believe) can be set to the 1.5 ones via
configuration parameters, thus the ones that require extended support
for the 1.5 series can simply grab the 2.0.x releases and modify the
default settings.

pros: keeps promises, easy to communicate and understand
cons: one bugfix only branch needs to be maintained


Cheers,
Daniele