# scikit-image atlantic meeting 2020-04-15

Starting time: 15:00 (Paris),

Join via [Zoom](https://monash.zoom.us/j/284282585)

Present: Emma, Lars, François, Stéfan, Karishma Gupta

## Items from the previous meeting

- See [scikit-image/meeting-notes](https://github.com/scikit-image/meeting-notes).

## Agenda

- pre-release checklist: which PRs should still get in? [#4496](https://github.com/scikit-image/scikit-image/pull/4496), [#3850](https://github.com/scikit-image/scikit-image/pull/3850)
- [skeletonize_3d produces a zero array in certain conditions](https://github.com/scikit-image/scikit-image/pull/3757)
- what could be done to [simplify the release process](https://github.com/scikit-image/scikit-image/issues/4544)?
- feedback on rotating charge of repo follow-up
- bug report: [#4583](https://github.com/scikit-image/scikit-image/issues/4583) should rescale intensity always return out_range dtype? @jni thinks yes. Currently it returns an image in the input dtype!
- decide between `selem`, `footprint`, `structure` or `neighborhood`, or `kernel` as parameter name for the structuring element, see [#4154](https://github.com/scikit-image/scikit-image/issues/4154) and [#4581](https://github.com/scikit-image/scikit-image/issues/4581)
- CI failure: any idea what's going on?
- all Py3.7, segmentation faults / access violations after, during `segmentation/tests/test_felzenszwalb.py::test_grey` [example log](https://dev.azure.com/scikit-image/scikit-image/_build/results?buildId=2956&view=logs&j=334af232-6109-57b9-b294-3cb1e881b307&t=39339382-c83a-5968-2bb4-5c9c395c8d0a&l=5295)?
- Looks like it's caused by the pre-install of Cython 3.0a1

## Action items

- Check on status of Azure pipelines with Egor: is our testing well split between this and AppVeyor? Are we using all our parallel workers with the different services optimally to ensure short builds?

---

After the meeting, please commit the contents of this document into the [meeting notes](https://github.com/scikit-image/meeting-notes) repo. Then clear out this document so that it can be re-used for the next meeting.