-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Add release instructions #2303
Add release instructions #2303
Conversation
The release branches are in a reasonable state for finalising a release. |
Another thing to mention, is that whilst the integration testing worked smoothly, the tags did not build the documentation the first time, because the CI was pointing to |
Thanks for the explanation! I see the issue, I'll add something to the documentation. In the content of DOLFINx, it would be great if the Actions simply read a JSON file with the git refs of the accompanying FEniCSx components, rather than having to change them manually in about 10 files. |
Should some details about adding a new version to the Spack packages be added in a future PR? |
RELEASE.md
Outdated
and mistakes before they reach tagged versions. | ||
|
||
At each of the following links run the GitHub Action Workflow manually using | ||
the `develop` branch in all fields. *Only proceed to tagging once all tests pass.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have develop
branches?
Probably won't get all of this done in one go but it's a start.