-
Notifications
You must be signed in to change notification settings - Fork 3
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
Revise EDAM release process to ensure sync with bio.tools #13
Comments
From @matuskalas on December 15, 2017 12:19 @hansioan What do you mean by "formally release"? @joncison Why would you want to update bio.tools before new EDAM version is released? I would understand if you want it right after. |
@matuskalas - that's essentially what I mean: @hansioan updates bio.tools before we "formally release" (i.e. announce) a new EDAM release - this way, people don't go to bio.tools with the wrong expectations. the good news is that Hans has automated the process for updating bio.tools for new EDAM releases - although he still needs to run the scripts manually (no continuous integration yet) |
From @matuskalas on December 15, 2017 22:6 Ok @joncison , then let's from now on do all the releasing circus up to the point of the GitHub/Zenodo release, then notify @hansioan to run his scripts & give back the green light, and then announce. |
From @matuskalas on January 1, 2018 21:58 @hansioan, could you please update bio.tools as soon as you're available with the new EDAM version 1.20? 1000000 thanks! |
From @hansioan on January 1, 2018 23:4 Done. |
From @hansioan on January 1, 2018 23:27 @matuskalas also done with deprecation fixes in bio.tools |
I updated the release process (http://edamontologydocs.readthedocs.io/en/latest/editors_guide.html) with note to mail Hans and confirm bio.tools is happy before announcing. |
From @joncison on December 15, 2017 11:52
Suggestion from talking with @hansioan is to not formally release EDAM until it's updated in bio.tools, to avoid problems like bio-tools/biotoolsRegistry#296
The task is to update the release docs (http://edamontologydocs.readthedocs.io/en/latest/editors_guide.html) and then stick to this.
cc @matuskalas @hmenager
Copied from original issue: edamontology/edamontology#338
The text was updated successfully, but these errors were encountered: