Skip to content

Docs: update document release steps#9921

Closed
ajantha-bhat wants to merge 1 commit intoapache:mainfrom
ajantha-bhat:docs_release
Closed

Docs: update document release steps#9921
ajantha-bhat wants to merge 1 commit intoapache:mainfrom
ajantha-bhat:docs_release

Conversation

@ajantha-bhat
Copy link
Member

Remove the references about archived iceberg-docs repo and point to README.

@github-actions github-actions bot added the docs label Mar 11, 2024
@ajantha-bhat ajantha-bhat requested review from Fokko and nastra March 12, 2024 10:30
@ajantha-bhat ajantha-bhat force-pushed the docs_release branch 2 times, most recently from 7a3af5a to ae8fc63 Compare March 12, 2024 12:55
repository and `iceberg` repository. Adjust the commands accordingly if it is not the case. Note that all
changes in `iceberg` need to happen against the `master` branch and changes in `iceberg-docs` need to happen
against the `main` branch.
Please follow the steps from [README](../README.md) to update the site docs and javadocs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this link to the section that mentions what needs to be done during a release?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to link to https://github.com/apache/iceberg/blob/main/site/README.md#release-process, but release deploy won't work. So, I linked the whole file.

P.S: I just want to get rid of referencing the archived iceberg-docs repo. Once we have automation we can update this section or add more info about manual steps in a follow up.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ajantha, now that the release is out, could you and @Fokko and @nastra help me review my release script?

Three thinks I'd like to have fixed by the next release are:

  1. Fix internal links that cross versioned doc and site boundaries.

  2. Add release script.

  3. Update release and contribution docs.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Always happy to validate.

So you want us to keep this PR on hold until we have the script for release?

@ajantha-bhat
Copy link
Member Author

Closing this PR as #10402 has handled the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants