Hi Tyler,

Thanks for managing the release again! This is a very important service for the SciPy community, and I'm very grateful!

Do you think we could try to add #9568 and #10052 assuming everyone agrees they are good?

thanks again!
Mark

On Sun, Apr 14, 2019 at 2:13 AM Ralf Gommers <ralf.gommers@gmail.com> wrote:


On Sun, Apr 14, 2019 at 12:27 AM Andrew Nelson <andyfaff@gmail.com> wrote:
Would it be possible to add 9990 and 10002 to 1.3.0, or is that too ambitious?

Those look like they're in good shape, should be doable. I've added them to the milestone. Tyler can always remove them again if we run out of time.


On Sun., 14 Apr. 2019, 07:20 Tyler Reddy, <tyler.je.reddy@gmail.com> wrote:
Hi All,

It is almost 4 months after the (slightly-delayed) 1.2.0 release on December 17/ 2018, so probably time to plan the 1.3.0 release. It would be a good idea to look over the PRs with a 1.3.0 milestone, and tag anything else that should have this milestone appropriately.

I'd like to propose the following schedule:

April 25: branch 1.3.x
April 28: rc1
May 11: rc2 (if needed)
May 20: final release

Thoughts?

That works for me. There may be a few items in https://github.com/scipy/scipy/milestone/37 that we won't get to, but the only real blocker (py37 build issue) on that list is ready to merge.

Cheers,
Ralf

_______________________________________________
SciPy-Dev mailing list
SciPy-Dev@python.org
https://mail.python.org/mailman/listinfo/scipy-dev


--
Mark Mikofski, PhD (2005)
Fiat Lux