[SciPy-Dev] Proposed 1.7.0 Release Schedule

Tyler Reddy tyler.je.reddy at gmail.com
Thu May 27 18:22:58 EDT 2021


I'll probably try to bump rc1 forward into early-mid next week because of
the long weekend here in the US. Maybe a few more backport/bug fixes will
trickle in as well.

Tyler

On Sun, 23 May 2021 at 18:17, Tyler Reddy <tyler.je.reddy at gmail.com> wrote:

> The draft release notes are ready for review/suggestions:
> https://github.com/scipy/scipy/pull/14118
>
> We have about 20 open PRs with milestone, which is a bit high this close
> to branching:
> https://github.com/scipy/scipy/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.7.0
>
> Quite a few are marked "approved." Some are likely to get bumped--I'm
> probably going to get a bit stricter tomorrow with bumping PRs that aren't
> on a clear trajectory to merging by Wednesday based on the comments or
> available expert reviewer bandwidth, CI issues that haven't been fixed, etc.
>
> Best wishes,
> Tyler
>
> On Sun, 16 May 2021 at 19:02, Andrew Nelson <andyfaff at gmail.com> wrote:
>
>> On Sun, 16 May 2021 at 22:14, Pamphile Roy <roy.pamphile at gmail.com>
>> wrote:
>>
>>> Regarding Optimize. It seems that lots of PRs and issues are pointing
>>> towards an overhaul of the module. My position would be to solve what can
>>> be solved for the release with open PRs and for the next release we should
>>> lay out a plan to evolve the module.
>>>
>>
>> It'd certainly be good for the number of active optimize maintainers to
>> increase, to tackle PRs and issues, etc.
>>
>> optimize is probably one of the most heavily used parts of scipy, that's
>> why it gets a lot of traffic on github. I think the module is probably in
>> not too bad a good shape. A review of outstanding issues would give an idea
>> of what types of issues are commonly experienced, it's not clear that a
>> large scale redesign would necessarily change anything.
>>
>> One thing I'm mainly interested in minimisations of scalar functions. I
>> had a desire to implement a class-based minimization system for those, but
>> I'm fairly convinced it would have to be developed outside scipy in a
>> spin-off project first.
>>
>>
>>
>>
>>> What do you think Andrew? Could we plan a specific meeting for that
>>> maybe?
>>>
>>> Cheers,
>>> Pamphile
>>>
>>
>> _______________________________________________
>> 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: <https://mail.python.org/pipermail/scipy-dev/attachments/20210527/2bef2b6b/attachment.html>


More information about the SciPy-Dev mailing list