Guide release manager to give a last chance to backup docs artifact before removing it #505
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.
In release process page, we guide the release manager "too lately" about keeping the generated docs of the latest RC. The guidance sentence appears later than removing docs from svn.
https://spark.apache.org/release-process.html - read through the section "finalize the release".
If release manager does not have any backup, they are expected to build the docs from scratch, and it's really painful to set up languages and corresponding libraries locally to build the doc (release script with docker is no longer usable at this time). It would be better to remind that they can take a backup before removing the artifact, which they will use the backup very soon.
Here is the screenshot of the change - bold NOTE sentence: