Quick notes how to update docs and javadoc at release publication time. #10810
Conversation
| @@ -270,6 +270,46 @@ git tag -am 'Release Apache Iceberg <VERSION>' apache-iceberg-<VERSION> apache-i | |||
|
|
|||
| Then release the candidate repository in [Nexus](https://repository.apache.org/#stagingRepositories). | |||
|
|
|||
| #### Update docs and javadoc for the release | |||
There was a problem hiding this comment.
There is already a section called "### Documentation Release" can we move it under that?
It points to a readme and maybe we should update these steps in that readme.
There was a problem hiding this comment.
Reason I put here is because imho, it should be part of the release publication and should be mentioned as part of the release process.
No problem to update, but release manager has to go there (which is not obvious imho).
There was a problem hiding this comment.
I agree with Ajantha that it looks like there are two sections about docs:
The one that's already there doesn't add much value since the publication steps are not in there
There was a problem hiding this comment.
@ajantha-bhat resuming this PR: I guess you are proposing to move update docs and javadoc in the documentation-release section right ?
There was a problem hiding this comment.
Maybe we can even move these info in the README pointed out in that section.
We just need all docs related stuffs in one place.
There was a problem hiding this comment.
I agree, let me rework this. Thanks.
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
No description provided.