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.
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 Matplotlib-devel Info Page
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 Matplotlib-devel Info Page
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 Matplotlib-devel Info Page