-
Notifications
You must be signed in to change notification settings - Fork 29
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
Zenodo Release of Thetis #165
Comments
As thetis is a single repository, making a manual zenodo release is quite straightforward. With firedrake this is more involved as you need to bundle up all the firedrake components, so having a dedicated firedrake-zenodo utility makes sense. However, in order to have a functional thetis release, the full firedrake software stack should be included as well. So I think the right way would be to install thetis with firedrake-install and then make a release with firedrake-zenodo which would store thetis sources as well (currently it does not include thetis). |
To do this, we could add an option to firedrake-zenodo that automatically builds a thetis release and links it all together (this is not difficult). I think we don't always want to release thetis when cutting a firedrake release (just because we have thetis installed doesn't necessarily mean that we want a thetis release). So we'd support
And then it's just a matter of the person running the release having the necessary oauth scope to make thetis releases. |
Yeah, that sounds like a good solution. |
@wence- How much work would it be to get thetis included in firedrake-zenodo? I think this would be the best solution in the long run. |
Here's and example Firedrake/Thetis bundle that I'd need:
|
Currently releasing a version of Thetis through zenodo is a manual process. It would be nice if this could be done automatically, the same way as already occurs using firedrake-zenodo with firedrake.
The text was updated successfully, but these errors were encountered: