improve docs for making releases #9024
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 5, 2022
Closed
bencomp
approved these changes
Oct 18, 2022
| Update Guides Link | ||
| ------------------ | ||
|
|
||
| "latest" at https://guides.dataverse.org/en/latest/ is a symlink to the directory with the latest release. That directory (e.g. ``5.10.1``) was put into place by the Jenkins "guides" job described above. |
There was a problem hiding this comment.
Perhaps you could create a link to the specific section, instead of writing "described above"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
For better understanding and knowledge sharing of our release process.
Which issue(s) this PR closes:
None, but these changes are based on running through the tasks for the 5.12 release (#9019).
Special notes for your reviewer:
For consistency, in the doc I stuck with 5.10.1 in all the examples.
Should "tweet about the release" be a step? I left it out because I'm not personally very into Twitter anymore.
Suggestions on how to test this:
None. Please just read it and see if it makes sense.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
No.
Additional documentation:
No.