2017-05-08 phone call

Folks,

Sorry for being so late on getting this out.

My self, Eric Firing and Ryan May.

- Went over the last few issues for 2.0.2 (which has subsequently been
tagged and released)
- discussed future release plans

Going forward, we do not plan to do a 2.0.3 (unless we find another truly
egregious regression) and plan to get a 2.1 RC in time for scipy (July).

This leaves the question of what to do with our milestones as we have 600+
things tagged for 2.0.3. In general, we need some way to differentiate
'This must go in for this release X.Y.Z' and 'This can / sholud be merged /
backported for release X.Y.Z'.

Maybe we should have a 'next minor' and 'next patch' milestones to hold the
'can/should' issues / PRs and use the explicitly numbered milestones for
the 'must' category?

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

Folks,

Sorry for being so late on getting this out.

My self, Eric Firing and Ryan May.

- Went over the last few issues for 2.0.2 (which has subsequently been
tagged and released)
- discussed future release plans

Going forward, we do not plan to do a 2.0.3 (unless we find another truly
egregious regression) and plan to get a 2.1 RC in time for scipy (July).

This leaves the question of what to do with our milestones as we have 600+
things tagged for 2.0.3. In general, we need some way to differentiate
'This must go in for this release X.Y.Z' and 'This can / sholud be merged /
backported for release X.Y.Z'.

Maybe we should have a 'next minor' and 'next patch' milestones to hold
the 'can/should' issues / PRs and use the explicitly numbered milestones
for the 'must' category?

How about labels for priority or importance instead of milestones? I really
don't like the idea of multiple concurrent milestones for a single release.

Ryan

--

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

ยทยทยท

On Sat, May 13, 2017 at 1:46 PM Thomas Caswell <tcaswell at gmail.com> wrote: