Hi Stefan,

From my perspective there are still some issues to be closed before the release (see https://github.com/scikit-image/scikit-image/milestone/6). This year we have been using GitHub features extensively and they should represent our current point of view regarding the codebase status. Among the tagged issues there are some long-lasting ones, and these could be transfered into 0.13 roadmap. As for the others, I'd prefer to solve them first.

Regarding release schedule: we are having a discussion in https://github.com/scikit-image/scikit-image/issues/2357. In short, the convenient release schedule should be tied to deprecation policy timeline, which is to be reviewed.

Above said, I'd suggest to push the release date a bit further. At least, the freeze initiation.

Regards,

Egor Panfilov

P.S. I'm traveling on the next week, and will not be able to contribute significant efforts till Dec'26th. However, I'll try to track the mailing list, and participate in the discussions (if any).

2016-12-18 1:24 GMT+03:00 Stefan van der Walt <stefanv@berkeley.edu>:

Hi, everyone

It's time for a new skimage release. I have the following timeline in mind:

Thursday 22 Dec, feature freeze
-- bug fixes, documentation, clean up --
January 5th, tag pre-release
-- developer and early adopter testing--
January 10th, tag release

How does that sound?

Also, do we have a volunteer for release manager? :)

Finally, I m thinking it may be a good idea to make an automated release schedule for the future. E.g. release every 4 months, and work out how long we need to freeze each time. Opinions?

Stéfan

_______________________________________________
scikit-image mailing list
scikit-image@python.org
https://mail.python.org/mailman/listinfo/scikit-image