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.
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
Happy release! #93
Comments
I totally agree. No fixed release schedule. Releases should be done when its needed. I have choosen the following scheme: Release name is date.month like 2019.08. If for whatever reason we need to make more than one release a month we use consecutive numbers after year.month like 2019.08.1. We will try to get a doi for each release and attach it somehow to the data. On my TODO for next week. |
I would like to contradict, and support time-based releases, which are much more predictable. We can still discuss which server serves devel or the last release, to make people happy that want to see their data immediately. Yours, Steffen |
The upload of data is not predictable, thus a fixed scheme is even not predictable... I want to see my spectra ASAP on massbank.eu and not on an dev server, to be honest. I guess, we loose contributors with a strict policy..... |
I agree with Tobias …
|
@meier-rene, will the release number be displayed on MassBank server? |
No more comments? So, we go for the just in time releases rather than fixed releases, right? |
I am still in favour of immediate availability of newly merged data, but also predictable releases. |
Okay, I agree with a test phase. Fixed release is still not my favour, because I don't see any advantage. |
Very cool, thanks Rene! Yours, Steffen |
I have created releases for MassBank-web and MassBank-data and I have put documentation for the release process in the README. For each MassBank-data release an archive and a persistent DOI is automatically created at Zenodo. You can see and click the DOI on the dev page of our README https://github.com/MassBank/MassBank-data/tree/dev. Will be on the main page with the next release. |
Thanks for your efforts @meier-rene. However, we need some release policy. Changes and updates in the data are occuring from time to time rather than frequently. Often the upload is also related to reportings or publishing of a paper.
Hence, a fixed release frequency is not an appropriate way to go. I suggest a very open release policy, that means that we release on request or as a larger set of new spectra is uploaded. I would expect that as a contributor, I want to see my spectra online ASAP and I don't want to wait for weeks (as in paper publishing....).
The text was updated successfully, but these errors were encountered: