Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tag a release #24

Closed
mcs07 opened this issue Jan 24, 2019 · 2 comments
Closed

Tag a release #24

mcs07 opened this issue Jan 24, 2019 · 2 comments

Comments

@mcs07
Copy link

mcs07 commented Jan 24, 2019

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.
@gtauriello gtauriello mentioned this issue Jan 31, 2019
Closed
@gtauriello
Copy link
Collaborator

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.

@gtauriello gtauriello mentioned this issue Feb 1, 2019
Merged
@gtauriello
Copy link
Collaborator

There is a release version now here: https://github.com/rcsb/mmtf-cpp/releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mcs07 @gtauriello