0.10.0 Release Tracker

[jlaehne]

Do we want to make a 0.10 release? I am particularly interested in #328 being available in a released version to facilitate colleagues the use of this file reader. Are there any currently open PRs/issues that should definitely be addressed still?

[ericpre]

Sounds good! I think that we need to sort out #425 and hyperspy/hyperspy#3528.

[jlaehne]

Does that require a prior HyperSpy release?

[ericpre]

It shouldn't require a hyperspy release - the current failure in #425 with RELEASE_next_minor is because hyperspy/hyperspy#3528 needs sorting before making a minor release of hyperspy.
However, it may be better to leave it for now to avoid rushing it. I can try to fix the current failures in a separate PR in the interest of making a rosettasciio release.

[ericpre]

I pull out the regression fix from hyperspy/hyperspy#3528 in hyperspy/hyperspy#3533 to fix the failure in the rosettaciio test suite with the development branch of hyperspy.

[ericpre]

I would suggest to merge #426 because it is ready to go and then it is ready to go?

@jlaehne, are you happy to do the release?

[jlaehne]

See #431