Author: buildbot Date: Sat Sep 23 10:57:25 2017 New Revision: 1018570 Log: Production update by buildbot for cxf
Modified: websites/production/cxf/content/cache/main.pageCache websites/production/cxf/content/dosgi-release-build.html Modified: websites/production/cxf/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/cxf/content/dosgi-release-build.html ============================================================================== --- websites/production/cxf/content/dosgi-release-build.html (original) +++ websites/production/cxf/content/dosgi-release-build.html Sat Sep 23 10:57:25 2017 @@ -99,12 +99,7 @@ Apache CXF -- DOSGi release build <td height="100%"> <!-- Content --> <div class="wiki-content"> -<div id="ConfluenceContent"><h2 id="DOSGireleasebuild-Preparations">Preparations</h2> - -<ul><li>Make sure your .m2/settings.xml contains your user and password</li></ul> - - -<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> +<div id="ConfluenceContent"><h2 id="DOSGireleasebuild-Preparations">Preparations</h2><ul><li>Make sure your .m2/settings.xml contains your user and password</li></ul><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> <servers>     <server>       <id>apache.snapshots.https</id> @@ -118,24 +113,7 @@ Apache CXF -- DOSGi release build     </server> </servers> </pre> -</div></div> -<ul><li>Make sure you have a pgp key</li><li>Make sure all jira issues for the version are resolved</li><li>Export the jira issues from the jira roadmap view of the version you are doing and update distribution/multi-bundle/src/main/release/release_notes.txt</li></ul> - - -<h2 id="DOSGireleasebuild-Dothereleaseinmaven">Do the release in maven</h2> - -<ul><li>mvn release:prepare</li><li>mvn release:perform</li><li>go to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a>, log in with you apache id, find your staging repo and close it</li></ul> - - -<h2 id="DOSGireleasebuild-Checkcompleteness">Check completeness</h2> - -<ul><li>Check the tag is there in subversion and contains the correct version in the poms</li><li>Check that the release notes are correct</li><li>Check that the staging repo is visible and contains the correct release version</li></ul> - - -<h2 id="DOSGireleasebuild-Sendvotemailtodevlist">Send vote mail to dev list</h2> - - -<h2 id="DOSGireleasebuild-Releasemavenrepo">Release maven repo</h2></div> +</div></div><ul><li>Make sure you have a pgp key</li><li>Make sure all jira issues for the version are resolved</li><li>Export the jira issues from the jira roadmap view of the version you are doing and update distribution/multi-bundle/src/main/release/release_notes.txt</li></ul><h2 id="DOSGireleasebuild-Dothereleaseinmaven">Do the release in maven</h2><p>When releasing on windows you might need the addtional argument -Dgpg.executable=C:\java\gnupg\bin\gpg.exe . This makes sure gpg 2 iss used instead of the git shell provided gpg1.</p><ul><li>mvn release:prepare -Darguments="-DskipTests"</li><li>mvn release:perform -Darguments="-DskipTests"</li><li>go to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a>, log in with you apache id, find your staging repo and close it</li></ul><h2 id="DOSGireleasebuild-Checkcompleteness">Check completeness</h2><ul><li>Check the tag is there in subversion and contains the correct version in the poms</li><li>Check that the release notes are correct and LICENSE and NOTICE are present in the distros</li><li>Check that the staging repo is visible and contains the correct release version</li></ul><h2 id="DOSGireleasebuild-Sendvotemailtodevlist">Send vote mail to dev list</h2><h2 id="DOSGireleasebuild-Releasemavenrepo">Release maven repo</h2><h2 id="DOSGireleasebuild-Deletestagedrelease">Delete staged release</h2><p>Sometimes people find issues in a staged release. In this case we need to remove the release and redo it.</p><p>Delete the tag locally and on the git server</p><pre>git tag --delete tagname<br clear="none">git push --delete origin tagname</pre><p>Delete staged artifacts on <a shape="rect" class="external-link" href="http://repo.apache.org">http://repo.apache.org</a></p><p> </p></div> </div> <!-- Content --> </td>