[SciPy-Dev] Proposed 1.6.0 Release Schedule

Romain Jacob jacobr at ethz.ch
Wed Dec 2 07:27:17 EST 2020


Hi everyone,

> There are two stats PRs left, but I believe the "bandwidth" is a bit 
> better with core devs reviewing those, and they could always be bumped 
> I think.

Could this stat PR (https://github.com/scipy/scipy/pull/12680) be 
considered for the 1.6.0 milestone?

I made the suggested changes and there has not been any further comments 
in a while; so, just wandering :-) If not, it would be cool to know what 
else I am expected to provide to conclude PR.

Cheers,
-- 
Romain

>
> There are two "dueling" optimize PRs:
> https://github.com/scipy/scipy/pull/13143
> https://github.com/scipy/scipy/pull/12889
>
> So, maybe we are within a single digit number of days from branching 
> 1.6.0 now?
>
> Many thanks to several core devs (of NumPy and SciPy projects) for 
> assisting with efforts to migrate off Travis CI due to the recent 
> restrictions imposed there.
>
> Best wishes,
> Tyler
>
> On Sun, 22 Nov 2020 at 13:24, Ilhan Polat <ilhanpolat at gmail.com 
> <mailto:ilhanpolat at gmail.com>> wrote:
>
>     I don't mean to disrupt your flow but please feel free to assign
>     some dummy work to us if need be. Given the pandemic and all, it's
>     much easier to get overwhelmed with stuff these days.
>
>     On Sun, Nov 22, 2020 at 8:14 PM Tyler Reddy
>     <tyler.je.reddy at gmail.com <mailto:tyler.je.reddy at gmail.com>> wrote:
>
>         We may need to delay the release a bit. Mostly because of the
>         disruption to the Travis CI service (not running/credit
>         limit), which would probably affect the wheels repo before a
>         final release too. I've tried to move a few of the simpler
>         jobs to Azure, but probably running out of steam for that
>         effort this weekend.
>
>         I've reached out to Travis CI support and asked NumFOCUS
>         informally what we might do here. A few kind folks have
>         offered to chip in to keep the CI running short-term. Let's
>         see what happens with the former inquiries first?
>
>         Open PR count is currently 26 for the 1.6.0 milestone, though
>         probably a few more I can bump to next milestone.
>
>         Best wishes,
>         Tyler
>
>
>
>         On Mon, 9 Nov 2020 at 00:12, Evgeni Burovski
>         <evgeny.burovskiy at gmail.com
>         <mailto:evgeny.burovskiy at gmail.com>> wrote:
>
>             How about shifting the release towards January then?
>
>             пн, 9 нояб. 2020 г., 1:43 Tyler Reddy
>             <tyler.je.reddy at gmail.com <mailto:tyler.je.reddy at gmail.com>>:
>
>                 Ok, I'll bump it by a week then.
>
>                   * November 24: branch maintenance/1.6.x
>                   * November 27: rc1
>                   * December 8: rc2 (if needed)
>                   * December 17: final release
>
>                 I was trying to avoid the overlap with US Thanksgiving
>                 and a final release in late December near Winter
>                 Break, but I'll manage.
>                 Tyler
>
>                 On Sun, 8 Nov 2020 at 14:53, Ralf Gommers
>                 <ralf.gommers at gmail.com
>                 <mailto:ralf.gommers at gmail.com>> wrote:
>
>
>
>                     On Sat, Nov 7, 2020 at 10:48 PM Tyler Reddy
>                     <tyler.je.reddy at gmail.com
>                     <mailto:tyler.je.reddy at gmail.com>> wrote:
>
>                         Hi,
>
>                         SciPy 1.5.0 was released June 21 (~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.6.0:
>                         - November 17: branch 1.6.x
>                         - November 20: rc1
>                         - December 1: rc2 (if needed)
>                         - December 10: final release
>
>                         As always, it is a good idea to start tagging
>                         things that should be in 1.6.0 & please do
>                         help with reviewing PRs/issues that are
>                         tagged--current counts are:
>
>                         - PRs: 45 open with 1.6.0 milestone
>                         - issues: 25 open with 1.6.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.6.0
>
>
>                         Thoughts/objections for the schedule?
>
>
>
>                     It does seem like there's a lot of PRs open,
>                     having only one weekend left seems optimistic. The
>                     majority can be bumped to 1.7.0, but there's a bit
>                     of a backlog of nice PRs that have been ready for
>                     a while and would be nice to get in. For example:
>
>                     - KDTree/cKDTree feature parity:
>                     https://github.com/scipy/scipy/pull/12852
>                     - HiGHS solver as linprog method:
>                     https://github.com/scipy/scipy/pull/12043
>                     - Balanced cut tree:
>                     https://github.com/scipy/scipy/pull/10730
>                     - Andrew's set of optimize PRs that he brought up
>                     on the mailing list recently
>                     - Greg's set of ndimage PRs, complex kernels and
>                     the boundary handling ones (#12725, #12767, #12776)
>
>                     If it's possible, given your time constraints, to
>                     bump the schedule by one week then that may be useful.
>
>                     Cheers,
>                     Ralf
>
>
>
>
>                     _______________________________________________
>                     SciPy-Dev mailing list
>                     SciPy-Dev at python.org <mailto:SciPy-Dev at python.org>
>                     https://mail.python.org/mailman/listinfo/scipy-dev
>
>                 _______________________________________________
>                 SciPy-Dev mailing list
>                 SciPy-Dev at python.org <mailto:SciPy-Dev at python.org>
>                 https://mail.python.org/mailman/listinfo/scipy-dev
>
>             _______________________________________________
>             SciPy-Dev mailing list
>             SciPy-Dev at python.org <mailto:SciPy-Dev at python.org>
>             https://mail.python.org/mailman/listinfo/scipy-dev
>
>         _______________________________________________
>         SciPy-Dev mailing list
>         SciPy-Dev at python.org <mailto:SciPy-Dev at python.org>
>         https://mail.python.org/mailman/listinfo/scipy-dev
>
>     _______________________________________________
>     SciPy-Dev mailing list
>     SciPy-Dev at python.org <mailto: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
-- 
Romain Jacob
Postdoctoral Researcher
ETH Zurich - Networked Systems Group (NSG)
www.romainjacob.net <https://www.romainjacob.net/>
@RJacobPartner <https://twitter.com/RJacobPartner>
Gloriastrasse 35, ETZ G78
8092 Zurich
+41 7 68 16 88 22
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/scipy-dev/attachments/20201202/aac2370c/attachment-0001.html>


More information about the SciPy-Dev mailing list