Skip to content

Site Update: Document the Automated Release Process - #224

Open
RussellSpitzer wants to merge 5 commits into
apache:productionfrom
RussellSpitzer:docs/release-github-actions
Open

RussellSpitzer wants to merge 5 commits into
apache:productionfrom
RussellSpitzer:docs/release-github-actions

Conversation

@RussellSpitzer

Copy link
Copy Markdown
Member

Documentation of apache/parquet-java#3547.

The release is now run with the Prepare RC, Cancel RC, and Publish
After Vote workflows in apache/parquet-java. Replace the manual steps
(prepare-release.sh, release:perform, closing and releasing in Nexus,
source-release.sh, finalize-release) with how to run each workflow,
its inputs, and what it does.

The dist.apache.org promotion stays a manual PMC step because the
workflow credentials can only write to dist/dev; the page shows the
svn commands that the Publish summary prints. The verification guide
is unchanged.

Generated-by: Claude Opus 5.5
Prepare RC and Publish After Vote check out the parquet-X.Y.x release
branch themselves, so the page no longer tells release managers to pick
a release branch when they run them.

Generated-by: Claude Opus 5.5
Each workflow now has a table of its inputs with the default and what
the input does. Numbered lists use explicit numbers so that the source
reads the same as the rendered page.

Generated-by: Claude Opus 5.5
The key is already in KEYS, so link to KEYS and show the key's
fingerprint instead of saying that it must be added.

Generated-by: Claude Opus 5.5
Rewrite the page in plain English: short sentences in active voice, no
semicolons or phrasal verbs, and lists for steps and conditions. Use
one word for each idea, for example "verify" and "checksum". The
repository secrets are now in a table. The release cadence and release
verification sections also get typo and grammar fixes.

Generated-by: Claude Opus 5.5

#### 1\. Run the prepare script
N.B. These workflows release only parquet-java. The steps to release
parquet-format are manual. The mechanics (keys, branches, votes) are the same.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we want to keep the original manual steps somewhere since parquet-format still uses the old approach?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants