Has there been talk about a release? We've long-since merged the big changes to CV. Among the things seeming unfinished there is that where `cv` is available, `fit` should also support a `labels` parameter. That's not available in RFECV etc. There are some other nice features in the next release too, and I think we should move towards putting them out there. Should we start tagging issues in and out of the 0.18 milestone?
Hi Joel. I totally agree. I've been still busy with the book and haven't caught up with all the developments yet. There is probably a whole bunch of bug fixes that we need to do, though, and maybe some other API changes / deprecations. I'll be more helpful in two weeks, when my book is submitted and scipy is over. Best, Andy On 07/04/2016 06:49 PM, Joel Nothman wrote:
Has there been talk about a release?
We've long-since merged the big changes to CV. Among the things seeming unfinished there is that where `cv` is available, `fit` should also support a `labels` parameter. That's not available in RFECV etc.
There are some other nice features in the next release too, and I think we should move towards putting them out there. Should we start tagging issues in and out of the 0.18 milestone?
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
I knew the book was holding things up, but I thought I'd check in. On 7 July 2016 at 04:26, Andreas Mueller <t3kcit@gmail.com> wrote:
Hi Joel. I totally agree. I've been still busy with the book and haven't caught up with all the developments yet. There is probably a whole bunch of bug fixes that we need to do, though, and maybe some other API changes / deprecations.
I'll be more helpful in two weeks, when my book is submitted and scipy is over.
Best, Andy
On 07/04/2016 06:49 PM, Joel Nothman wrote:
Has there been talk about a release?
We've long-since merged the big changes to CV. Among the things seeming unfinished there is that where `cv` is available, `fit` should also support a `labels` parameter. That's not available in RFECV etc.
There are some other nice features in the next release too, and I think we should move towards putting them out there. Should we start tagging issues in and out of the 0.18 milestone?
_______________________________________________ scikit-learn mailing listscikit-learn@python.orghttps://mail.python.org/mailman/listinfo/scikit-learn
_______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
Sorry for the late reply, Before working on this release I would like to automate the wheel generation process (for the release wheels) in a single repo that will generate wheels for linux, osx and windows based on https://github.com/matthew-brett/multibuild I plan to put that repo under https://github.com/scikit-learn/scikit-learn-wheels and deprecate https://github.com/MacPython/scikit-learn-wheels that we used for the OSX wheels. There is also some issue triaging to do, it would be great to identify blocker bugs that we would like to get fixed before releasing 0.18. We can aim to do a beta mid-August and the final release after euroscipy (first week of September). -- Olivier
Hi, On Mon, Jul 25, 2016 at 12:54 PM, Olivier Grisel <olivier.grisel@ensta.org> wrote:
Sorry for the late reply,
Before working on this release I would like to automate the wheel generation process (for the release wheels) in a single repo that will generate wheels for linux, osx and windows based on https://github.com/matthew-brett/multibuild
I plan to put that repo under https://github.com/scikit-learn/scikit-learn-wheels and deprecate https://github.com/MacPython/scikit-learn-wheels that we used for the OSX wheels.
Actually, sorry, I already switched to multibuild for the MacPython repo, so it already builds manylinux wheels. There's a single test failure now on OSX because I added 32-bit tests to the OSX test command : https://travis-ci.org/MacPython/scikit-learn-wheels/builds/146137997 Obviously feel totally free to move the MacPython repo to scikit-learn if you'd prefer. Cheers, Matthew
Hi Olivier / all Let me know if I can help with the builds. I'm gonna start reviews and triaging and tagging this week. Mid August sounds good for a beta / RC. It would be great if we could release in September, as that is when The Book (aka my past year) is scheduled to come out (I finished it last week). The Book uses model_selection, so having the release out before the book would be good. Andy On 07/25/2016 07:54 AM, Olivier Grisel wrote:
Sorry for the late reply,
Before working on this release I would like to automate the wheel generation process (for the release wheels) in a single repo that will generate wheels for linux, osx and windows based on https://github.com/matthew-brett/multibuild
I plan to put that repo under https://github.com/scikit-learn/scikit-learn-wheels and deprecate https://github.com/MacPython/scikit-learn-wheels that we used for the OSX wheels.
There is also some issue triaging to do, it would be great to identify blocker bugs that we would like to get fixed before releasing 0.18.
We can aim to do a beta mid-August and the final release after euroscipy (first week of September).
Thanks Matthew I had not realized. I will add an appveyor config there with a dedicated `sklearn-wheels` account so that we don't wait for the `sklearn-ci` jobs when we are building the release wheels. -- Olivier
Ok I fixed all the 32 bit Linux & OSX build issues in scikit-learn master and all wheels builds are green with the multibuild setup: https://travis-ci.org/MacPython/scikit-learn-wheels Matthew: would you be interested in having the multibuild repo extended to also include appveyor configration files or do you think it's better to let projects owner do their own appveyor config by themselves? -- Olivier
Definitely interested ! On 17 Aug 2016 07:44, "Olivier Grisel" <olivier.grisel@ensta.org> wrote:
Ok I fixed all the 32 bit Linux & OSX build issues in scikit-learn master and all wheels builds are green with the multibuild setup:
https://travis-ci.org/MacPython/scikit-learn-wheels
Matthew: would you be interested in having the multibuild repo extended to also include appveyor configration files or do you think it's better to let projects owner do their own appveyor config by themselves?
-- Olivier _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
I vote we push back the release a bit (two weeks?). I had unexpected things come up that ate a bunch of my time. On 07/25/2016 03:53 PM, Andreas Mueller wrote:
Hi Olivier / all Let me know if I can help with the builds. I'm gonna start reviews and triaging and tagging this week. Mid August sounds good for a beta / RC.
It would be great if we could release in September, as that is when The Book (aka my past year) is scheduled to come out (I finished it last week). The Book uses model_selection, so having the release out before the book would be good.
Andy
On 07/25/2016 07:54 AM, Olivier Grisel wrote:
Sorry for the late reply,
Before working on this release I would like to automate the wheel generation process (for the release wheels) in a single repo that will generate wheels for linux, osx and windows based on https://github.com/matthew-brett/multibuild
I plan to put that repo under https://github.com/scikit-learn/scikit-learn-wheels and deprecate https://github.com/MacPython/scikit-learn-wheels that we used for the OSX wheels.
There is also some issue triaging to do, it would be great to identify blocker bugs that we would like to get fixed before releasing 0.18.
We can aim to do a beta mid-August and the final release after euroscipy (first week of September).
Many thanks ! Bertrand On 17/08/2016 16:43, Olivier Grisel wrote:
Ok I fixed all the 32 bit Linux & OSX build issues in scikit-learn master and all wheels builds are green with the multibuild setup:
https://travis-ci.org/MacPython/scikit-learn-wheels
Matthew: would you be interested in having the multibuild repo extended to also include appveyor configration files or do you think it's better to let projects owner do their own appveyor config by themselves?
Ok for pushing back. Let's try to work on the beta on the week after euroscipy if we can. At least all the annoying binary packaging issues are fixed (test failures for the linux and OSX 32 bit platforms) so the release process itself should hopefully be painless. -- Olivier
participants (5)
-
Andreas Mueller -
bthirion -
Joel Nothman -
Matthew Brett -
Olivier Grisel