Author: stoty
Date: Fri Apr 4 07:57:19 2025
New Revision: 1924764
URL: http://svn.apache.org/viewvc?rev=1924764&view=rev
Log:
PHOENIX-7570 Update release process page to close staged maven repos immediately
Modified:
phoenix/site/publish/release.html
phoenix/site/source/src/site/markdown/release.md
Modified: phoenix/site/publish/release.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/release.html?rev=1924764&r1=1924763&r2=1924764&view=diff
==============================================================================
--- phoenix/site/publish/release.html (original)
+++ phoenix/site/publish/release.html Fri Apr 4 07:57:19 2025
@@ -234,6 +234,10 @@ Generated by Apache Maven Doxia
<p>If the dyr-run release artifacts (source, binary, and maven) check out,
then do publish a real RC to ASF</p>
<p>Repeat the dry run process, but add the <code>-f</code> switch to the
<code>do-release-docker.sh</code> command.</p>
<p>The script will upload the source and binary release artifacts to a
directory under <code>https://dist.apache.org/repos/dist/dev/phoenix/</code>
The script will also deploy the maven artifacts to
<code>https://repository.apache.org/#stagingRepositories</code> Check that
these are present.</p>
+ <section>
+ <h3 id="Close_the_staging_repository">Close the staging repository</h3>
+ <p>The published staging repository is in the âopenâ state. Open staging
repositories are agressively cleaned up, and may be removed by the time the
vote passes. To avoid this, <a class="externalLink"
href="https://central.sonatype.org/publish/release/#locate-and-examine-your-staging-repository";>close</a>
(but DO NOT release) the staging repository immediately after deployment.</p>
+ </section>
</section>
<section>
<h2 id="Voting">Voting</h2>
@@ -257,7 +261,7 @@ Generated by Apache Maven Doxia
</pre>
</div></li>
<li><p>Remove any obsolete releases on <a class="externalLink"
href="https://dist.apache.org/repos/dist/release/phoenix";>https://dist.apache.org/repos/dist/release/phoenix</a>
given the current release.</p></li>
- <li><p>Go to <a class="externalLink"
href="https://repository.apache.org/#stagingRepositories";>https://repository.apache.org/#stagingRepositories</a>
and <code>close</code> -> <code>release</code> the staged artifacts (takes
a while so you may need to <code>refresh</code> multiple times).</p></li>
+ <li><p>Go to <a class="externalLink"
href="https://repository.apache.org/#stagingRepositories";>https://repository.apache.org/#stagingRepositories</a>
and <code>release</code> the staged artifacts (takes a while so you may need
to <code>refresh</code> multiple times).</p></li>
<li><p>Create new branch based on current release if needed, for ex: 4.15
branches in this case.</p></li>
<li><p>Set version to the upcoming SNAPSHOT and commit:</p>
<div class="source">
Modified: phoenix/site/source/src/site/markdown/release.md
URL:
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/release.md?rev=1924764&r1=1924763&r2=1924764&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/release.md (original)
+++ phoenix/site/source/src/site/markdown/release.md Fri Apr 4 07:57:19 2025
@@ -82,6 +82,13 @@ The script will upload the source and bi
The script will also deploy the maven artifacts to
`https://repository.apache.org/#stagingRepositories`
Check that these are present.
+### Close the staging repository
+
+The published staging repository is in the "open" state. Open staging
repositories
+are agressively cleaned up, and may be removed by the time the vote passes.
+To avoid this,
[close](https://central.sonatype.org/publish/release/#locate-and-examine-your-staging-repository)
+(but DO NOT release) the staging repository immediately after deployment.
+
## Voting
1. Initiate the vote email. See example
[here](https://www.mail-archive.com/dev@phoenix.apache.org/msg41202.html), or
use the `<workdir>/output/vote.txt` template generated by the script.
2. In case the RC (Release Candidate) is rejected via the vote, you will have
to repeat the above process and re-initiate the vote for the next RC (RC0, RC1,
etc.).
@@ -101,7 +108,7 @@ Check that these are present.
</pre>
3. Remove any obsolete releases on
https://dist.apache.org/repos/dist/release/phoenix given the current release.
-4. Go to https://repository.apache.org/#stagingRepositories and
<code>close</code> -> <code>release</code> the staged artifacts (takes a while
so you may need to `refresh` multiple times).
+4. Go to https://repository.apache.org/#stagingRepositories and
<code>release</code> the staged artifacts (takes a while so you may need to
`refresh` multiple times).
7. Create new branch based on current release if needed, for ex: 4.15 branches
in this case.
8. Set version to the upcoming SNAPSHOT and commit:
