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

Consider DOI release assignment strategy #319

Open

jarmarshall opened this issue Apr 4, 2019 · 1 comment

Labels

documentation question

Milestone

Contributor

jarmarshall commented Apr 4, 2019

Currently the deployment strategy (https://mumot.readthedocs.io/en/latest/development.html) specifies requesting a new DOI for each release. This may not be appropriate for patch releases, unless contributors have changed. Note, however that the ORDA entry refers to a specific branch, so this will be out-of-date once a new release is made (see e.g. https://figshare.shef.ac.uk/articles/MuMoT_Release_1_0_0/7951298/1)

The strategy should be left as is, or refined and described appropriately in the docs

jarmarshall added question documentation labels

jarmarshall added this to the First release patch milestone

Contributor Author

jarmarshall commented Sep 30, 2019

So as of https://github.com/DiODeProject/MuMoT/milestone/3 I think this should be left as is...

jarmarshall modified the milestones: First release patch, Second release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment