[Matplotlib-devel] 2.2 LTS backport policy

[tcaswell]

Folks,

I propose the following criteria for backporting PRs to the 2.2.x branch.  We always will backport 

 - critical bug fixes (segfault, failure to import, things that the user can not work around)

 - fixes for regressions against 2.0 or 2.1 

Everything else (regressions against 1.x versions, bugs/api inconsistencies the user can work around in their code) are on a case-by-case basis, should be low-risk, and need someone to advocate for and shepherd through the backport.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

[Paul Hobson-2]

That's a sound approach, IMO.

-paul

On Thu, Mar 8, 2018 at 8:40 AM, Thomas Caswell <[hidden email]> wrote:

Folks,

I propose the following criteria for backporting PRs to the 2.2.x branch.  We always will backport 

 - critical bug fixes (segfault, failure to import, things that the user can not work around)

 - fixes for regressions against 2.0 or 2.1 

Everything else (regressions against 1.x versions, bugs/api inconsistencies the user can work around in their code) are on a case-by-case basis, should be low-risk, and need someone to advocate for and shepherd through the backport.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

[Ryan May-3]

Seems generally reasonable to me.

Ryan

On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <[hidden email]> wrote:

Folks,

I propose the following criteria for backporting PRs to the 2.2.x branch.  We always will backport 

 - critical bug fixes (segfault, failure to import, things that the user can not work around)

 - fixes for regressions against 2.0 or 2.1 

Everything else (regressions against 1.x versions, bugs/api inconsistencies the user can work around in their code) are on a case-by-case basis, should be low-risk, and need someone to advocate for and shepherd through the backport.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

--

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

[tcaswell]

Put this into a PR to get it into the docs https://github.com/matplotlib/matplotlib/pull/10822

Tom

On Thu, Mar 8, 2018 at 1:18 PM Ryan May <[hidden email]> wrote:

Seems generally reasonable to me.

Ryan

On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <[hidden email]> wrote:

Folks,

I propose the following criteria for backporting PRs to the 2.2.x branch.  We always will backport 

 - critical bug fixes (segfault, failure to import, things that the user can not work around)

 - fixes for regressions against 2.0 or 2.1 

Everything else (regressions against 1.x versions, bugs/api inconsistencies the user can work around in their code) are on a case-by-case basis, should be low-risk, and need someone to advocate for and shepherd through the backport.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel

--

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel