From jni at fastmail.com Sun May 20 23:13:59 2018 From: jni at fastmail.com (Juan Nunez-Iglesias) Date: Mon, 21 May 2018 13:13:59 +1000 Subject: [scikit-image] Fwd: scikit-image sprint next week! In-Reply-To: References: Message-ID: <80e4020a-49dc-497a-9867-542d4378284b@Spark> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jni at fastmail.com Mon May 21 08:48:15 2018 From: jni at fastmail.com (Juan Nunez-Iglesias) Date: Mon, 21 May 2018 22:48:15 +1000 Subject: [scikit-image] Releasing 0.14 Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From egor.v.panfilov at gmail.com Mon May 21 12:41:28 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Mon, 21 May 2018 19:41:28 +0300 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: Message-ID: 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 : > 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 at python.org > https://mail.python.org/mailman/listinfo/scikit-image > -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvertrumpet999 at gmail.com Mon May 21 16:41:39 2018 From: silvertrumpet999 at gmail.com (Josh Warner) Date: Mon, 21 May 2018 13:41:39 -0700 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: Message-ID: 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 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 : > >> 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 at python.org >> https://mail.python.org/mailman/listinfo/scikit-image >> > _______________________________________________ > scikit-image mailing list > scikit-image at python.org > https://mail.python.org/mailman/listinfo/scikit-image > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefanv at berkeley.edu Mon May 21 18:50:26 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Mon, 21 May 2018 15:50:26 -0700 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: Message-ID: <20180521225026.4kelni5ibl5kg5xz@carbo> Hi Juan, On Mon, 21 May 2018 22:48:15 +1000, Juan Nunez-Iglesias wrote: > 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). Thanks for pushing ahead with this release! One request: that we add one review step to releases, which is that we (as a community) review the release notes. In the past, the release manager simply did these by themselves, but since it is so widely visible, additional eyes would help (to be clear, I'm referring mainly to my own past attempts to get this right!). Alternatively, we can try doing a pre-release, like NumPy and SciPy do. That is probably the safer and more responsible option, since we may also hear from other projects that have the "--pre" flag in their continuous integration setups. But it happens to also give us a chance to complete the above-mentioned release note review. Josh, we can still backport flood fill to a next point release later, especially if you can already submit it by tomorrow. Best regards, St?fan From stefanv at berkeley.edu Mon May 21 20:22:15 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Mon, 21 May 2018 17:22:15 -0700 Subject: [scikit-image] Fwd: MeeseeksDev bot Message-ID: <20180522002215.wsoid3mlghemd5me@carbo> 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 -------------- next part -------------- An embedded message was scrubbed... From: Stefan van der Walt Subject: MeeseeksDev bot Date: Thu, 15 Feb 2018 13:20:36 -0800 Size: 1159 URL: From jni at fastmail.com Mon May 21 22:11:46 2018 From: jni at fastmail.com (Juan Nunez-Iglesias) Date: Tue, 22 May 2018 12:11:46 +1000 Subject: [scikit-image] Releasing 0.14 In-Reply-To: <20180521225026.4kelni5ibl5kg5xz@carbo> References: <20180521225026.4kelni5ibl5kg5xz@carbo> Message-ID: <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.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. From nelle.varoquaux at gmail.com Tue May 22 19:01:55 2018 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Tue, 22 May 2018 16:01:55 -0700 Subject: [scikit-image] Submit a BoF at SciPy 2018, before June 27! Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From egor.v.panfilov at gmail.com Wed May 23 06:21:09 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Wed, 23 May 2018 13:21:09 +0300 Subject: [scikit-image] Releasing 0.14 In-Reply-To: <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> Message-ID: 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 : > 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 at python.org > https://mail.python.org/mailman/listinfo/scikit-image > -------------- next part -------------- An HTML attachment was scrubbed... URL: From egor.v.panfilov at gmail.com Wed May 23 11:08:10 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Wed, 23 May 2018 18:08:10 +0300 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> Message-ID: Hello list, I've started to prepare for the release, and have already created the release branch. If some of you would like to review the release notes, please, take a look at https://github.com/scikit-image/scikit-image/blob/v0.14.x/doc/release/release_0.14.rst . Concerning the development: I've rescheduled most of the issues and PR to the next milestones, leaving approx. 10 items for this release. @scikit-image/core, the remaining issues and PRs are pretty much finalized. Please, take a final look, and consider merging if everything looks OK. As discussed with Juan, I'm going to hold the release till tomorrow, waiting for your last-minute remarks and reviews. Thanks! Regards, Egor ??, 23 ??? 2018 ?. ? 13:21, Egor Panfilov : > 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 : > >> 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 at python.org >> https://mail.python.org/mailman/listinfo/scikit-image >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefanv at berkeley.edu Thu May 24 15:01:34 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Thu, 24 May 2018 12:01:34 -0700 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> Message-ID: <20180524190134.2azmi5c66ca4xuwl@carbo> Hi Egor, On Wed, 23 May 2018 18:08:10 +0300, Egor Panfilov wrote: > Hello list, > > I've started to prepare for the release, and have already created the > release branch. If some of you would like to review the release notes, > please, take a look at > https://github.com/scikit-image/scikit-image/blob/v0.14.x/doc/release/release_0.14.rst Woah, this is a big release! I'll leave some comments on the document directly, thanks. Best regards, St?fan From stefanv at berkeley.edu Thu May 24 15:02:46 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Thu, 24 May 2018 12:02:46 -0700 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> Message-ID: <20180524190246.qlpuqucnzeotngrp@carbo> On Wed, 23 May 2018 18:08:10 +0300, Egor Panfilov wrote: > I've started to prepare for the release, and have already created the > release branch. If some of you would like to review the release notes, > please, take a look at > https://github.com/scikit-image/scikit-image/blob/v0.14.x/doc/release/release_0.14.rst Where should comments on this document be made? Is there a PR or an easy way to annotate the document on GitHub? St?fan From egor.v.panfilov at gmail.com Thu May 24 15:37:05 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Thu, 24 May 2018 22:37:05 +0300 Subject: [scikit-image] Releasing 0.14 In-Reply-To: <20180524190246.qlpuqucnzeotngrp@carbo> References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> <20180524190246.qlpuqucnzeotngrp@carbo> Message-ID: Probably, the most convenient option is to use this temporary PR - https://github.com/scikit-image/scikit-image/pull/3102 , and write the comments as reviews. I'll later make the proposed changes directly in the v0.14.x branch. Regards, Egor ??, 24 ??? 2018 ?. ? 22:30, Stefan van der Walt : > On Wed, 23 May 2018 18:08:10 +0300, Egor Panfilov wrote: > > I've started to prepare for the release, and have already created the > > release branch. If some of you would like to review the release notes, > > please, take a look at > > > https://github.com/scikit-image/scikit-image/blob/v0.14.x/doc/release/release_0.14.rst > > Where should comments on this document be made? Is there a PR or an > easy way to annotate the document on GitHub? > > St?fan > _______________________________________________ > scikit-image mailing list > scikit-image at python.org > https://mail.python.org/mailman/listinfo/scikit-image > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefanv at berkeley.edu Thu May 24 19:01:27 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Thu, 24 May 2018 16:01:27 -0700 Subject: [scikit-image] Releasing 0.14 In-Reply-To: References: <20180521225026.4kelni5ibl5kg5xz@carbo> <1526955106.3914908.1380114200.3534A2AB@webmail.messagingengine.com> <20180524190246.qlpuqucnzeotngrp@carbo> Message-ID: <20180524230127.acn7ne5ihk3gpn7j@carbo> On Thu, 24 May 2018 22:37:05 +0300, Egor Panfilov wrote: > Probably, the most convenient option is to use this temporary PR - > https://github.com/scikit-image/scikit-image/pull/3102 , and write the > comments as reviews. > I'll later make the proposed changes directly in the v0.14.x branch. OK, perfect. Note that the previous release notes edit the PR list quite heavily to group them into more readable chunks. They then include the full PR list at the end. See, e.g., https://github.com/scikit-image/scikit-image/blob/master/doc/release/release_0.13.rst St?fan From stefanv at berkeley.edu Fri May 25 14:45:46 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Fri, 25 May 2018 11:45:46 -0700 Subject: [scikit-image] Sprint at UC Berkeley: Monday 28 May to Friday 1 June Message-ID: <20180525184546.xwzg3cnpereuv3gv@carbo> Hi everyone, We will be having a joint scikit-image / scikit-learn / dask sprint [0] at UC Berkeley, this coming week Monday to Friday. If there are issues you'd like to see discussed, please add them to the GitHub issue [1]. You are also more than welcome to attend the sprint in person (I apologize for the late notice). Best regards, St?fan [0] https://scisprints.github.io/ [1] https://github.com/scikit-image/scikit-image/issues/3086 From egor.v.panfilov at gmail.com Tue May 29 04:59:20 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Tue, 29 May 2018 11:59:20 +0300 Subject: [scikit-image] Scikit-image 0.14.0 release Message-ID: Hello list, On behalf of `scikit-image` team I'm happy to announce the release of `scikit-image` version 0.14.0 ! This release brings a lot of exciting additions (such as new segmentation tools and algorithms, new datasets and data generating routines), various enhancements (nD support for image moments and regionprops, rescale, resize and pyramid_* function, multichannel support for HOG, multiple performance improvements, and many more) and a number of bugfixes to the code and to the documentation. I am also pleased to inform you that 0.14.x is the last major release with official support for Python 2.7. In order to make the transition to Python 3.x smooth for all the users we're making this release a long-term support one (it will receive important bugfixes and backports for approx. 2 years, following the Python 2.7 end-of-life cycle). For more details on the changes and additions, please, refer to the release notes [1]. I'd like to thank all the developers of the library for their hard work, and all the users for staying with us! Regards, Egor Panfilov, scikit-image core team .. [1] https://github.com/scikit-image/scikit-image/blob/v0.14.x/doc/release/release_0.14.rst .. [2] https://pypi.org/project/scikit-image/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue May 29 06:58:52 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 29 May 2018 11:58:52 +0100 Subject: [scikit-image] Scikit-image 0.14.0 release In-Reply-To: References: Message-ID: Hi, On Tue, May 29, 2018 at 9:59 AM, Egor Panfilov wrote: > Hello list, > > On behalf of `scikit-image` team I'm happy to announce the release of > `scikit-image` version 0.14.0 ! > This release brings a lot of exciting additions (such as new segmentation > tools and algorithms, new datasets and data generating routines), various > enhancements (nD support for image moments and regionprops, rescale, resize > and pyramid_* function, multichannel support for HOG, multiple performance > improvements, and many more) and a number of bugfixes to the code and to the > documentation. > I am also pleased to inform you that 0.14.x is the last major release with > official support for Python 2.7. In order to make the transition to Python > 3.x smooth for all the users we're making this release a long-term support > one (it will receive important bugfixes and backports for approx. 2 years, > following the Python 2.7 end-of-life cycle). > > For more details on the changes and additions, please, refer to the release > notes [1]. > > I'd like to thank all the developers of the library for their hard work, and > all the users for staying with us! Congratulations ! I've built Windows wheels over at https://ci.appveyor.com/project/matthew-brett/scikit-image-wheels - just one test failure on Python 2.7, a stray extra warning: https://ci.appveyor.com/project/matthew-brett/scikit-image-wheels/build/1.0.18/job/wkxwudgyioytxa42#L1746 Wheels are up at https://3f23b170c54c2533c070-1c8a9b3114517dc5fe17b7c3f8c63a43.ssl.cf2.rackcdn.com/ OK for me to upload? (I have PyPI permissions). Cheers, Matthew From egor.v.panfilov at gmail.com Tue May 29 07:15:20 2018 From: egor.v.panfilov at gmail.com (Egor Panfilov) Date: Tue, 29 May 2018 14:15:20 +0300 Subject: [scikit-image] Scikit-image 0.14.0 release In-Reply-To: References: Message-ID: Hi Matthew, Please, do! The log looks fine, although we need to work on `random_walker` to make it less fragile. I'll report this issue to our bugtracker. Thank you very much for the prompt support! Regards, Egor ??, 29 ??? 2018 ?. ? 13:59, Matthew Brett : > Hi, > > On Tue, May 29, 2018 at 9:59 AM, Egor Panfilov > wrote: > > Hello list, > > > > On behalf of `scikit-image` team I'm happy to announce the release of > > `scikit-image` version 0.14.0 ! > > This release brings a lot of exciting additions (such as new segmentation > > tools and algorithms, new datasets and data generating routines), various > > enhancements (nD support for image moments and regionprops, rescale, > resize > > and pyramid_* function, multichannel support for HOG, multiple > performance > > improvements, and many more) and a number of bugfixes to the code and to > the > > documentation. > > I am also pleased to inform you that 0.14.x is the last major release > with > > official support for Python 2.7. In order to make the transition to > Python > > 3.x smooth for all the users we're making this release a long-term > support > > one (it will receive important bugfixes and backports for approx. 2 > years, > > following the Python 2.7 end-of-life cycle). > > > > For more details on the changes and additions, please, refer to the > release > > notes [1]. > > > > I'd like to thank all the developers of the library for their hard work, > and > > all the users for staying with us! > > Congratulations ! > > I've built Windows wheels over at > https://ci.appveyor.com/project/matthew-brett/scikit-image-wheels - > just one test failure on Python 2.7, a stray extra warning: > > > https://ci.appveyor.com/project/matthew-brett/scikit-image-wheels/build/1.0.18/job/wkxwudgyioytxa42#L1746 > > Wheels are up at > > https://3f23b170c54c2533c070-1c8a9b3114517dc5fe17b7c3f8c63a43.ssl.cf2.rackcdn.com/ > > OK for me to upload? (I have PyPI permissions). > > Cheers, > > Matthew > _______________________________________________ > scikit-image mailing list > scikit-image at python.org > https://mail.python.org/mailman/listinfo/scikit-image > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue May 29 07:54:40 2018 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 29 May 2018 12:54:40 +0100 Subject: [scikit-image] Scikit-image 0.14.0 release In-Reply-To: References: Message-ID: Hi Egor, On Tue, May 29, 2018 at 12:15 PM, Egor Panfilov wrote: > Hi Matthew, > > Please, do! > The log looks fine, although we need to work on `random_walker` to make it > less fragile. I'll report this issue to our bugtracker. > Thank you very much for the prompt support! No problem. Wheels are up now. Cheers, Matthew From stefanv at berkeley.edu Tue May 29 14:43:34 2018 From: stefanv at berkeley.edu (Stefan van der Walt) Date: Tue, 29 May 2018 11:43:34 -0700 Subject: [scikit-image] Scikit-image 0.14.0 release In-Reply-To: References: Message-ID: <20180529184334.hchia5ninruvwmk7@carbo> On Tue, 29 May 2018 11:59:20 +0300, Egor Panfilov wrote: > I'd like to thank all the developers of the library for their hard work, > and all the users for staying with us! A big thank you also from my side for everyone who helped to make this release possible! You all make an amazing team, and I am delighted to learn so much from you every day. We kick off 0.15.x development on a high note with a sprint here at UC Berkeley this week. Feel free to swing by on Gitter and say hi! Best regards, St?fan