Mailman 3 May 2018 - scikit-image

Re: [scikit-image] Releasing 0.14
by Egor Panfilov 23 May '18

23 May '18

Hi Juan, I'm in GMT+3. Today I'm going to finish the review of 0.14 milestone, prepare the release notes, and go for a dry-run of the release. Please, let me which tool would you like to use for the interactive chat on the potential questions. As for flood fill, if there is an urgent need in the algorithm for the upcoming tutorial sessions, and if Josh has everything already implemented, I think, it could easily go to `skimage.future` right away (or with 0.14.1, of course). We can then re-iterate on the API, and improve the implementation in other ways. Regards, Egor вт, 22 мая 2018 г., 5:11 Juan Nunez-Iglesias <jni(a)fastmail.com>: > Hello everyone, and thanks for the robust response! =) > > Josh, there is no urgency in getting flood fill into 0.14.0. It can go > into 0.14.1 equally well. Actually my goal is for 0.14.0 to be out before > next week's sprint *and* possibly to do generic flood-fill with > LowLevelCallable support during the sprint. These goals are mutually > exclusive with having flood fill in 0.14.0. And, incidentally, I would > think that nD basic flood-fill should be as easy as 2D given the > offsets_to_neighbors functions in watershed/the local_maxima PR. I would > *very* much prefer to have an nD flood-fill from the beginning. What is > "basic" flood fill btw? Same value as starting index? > > Egor, awesome that you can do the release. As to the timing, given > Stéfan's suggestion that we should have a round of review of the release > notes before the actual release, *and* that I am flying MEL-SFO on > Thursday, do you think we could do this today or tomorrow (Wednesday)? > Today would be much less hectic for me, but tomorrow would be ok. What is > your timezone btw? > > Stéfan, as to pre-releases, it is a good idea, but I would target that for > 0.15 or maybe even 0.14.1. I don't want to change the release process right > this second. > > Onwards and upwards! > > Juan. > _______________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image >

1 0

Submit a BoF at SciPy 2018, before June 27!
by Nelle Varoquaux 23 May '18

23 May '18

Dear all, (apologies for the cross-posting) The SciPy conference would like to invite you to submit proposals for Birds of a Feather (BOF) sessions at this year's SciPy! BOFs usually include short presentations by a panel and a moderator with the bulk of the time spent opening up the discussion to everyone in attendance. BoF topics can be of general interest, such as state-of-the-project BoFs, or based on the themes of the conference and the mini-symposia topics. Please submit your proposals by June 27 here: https://scipy2018.scipy. org/ehome/299527/648142/ Past SciPy conferences have had a large variety of BOF sessions, including topics on Reproducibility, Jupyter Notebooks, Distributed Computing, Geospatial Packages in Python, Teaching Scientific Computing with Python, Python and Finance, NumFOCUS, Python in Astronomy, Collaborating and Contributing in Open Science, Education, and a Matplotlib Enhancement Proposal Discussion. Generally, if there is a topic where you think a number of people at SciPy will be interested, you should propose it! Thanks, Jess & Nelle

1 0

Releasing 0.14
by Juan Nunez-Iglesias 22 May '18

22 May '18

Hello list, Tomorrow I am going to do one last pass at the 0.14 milestone and then release 0.14. As a reminder, 0.14.x will be a LTS release, the last skimage version compatible with Python 2.7, and it will receive important backports (bug fixes, critical performance improvements, and maybe even a new feature or two, based principally on community demand). Given how long we have been planning this release, I think we have reached the point where we should release what we have rather than hold it up for every last PR that we want in it. Many users have requested this release, and it is particularly important for our Windows users that may not have a complete developer toolchain to build from source, and have a difficult time accessing the features that have made it onto master in the past year. If you have any strong objections to pushing this out, please voice them now. Egor, you twice mentioned wanting to be release manager for this release. (Sorry that I was not more available to help on those occasions.) I’m happy to let you do this one if you still want to, but I’m also happy to do it myself. Let me know your preference. Thanks, Juan.

3 3

