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).
пн, 21 мая 2018 г. в 15:57, Juan Nunez-Iglesias firstname.lastname@example.org:
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.
scikit-image mailing list email@example.com https://mail.python.org/mailman/listinfo/scikit-image