Initial Release

[jlaehne]

v0.1

We have progressed quite far on preparing an initial release and improving consistency within RosettaSciIO as documented in the milestone. Therefore, we should aim for a timely initial release. Let's try to use this issue to speed up that process and see what is left. In principle, I think we could even release the current state.

However, it would be good to clarify the following points:

• Permissive license or LGPL? #51
• Use pooch library to manage test files #14 (currently the test data blows up the project size)
• set_log_level for rosettasciio is needed #69
• Deprecate record_by metadata setting #79

Finally, there are a number of reported bugs that would be nice to get fixed (and most of them should be low hanging fruits):

• Signal type of EDS dataset #37
• Fix bug in _build_spectrum #66
• Error in reading 4DSTEM .mrc files from Velox #71
• Error when writing two-dimensional signal in mrcz format #73
• Cannot load elid file #82
• Latest python-box release breaks rosettasciio #83
• Fix exporting scalebar with reciprocal units containing space #90
• Incorrect Scale Conversion for Non-FEI MRC Files #91
• Non-FEI MRC Files Fail to Load #96

And of course, it is always good to

• Increase coverage #60

Once, we are happy with the state, we need to

• Create release workflow file (Add release workflow #126)
• Document releasing workflow (Add release workflow #126)
• Create RosettaSciIO on pypi - this is setup with trusted publisher in Add release workflow #126
• Zenodo is setup to create DOI and entry on creation of the github release.
• Do initial release on github - Add release workflow #126 set it up to create GitHub release after successfully generating sdist and wheel and uploading to pypi.org
• Create conda-forge feedstock

[jlaehne]

Do feel free to edit and add to the above list.

[ericpre]

We could merge the existing the PR ready to review and proceed with the release. The rest can be addressed in following releases.

[ericpre]

After #129 and #131 are done and merged, I think that we can proceed with the release, everything should be in place.

[jlaehne]

#11, #55 and #87 are also ready for review and may be included in the initial release - though they should not hold back the release as we can then easily do follow-up releases.

[ericpre]

#11 is quite large and may take time to review - except it someone already started reviewing it?

[CSSFrancis]

I need to make some changes to #11 based on the changes introduced by #111 so I was kind of waiting before going back to it. I would vote for going for the 0.1.0 release and then we can add it later.

[jlaehne]

The initial release is out: #133