Fwd: MeeseeksDev bot
by Stefan van der Walt 22 May '18

22 May '18

Hi all developers, As we get ready to release 0.14, a reminder of the MeeseeksBox bot, which can help backport patches and assist with other administrative tasks. See attached instructions for backports. Best regards, Stéfan

1 0

Re: [scikit-image] Releasing 0.14
by Josh Warner 22 May '18

22 May '18

I would really, really like for us to have flood fill in this release. Particularly if it's going to be the last with some backwards compatibility. It would help with tutorials - actually the panorama tutorial is now broken without it without an acceptable workaround other than shipping a flood fill with the tutorial - and is so basic yet essential we have very little excuse to still be lacking this. There was discussion about implementing it recently, but I think that's still pending. I will make a PR with a basic, 2D uint8 flood fill in Cythob by tomorrow. There are definitely improvements that can be made in speed & generalization, but let's at least have the very basic algorithm in 0.14 so we can backport improvements. Josh On Mon, May 21, 2018, 09:46 Egor Panfilov <egor.v.panfilov(a)gmail.com> wrote: > Hi Juan, > > Yes, I'm still willing to be a release manager. > I agree with you that, despite having a moderate list of open issues > [softly] scheduled for 0.14, we should go ahead and make a release. The > master branch holds a ton of fascinating additions, and it is way far ahead > of 0.13.1 already. > > My suggestion would be to wait couple of days so that the maintainers > could review 0.14 milestone and catch up with the issues they consider > critical for 0.14. Once everything is set, we (I might need your > assistance, @jni :)) can make a release (this Thursday or Friday). > > Regards, > Egor > > пн, 21 мая 2018 г. в 15:57, Juan Nunez-Iglesias <jni(a)fastmail.com>: > >> Hello list, >> >> Tomorrow I am going to do one last pass at the 0.14 milestone and then >> release 0.14. As a reminder, 0.14.x will be a LTS release, the last skimage >> version compatible with Python 2.7, and it will receive important backports >> (bug fixes, critical performance improvements, and maybe even a new feature >> or two, based principally on community demand). >> >> Given how long we have been planning this release, I think we have >> reached the point where we should release what we have rather than hold it >> up for every last PR that we want in it. Many users have requested this >> release, and it is particularly important for our Windows users that may >> not have a complete developer toolchain to build from source, and have a >> difficult time accessing the features that have made it onto master in the >> past year. >> >> If you have any strong objections to pushing this out, please voice them >> now. >> >> Egor, you twice mentioned wanting to be release manager for this release. >> (Sorry that I was not more available to help on those occasions.) I’m happy >> to let you do this one if you still want to, but I’m also happy to do it >> myself. Let me know your preference. >> >> Thanks, >> >> Juan. >> >> _______________________________________________ >> scikit-image mailing list >> scikit-image(a)python.org >> https://mail.python.org/mailman/listinfo/scikit-image >> > _______________________________________________ > scikit-image mailing list > scikit-image(a)python.org > https://mail.python.org/mailman/listinfo/scikit-image >

1 0

Fwd: scikit-image sprint next week!
by Juan Nunez-Iglesias 21 May '18

21 May '18

Hi Everyone, As some of you might already know, Nelle Varoquaux has organised a joint dask, scikit-learn, and scikit-image sprint at UC Berkeley from May 28 to June 1. (Mon-Fri) If you would like to participate remotely, we will be monitoring the gitter chat [1]. It might get a bit noisy in there, in which case we might try to move discussions to separate chat rooms for individual issues. If you happen to be in or close to Berkeley, you are of course welcome to join us in person! Just email me privately for instructions. As to *what* we will work on during the sprint, I have made an issue [2] summarising some early ideas Emma, Stéfan, and myself quickly volleyed over email. Please use this issue to discuss any other ideas or wishlists you might have for the sprint. .. [1]: https://gitter.im/scikit-image/scikit-image .. [2]: https://github.com/scikit-image/scikit-image/issues/3086 Looking forward to a productive week! Juan.

1 0