Author: buildbot
Date: Tue May 9 16:42:49 2023
New Revision: 1083149
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/release-management.html
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/release-management.html
==============================================================================
--- websites/production/cxf/content/release-management.html (original)
+++ websites/production/cxf/content/release-management.html Tue May 9 16:42:49
2023
@@ -58,7 +58,7 @@ Apache CXF -- Release Management
<td id="cell-1-1"> </td>
<td id="cell-1-2">
<!-- Banner -->
-<div class="banner" id="banner"><div class="table-wrap"><table class="wrapped
confluenceTable" style="width: 100.0%;" border="0" cellpadding="0"
cellspacing="0"><colgroup span="1"><col span="1"><col
span="1"></colgroup><tbody><tr><td align="left" colspan="1" rowspan="1"
class="confluenceTd" style="border: none;"><a shape="rect" title="Apache CXF"
href="http://cxf.apache.org/";> <span style="font-weight: bold;font-size:
170.0%;color: white;">Apache CXF</span> </a></td><td align="right" colspan="1"
rowspan="1" class="confluenceTd" style="border: none;"><div
class="content-wrapper"><a shape="rect" class="external-link"
href="http://www.apache.org/"; title="The Apache Software Foundation"> <span
class="confluence-embedded-file-wrapper image-right-wrapper
confluence-embedded-manual-size"><img class="confluence-embedded-image
confluence-external-resource image-right" draggable="false" alt="The Apache
Software Foundation" width="214" src="https://apache.org/img/asf_logo.png";
data-image-src="
https://apache.org/img/asf_logo.png";></span>
</a></div></td></tr></tbody></table></div></div>
+<div class="banner" id="banner"><div class="table-wrap"><table class="wrapped
confluenceTable" style="width: 100.0%;" border="0" cellpadding="0"
cellspacing="0"><colgroup span="1"><col span="1"><col
span="1"></colgroup><tbody><tr><td align="left" colspan="1" rowspan="1"
class="confluenceTd" style="border: none;"><a shape="rect"
href="http://cxf.apache.org/"; title="Apache CXF"> <span style="font-weight:
bold;font-size: 170.0%;color: white;">Apache CXF</span> </a></td><td
align="right" colspan="1" rowspan="1" class="confluenceTd" style="border:
none;"><div class="content-wrapper"><a shape="rect" class="external-link"
href="http://www.apache.org/"; title="The Apache Software Foundation"> <span
class="confluence-embedded-file-wrapper image-right-wrapper
confluence-embedded-manual-size"><img class="confluence-embedded-image
confluence-external-resource image-right" draggable="false" alt="The Apache
Software Foundation" width="214" src="https://apache.org/img/asf_logo.png";
data-image-src="
https://apache.org/img/asf_logo.png";></span>
</a></div></td></tr></tbody></table></div></div>
<!-- Banner -->
<div id="top-menu">
<table border="0" cellpadding="1" cellspacing="0" width="100%">
@@ -121,13 +121,16 @@ Apache CXF -- Release Management
<pre>mvn release:prepare -Peverything
mvn release:perform -Peverything
</pre>
-</div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>If you are performing the release
on a Mac, it is advisable to add -DpushChanges=false to the "release:prepare"
step above. The version of git that Apple ships with some versions of OSX has
problems pushing the changes in quick succession from the release plugin and
can become corrupt. Having the release plugin NOT push the changes and then
running "git push -tags origin master" works around that
problem.</p></div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>It is recommended to name the
local maintenance branches the same as the remote ones ("2.7.x-fixes", "3.0.x
-fixes", ...) to avoid issue with the branch names when running the release
plugin.</p></div></div><p> </p><p>The above commands tag the release,
update the poms versions, etc., then build it (off the tag), gpg sign and
deploy everything (including source jars and javadoc jars) to the <a
shape="rect" class="external-link" href="https://repository.apache.org";>Nexus
repository location</a>. When the build is done staging, you next need to login
to the Nexus repository and "close" the staging area (click on Staging
Repositories in the left-side menu, select the repo you just uploaded and then
select the close button.) Closing is very important. After the staging area is
closed, note the URL for the staging area as you will need that for the
vote.</p><p>At this point, everything "pre-vote" is done. Call the vote.</p><h2
id="ReleaseManagement-Releasingtheartifacts">Releasing the
artifacts</h2><ul><li>Maven artifacts - After the vote passes, you'll need to
promote that staging reposi
tory to the main location. Login to <a shape="rect" class="external-link"
href="https://repository.apache.org";>Nexus repository location</a> to do that
as well, find the staging repository and click the Release
button.</li></ul><ul><li><p>Distributions - You will need to commit the
distributions into the special svn distribution area: <a shape="rect"
class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf";>https://dist.apache.org/repos/dist/release/cxf</a>
<br clear="none"> after you commit they will be live on dist.apache.org fairly
quickly, but it will still take time for the mirrors to get copies. It's likely
easier to make the directory via an svn command, check out just that directory,
and then add the files. The dist area is rather large (400MB or so) so checking
out the entire thing may be slow.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>If you are performing the release
on a Mac, it is advisable to add -DpushChanges=false to the "release:prepare"
step above. The version of git that Apple ships with some versions of OSX has
problems pushing the changes in quick succession from the release plugin and
can become corrupt. Having the release plugin NOT push the changes and then
running "git push -tags origin master" works around that
problem.</p></div></div><div class="confluence-information-macro
confluence-information-macro-warning"><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>It is recommended to name the
local maintenance branches the same as the remote ones ("2.7.x-fixes", "3.0.x
-fixes", ...) to avoid issue with the branch names when running the release
plugin.</p></div></div><p><br clear="none"></p><p>The above commands tag the
release, update the poms versions, etc., then build it (off the tag), gpg sign
and deploy everything (including source jars and javadoc jars) to the <a
shape="rect" class="external-link" href="https://repository.apache.org";>Nexus
repository location</a>. When the build is done staging, you next need to login
to the Nexus repository and "close" the staging area (click on Staging
Repositories in the left-side menu, select the repo you just uploaded and then
select the close button.) Closing is very important. After the staging area is
closed, note the URL for the staging area as you will need that for the
vote.</p><p>At this point, everything "pre-vote" is done. Call the vote.</p><h2
id="ReleaseManagement-Releasingtheartifacts">Releasing the
artifacts</h2><ul><li>Maven artifacts - After the vote passes, you'll need to
promote that sta
ging repository to the main location. Login to <a shape="rect"
class="external-link" href="https://repository.apache.org";>Nexus repository
location</a> to do that as well, find the staging repository and click the
Release button.</li></ul><ul><li><p>Distributions - You will need to commit the
distributions into the special svn distribution area: <a shape="rect"
class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf";>https://dist.apache.org/repos/dist/release/cxf</a>
<br clear="none">after you commit they will be live on dist.apache.org fairly
quickly, but it will still take time for the mirrors to get copies. It's likely
easier to make the directory via an svn command, check out just that directory,
and then add the files. The dist area is rather large (400MB or so) so checking
out the entire thing may be slow.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default">svn mkdir
https://dist.apache.org/repos/dist/release/cxf/2.6.3
svn checkout https://dist.apache.org/repos/dist/release/cxf/2.6.3
.... add files to 2.6.3 .....
svn commit
</pre>
-</div></div></li></ul><p>The <a shape="rect"
href="http://cxf.apache.org/download.html";>download page</a> of a currently
released version will tell you the precise files you need to upload. Basically,
the -src.tar.gz, -src.zip, tar.gz, .zip files, and the .md5, .sha1, and .asc
signature files of each of those. For greatest accuracy, it's best to download
the files from Nexus and use those. (For example, for CXF 2.6.2, you would
check <a shape="rect" class="external-link"
href="https://repository.apache.org/content/repositories/releases/org/apache/cxf/apache-cxf/2.6.2/";>this
folder</a>).</p><ul><li>Update the download page - around 24 hours after
committing the distributions, update the download page, release notes, etc. to
point at the new versions. At that stage you'll want to delete (svn rm) the
previous version of each branch you uploaded to <a shape="rect"
class="external-link"
href="https://dist.apache.org";>https://dist.apache.org</a>, so if you added <a
shape="rect" class="ext
ernal-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.6.3";>https://dist.apache.org/repos/dist/release/cxf/2.6.3</a>
and <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.5.6";>https://dist.apache.org/repos/dist/release/cxf/2.5.6</a>,
you'll want to remove <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.6.2";>https://dist.apache.org/repos/dist/release/cxf/2.6.2</a>
and <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.5.5";>https://dist.apache.org/repos/dist/release/cxf/2.5.5</a>.
(Older versions will still be available at <a shape="rect"
class="external-link"
href="http://archive.apache.org/dist/cxf/";>http://archive.apache.org/dist/cxf/</a>
and are referenced from there on the CXF download
page.)</li></ul><ul><li>Unpack the javadocs from the appropriate
cxf-bundle-VERSION-javadocs.jar into the appropriate directory in an svn
checkout of <a shap
e="rect" class="external-link"
href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc";>https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc</a>
and commit the new version. Make sure any new files are
added.</li></ul><ul><li>Unpack the schemas directory from the appropriate
cxf-bundle-VERSION.jar and check if any of the schemas in <a shape="rect"
class="external-link"
href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas";>https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas</a>
need updating.</li></ul><h2 id="ReleaseManagement-UpdatingJIRA">Updating
JIRA</h2><p>JIRA will need to be updated:</p><ul><li>Add new versions that JIRA
items can be created against, and mark the version(s) you just released as
"released":</li></ul><ol><li>Go to the <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF";>CXF JIRA Home Page</a> and
select th
e "Versions" left menu item, then select "Manage Versions".</li><li>Select the
tools icon (far right side) for the version(s) you've just released and select
"Release".</li><li>Also on this screen type in new release versions for the
branch(es) you've released and plan on releasing more versions
from.</li></ol><ul><li>Close the JIRA items that were marked resolved for each
release:</li></ul><ol><li>From the previous screen, select "Exit
Administration".</li><li>From the CXF JIRA home page, select Versions from the
left-side menu, and for each version you just released:<ol><li>Select version,
then issues left-side menu item, then select the "Resolved" list.</li><li>From
the tools icon, select Bulk Change -> select all items -> Transition
Issues -> Close Issues -> Confirm.</li></ol></li></ol></div>
+</div></div></li></ul><p>The <a shape="rect"
href="http://cxf.apache.org/download.html";>download page</a> of a currently
released version will tell you the precise files you need to upload. Basically,
the -src.tar.gz, -src.zip, tar.gz, .zip files, and the .md5, .sha1, and .asc
signature files of each of those. For greatest accuracy, it's best to download
the files from Nexus and use those. (For example, for CXF 2.6.2, you would
check <a shape="rect" class="external-link"
href="https://repository.apache.org/content/repositories/releases/org/apache/cxf/apache-cxf/2.6.2/";>this
folder</a>).</p><ul><li>Update the download page - around 24 hours after
committing the distributions, update the download page, release notes, etc. to
point at the new versions. At that stage you'll want to delete (svn rm) the
previous version of each branch you uploaded to <a shape="rect"
class="external-link"
href="https://dist.apache.org";>https://dist.apache.org</a>, so if you added <a
shape="rect" class="ext
ernal-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.6.3";>https://dist.apache.org/repos/dist/release/cxf/2.6.3</a>
and <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.5.6";>https://dist.apache.org/repos/dist/release/cxf/2.5.6</a>,
you'll want to remove <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.6.2";>https://dist.apache.org/repos/dist/release/cxf/2.6.2</a>
and <a shape="rect" class="external-link"
href="https://dist.apache.org/repos/dist/release/cxf/2.5.5";>https://dist.apache.org/repos/dist/release/cxf/2.5.5</a>.
(Older versions will still be available at <a shape="rect"
class="external-link"
href="http://archive.apache.org/dist/cxf/";>http://archive.apache.org/dist/cxf/</a>
and are referenced from there on the CXF download page.)</li></ul><ul><li><p
class="auto-cursor-target">Javadocs - the javadocs in the distribution are a
limited set of javadocs useful for MOST people. 
However, the CXF website contains a more complete set of javadocs.  To
generate the docs for the site, from the source distribution (or git tag),
run:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">mvn javadoc:aggregate
+mvn package -DskipTests=true javadoc:aggregate-no-fork -pl distribution -am
-Peverything -Dmaven.javadoc.skippedModules=cxf-testutils</pre>
+</div></div><p class="auto-cursor-target">The first call (which WILL fail
while trying to process some of the system tests) makes sure all the necessary
things are built, code generated, etc...   The second call will
generate the javadoc for the site.  <span style="letter-spacing:
0.0px;">Then copy the contents of target/site/apidocs to a new versioned
directory in an svn checkout of </span><a shape="rect"
class="external-link"
href="https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc";
style="letter-spacing:
0.0px;">https://svn-master.apache.org/repos/infra/websites/production/cxf/content/javadoc</a><span
style="letter-spacing: 0.0px;"> and commit the new version. Make sure any new
files are added.</span></p></li></ul><ul><li>Unpack the schemas directory from
the appropriate cxf-bundle-VERSION.jar and check if any of the schemas in <a
shape="rect" class="external-link"
href="https://svn-master.apache.org/repos/infra/websites/producti
on/cxf/content/schemas">https://svn-master.apache.org/repos/infra/websites/production/cxf/content/schemas</a>
need updating.</li></ul><h2 id="ReleaseManagement-UpdatingJIRA">Updating
JIRA</h2><p>JIRA will need to be updated:</p><ul><li>Add new versions that JIRA
items can be created against, and mark the version(s) you just released as
"released":</li></ul><ol><li>Go to the <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF";>CXF JIRA Home Page</a> and
select the "Versions" left menu item, then select "Manage
Versions".</li><li>Select the tools icon (far right side) for the version(s)
you've just released and select "Release".</li><li>Also on this screen type in
new release versions for the branch(es) you've released and plan on releasing
more versions from.</li></ol><ul><li>Close the JIRA items that were marked
resolved for each release:</li></ul><ol><li>From the previous screen, select
"Exit Administration".</li><li>From the CXF JIRA home page, se
lect Versions from the left-side menu, and for each version you just
released:<ol><li>Select version, then issues left-side menu item, then select
the "Resolved" list.</li><li>From the tools icon, select Bulk Change ->
select all items -> Transition Issues -> Close Issues ->
Confirm.</li></ol></li></ol></div>
</div>
<!-- Content -->
</td>
![https://apache.org/img/asf_logo.png"](https://apache.org/img/asf_logo.png"){kind=link}