[SciPy-Dev] Proposed SciPy 1.4.0 Release Schedule

Tyler Reddy tyler.je.reddy at gmail.com
Tue Nov 12 11:30:37 EST 2019


Down to 12 open PRs with 1.4.0 milestone--getting closer!

On Sat, 9 Nov 2019 at 21:40, Tyler Reddy <tyler.je.reddy at gmail.com> wrote:

> We currently sit at 31 open PRs and 20 open issues with 1.4.0 milestone.
>
> That's a substantial drop in PRs but a rise in issues since the last
> accounting. Things got
> a little hectic with Python 3.8 for 1.3.2, but hopefully the wheels stuff
> is in good shape
> for 1.4.x series now.
>
> Branching in about 5 days is ambitious, but let's aim to stay reasonably
> on track if possible.
>
> On Mon, 21 Oct 2019 at 13:39, Matt Haberland <haberland at ucla.edu> wrote:
>
>> Re: 1.2.3 release, I did get a request in gh-10915
>> <https://github.com/scipy/scipy/issues/10915> for gh-10498
>> <https://github.com/scipy/scipy/pull/10498> to be backported to 1.2.
>>
>> On Mon, Oct 21, 2019 at 8:47 AM Ralf Gommers <ralf.gommers at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Sat, Oct 19, 2019 at 12:24 AM Tyler Reddy <tyler.je.reddy at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> SciPy 1.3.0 was released May 17 (5 months ago), and I think we'd like
>>>> to keep a roughly biannual release cadence.
>>>>
>>>> I'd like to propose the following schedule for 1.4.0:
>>>> - November 14: branch 1.4.x
>>>> - November 17: rc1
>>>> - December 1: rc2 (if needed)
>>>> - December 10: final release
>>>>
>>>
>>> Sounds good to me.
>>>
>>>>
>>>> The arrival of Python 3.8 and simultaneous responsibility to get at
>>>> least one more 1.2.x LTS Python 2.7 release out the door means things will
>>>> probably be busy on the release front until 2020.
>>>>
>>>
>>> True. I think supporting 3.8 is fairly high-prio, there's a lot of
>>> demand for it. Doing a 1.3.2 release that supports it would make sense I
>>> guess.
>>>
>>> There don't seem to be any new commits on the 1.2.x branch nor urgent
>>> Python 2.7 fixes that need to go out. So do we need a 1.2.3 release?
>>>
>>> Cheers,
>>> Ralf
>>>
>>>
>>>
>>>> As always, it is a good idea to start tagging things that should be in
>>>> 1.4.0 & please do help with reviewing PRs/issues that are tagged--current
>>>> counts are:
>>>>
>>>> - PRs: 40 open with 1.4.0 milestone
>>>> - issues: 17 open with 1.4.0 milestone
>>>>
>>>> While helping with that, also great if the release notes wiki is
>>>> updated for appropriate changes:
>>>> https://github.com/scipy/scipy/wiki/Release-note-entries-for-SciPy-1.4.0
>>>>
>>>> Curating those final notes can be painful if the wiki isn't updated.
>>>>
>>>> Thoughts/objections for the schedule?
>>>>
>>>> Best wishes,
>>>> Tyler
>>>> _______________________________________________
>>>> SciPy-Dev mailing list
>>>> SciPy-Dev at python.org
>>>> https://mail.python.org/mailman/listinfo/scipy-dev
>>>>
>>> _______________________________________________
>>> SciPy-Dev mailing list
>>> SciPy-Dev at python.org
>>> https://mail.python.org/mailman/listinfo/scipy-dev
>>>
>>
>>
>> --
>> Matt Haberland
>> Assistant Adjunct Professor in the Program in Computing
>> Department of Mathematics
>> 6617A Math Sciences Building, UCLA
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20191112/ac79c285/attachment.html>


More information about the SciPy-Dev mailing list