Re: [SciPy-Dev] SciPy 1.1.0 release schedule
Dear All, #PR8203 is planned for 1.1.0 release. Few minors comments to address but very close to be merged according reviewers. I'll do my best to address them ASAP. Sylvain. -----Original Message----- From: SciPy-Dev [mailto:scipy-dev-bounces+sylvain.gubian=pmi.com@python.org] On Behalf Of scipy-dev-request@python.org Sent: mardi 10 avril 2018 23:16 To: scipy-dev@python.org Subject: SciPy-Dev Digest, Vol 174, Issue 10 Send SciPy-Dev mailing list submissions to scipy-dev@python.org To subscribe or unsubscribe via the World Wide Web, visit https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.python.org%2Fmailman%2Flistinfo%2Fscipy-dev&data=02%7C01%7Csylvain.gubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=qMVAKjIj6VyXGq%2BYbluHPuQnIBX8NNuExIZnJEcgfcU%3D&reserved=0 or, via email, send a message with subject or body 'help' to scipy-dev-request@python.org You can reach the person managing the list at scipy-dev-owner@python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of SciPy-Dev digest..." Today's Topics: 1. SciPy 1.1.0 release schedule (Pauli Virtanen) 2. Re: SciPy 1.1.0 release schedule (Mark Alexander Mikofski) 3. Re: SciPy 1.1.0 release schedule (Pauli Virtanen) 4. Re: SciPy 1.1.0 release schedule (Pauli Virtanen) 5. Re: SciPy 1.1.0 release schedule (Blair Azzopardi) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Apr 2018 21:39:02 +0200 From: Pauli Virtanen <pav@iki.fi> To: scipy-dev <scipy-dev@python.org> Subject: [SciPy-Dev] SciPy 1.1.0 release schedule Message-ID: <d52dd92bea7b25f2b5ff1d8ea42d7f8efc0bbbdb.camel@iki.fi> Content-Type: text/plain; charset="UTF-8" Hi, 2018-03-25 17:45 -0700, Ralf Gommers wrote:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit hub.com%2Fscipy%2Fscipy%2Fmilestone%2F34&data=02%7C01%7Csylvain.gubian %40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=gGcS%2BZH%2B%2FhauPHDbB4bHx%2B9K0ZtMMeBUgvEe7vO63wA%3D&reserved=0), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend. If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0. There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though. If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though). Best, Pauli -- ------------------------------ Message: 2 Date: Tue, 10 Apr 2018 20:12:37 +0000 From: Mark Alexander Mikofski <mikofski@berkeley.edu> To: SciPy Developers List <scipy-dev@python.org> Subject: Re: [SciPy-Dev] SciPy 1.1.0 release schedule Message-ID: <CAEqRcW1E6OnGWmHtZ3BNgGCMAePg7=YNweZ4-LwQOk=BRy7Utw@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Can PR #8357 please be considered for v1.1.0? It has been reviewed by several maintainers and contributors, it closes two issues, and has support of several users. Also it is tested, benchmarked, and documented. I believe I have addressed all comments from all reviewers, but please let me know if anyone has any more comments. Thanks so much! On Tue, Apr 10, 2018, 1:05 PM Pauli Virtanen <pav@iki.fi> wrote:
Hi,
2018-03-25 17:45 -0700, Ralf Gommers wrote:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg ithub.com%2Fscipy%2Fscipy%2Fmilestone%2F34&data=02%7C01%7Csylvain.gu bian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=gGcS%2BZH%2B%2FhauPHDbB4bHx%2B9K0ZtMMeBUgvEe7vO63wA%3D&reserved=0), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend.
If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0.
There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though.
If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though).
Best, Pauli
-- _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai l.python.org%2Fmailman%2Flistinfo%2Fscipy-dev&data=02%7C01%7Csylvain.g ubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068 ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=qMVAKjIj6VyXGq%2BYb luHPuQnIBX8NNuExIZnJEcgfcU%3D&reserved=0
-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.python.org%2Fpipermail%2Fscipy-dev%2Fattachments%2F20180410%2Fa304b33f%2Fattachment-0001.html&data=02%7C01%7Csylvain.gubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=puiVKaAv8yu56DoKNqcIYMt%2BUgdiFGk8gRFbhTzm9r8%3D&reserved=0> ------------------------------ Message: 3 Date: Tue, 10 Apr 2018 21:02:21 +0200 From: Pauli Virtanen <pav@iki.fi> To: scipy-dev@python.org Subject: Re: [SciPy-Dev] SciPy 1.1.0 release schedule Message-ID: <25564720afdc9f408862f670492b03d03e094696.camel@iki.fi> Content-Type: text/plain; charset="UTF-8" Hi, su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit hub.com%2Fscipy%2Fscipy%2Fmilestone%2F34&data=02%7C01%7Csylvain.gubian %40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=gGcS%2BZH%2B%2FhauPHDbB4bHx%2B9K0ZtMMeBUgvEe7vO63wA%3D&reserved=0), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend. If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0. There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though. If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though). Best, Pauli ------------------------------ Message: 4 Date: Tue, 10 Apr 2018 21:04:13 +0200 From: Pauli Virtanen <pav@iki.fi> To: scipy-dev@python.org Subject: Re: [SciPy-Dev] SciPy 1.1.0 release schedule Message-ID: <91b19d6380a8b8a68fdc8c2cda8d599a27b1d7f8.camel@iki.fi> Content-Type: text/plain; charset="UTF-8" Hi, su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit hub.com%2Fscipy%2Fscipy%2Fmilestone%2F34&data=02%7C01%7Csylvain.gubian %40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=gGcS%2BZH%2B%2FhauPHDbB4bHx%2B9K0ZtMMeBUgvEe7vO63wA%3D&reserved=0), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend. If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0. There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though. If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though). Best, Pauli ------------------------------ Message: 5 Date: Tue, 10 Apr 2018 22:15:33 +0100 From: Blair Azzopardi <blairuk@gmail.com> To: SciPy Developers List <scipy-dev@python.org> Subject: Re: [SciPy-Dev] SciPy 1.1.0 release schedule Message-ID: <CAAiKHotGpKi0uE8kG_eD8tKJ5qJ8p+x-E731WvRm114i9LJGcg@mail.gmail.com> Content-Type: text/plain; charset="utf-8" On 10 April 2018 at 20:04, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg ithub.com%2Fscipy%2Fscipy%2Fmilestone%2F34&data=02%7C01%7Csylvain.gu bian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=gGcS%2BZH%2B%2FhauPHDbB4bHx%2B9K0ZtMMeBUgvEe7vO63wA%3D&reserved=0), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend.
If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0.
There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though.
If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though).
Best, Pauli
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai l.python.org%2Fmailman%2Flistinfo%2Fscipy-dev&data=02%7C01%7Csylvain.g ubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068 ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=qMVAKjIj6VyXGq%2BYb luHPuQnIBX8NNuExIZnJEcgfcU%3D&reserved=0
Please can you consider merging PR #7374. It's already in the 1.1 milestone and I'd say it's pretty mature. The code offers 3 different ways of calculating stable pdf/cdfs all of which match samples provided by Nolan's public domain executable. It also offers parameter estimation using quantiles. Any further optimisations can be added in a later release. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.python.org%2Fpipermail%2Fscipy-dev%2Fattachments%2F20180410%2F93d9961a%2Fattachment.html&data=02%7C01%7Csylvain.gubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=YjdpODs8xQCMoJ%2BeVEpHYeRMzQW46mNxQGCyV0%2BRxjU%3D&reserved=0> ------------------------------ Subject: Digest Footer _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.python.org%2Fmailman%2Flistinfo%2Fscipy-dev&data=02%7C01%7Csylvain.gubian%40pmi.com%7C38a531959d654daaa84908d59f28752b%7C8b86a65e3c3a44068ac319a6b5cc52bc%7C0%7C0%7C636589918472558141&sdata=qMVAKjIj6VyXGq%2BYbluHPuQnIBX8NNuExIZnJEcgfcU%3D&reserved=0 ------------------------------ End of SciPy-Dev Digest, Vol 174, Issue 10 ******************************************
participants (1)
-
Gubian, Sylvain