2.2 LTS backport policy

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180308/48a13545/attachment.html>

That's a sound approach, IMO.
-paul

···

On Thu, Mar 8, 2018 at 8:40 AM, Thomas Caswell <tcaswell at gmail.com> 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
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/20180308/b89329e1/attachment.html>

Seems generally reasonable to me.

Ryan

···

On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <tcaswell at gmail.com> 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
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

--
Ryan May
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180308/bb48668e/attachment.html>

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 <rmay31 at gmail.com> wrote:

Seems generally reasonable to me.

Ryan

On Thu, Mar 8, 2018 at 9:40 AM, Thomas Caswell <tcaswell at gmail.com> 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
Matplotlib-devel at python.org
https://mail.python.org/mailman/listinfo/matplotlib-devel

--
Ryan May

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