Closed mcs07 closed 5 years ago
Thank you for the proposal.
I will tag the current code as it should have full support for the MMTF spec 1.0 while the currently open issues and PRs include experimental support for the next MMTF spec.
There is a release version now here: https://github.com/rcsb/mmtf-cpp/releases
It would be nice to have a commit tagged as a release (i.e. "v1.0.0" or even "v0.01" if you want to indicate some level of instability). This would be useful because I'd like to make a conda-forge recipe for this project.
Additionally, it would be even better if a release archive was prepared and uploaded to the GitHub releases page without the submodules etc. I think this relates to #21. It could probably be automated with a CI job, but this would be more work and a simple tagged commit would still be very useful in the meantime.