You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li>The Rampart project has 8 modules under it. They are:
@@ -186,5 +181,125 @@ align="middle" />
186
181
<p></p>
187
182
188
183
<p></p>
189
-
</body>
184
+
185
+
<h3>Release process and release preparation</h3>
186
+
<p>Check that all dependencies and plugins are available from standard repositories. To do this, clean the local repository and execute 'mvn clean install followed by 'mvn site'</p>
187
+
188
+
<p>Check that the set of license files in the legal directory is complete and accurate (by checking that in the binary distribution for every third party JAR in the lib directory. </p>
189
+
190
+
<p>Check that the apache-release profile can be executed properly. To do this, issue the following command: mvn clean install -Papache-release -DskipTests=true</p>
191
+
192
+
<p>You may also execute a dry run of the release process: mvn release:prepare -DdryRun=true. After this, you need to clean up using the following command: mvn release:clean</p>
193
+
194
+
<p>Check that the Maven site can be generated and deployed successfully, and that it has the expected content.</p>
195
+
196
+
<p>To generate the entire documentation in one place, complete with working inter-module links, execute the site-deploy phase (and check the files under target/staging). A quick and reliable way of doing that is to use the following command: mvn -Dmaven.test.skip=true clean package site-deploy</p>
197
+
198
+
<p>Complete the release notes in the new src/site/markdown/release-notes .md file, i.e. 2.0.0.md. It should include a description of the major changes in the release as well as a list of resolved JIRA issues.</p>
199
+
200
+
<h3>Prerequisites</h3>
201
+
202
+
<p>The following things are required to perform the actual release:</p>
203
+
204
+
<p>A PGP key that conforms to the <ahref="http://specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf"> requirement for Apache release signing</a></p>
205
+
206
+
<p>To make the release process easier, the passphrase for the code signing key should be configured in ~/.m2/settings.xml</p>
<p>To make the release process easier, the passphrase for the code signing key should be configured in ~/.m2/settings.xml</p>
224
+
225
+
<p>The release process uses a Nexus staging repository. Every committer should have access to the corresponding staging profile in Nexus. To validate this, login to repository.apache.org and check that you can see the org.apache.axis staging profile. The credentials used to deploy to Nexus should be added to settings.xml</p>
226
+
227
+
<h3>Release</h3>
228
+
229
+
<p>In order to prepare the release artifacts for vote, execute the following steps:</p>
230
+
231
+
<p>If necessary, update the copyright date in the top level NOTICE file.</p>
232
+
233
+
<p>Start the release process with the following command:</p>
234
+
235
+
<code>mvn release:prepare</code>
236
+
237
+
<p>When asked for the "SCM release tag or label", keep the default value (x.y.z) </p>
238
+
239
+
<p>The above command will create a tag in Subversion and increment the version number of the trunk to the next development version. It will also create a release.properties file that will be used in the next step.</p>
240
+
241
+
<p>Perform the release using the following command: </p>
242
+
243
+
<code>mvn release:perform</code>
244
+
245
+
<p>This will upload the release artifacts to the Nexus staging repository.</p>
246
+
247
+
<p>Close the staging repository. The name of the staging profile is org.apache.axis. See <ahref="https://maven.apache.org/developers/release/maven-project-release-procedure.html"> for a more thorough description of this step. </a></p>
248
+
249
+
<p>Execute the target/checkout/etc/dist.py script to upload the source and binary distributions to the development area of the <ahref="https://dist.apache.org/repos/dist/"> repository. </a></p>
250
+
251
+
<p>If not yet done, export your public key and <ahref="https://dist.apache.org/repos/dist/release/axis/axis2/java/rampart/KEYS"> append it here. </a></p>
252
+
253
+
<p>The command to export a public key is as follows:</p>
254
+
255
+
<code>gpg --armor --export key_id</code>
256
+
257
+
<p>Delete <ahref="https://dist.apache.org/repos/dist/release/axis/axis2/java/rampart/KEYS"> if it exists. </a></p>
<p>The staging area will be checked out to target/scmpublish-checkout (relative to target/checkout). Do a sanity check on the changes and then commit them.</p>
270
+
271
+
<p>Start the release vote by sending a mail to [email protected] . The mail should mention the list of issues solved in the release (by linking to the relevant JIRA view).</p>
272
+
273
+
<p>Include a link to the location of the Nexus staging repository, and a link to the <ahref="https://dist.apache.org/repos/dist/dev/axis/axis2/java/rampart/"> source and binary distributions. </a></p>
274
+
275
+
<p>A link to the preview of the <ahref="https://axis.apache.org/axis2/java/rampart-staging/"> Maven site. </a></p>
276
+
277
+
<p>If the vote passes, execute the following steps:</p>
278
+
279
+
<p>Promote the artifacts in the staging repository. See<ahref="https://central.sonatype.org/publish/release/#close-and-drop-or-release-your-staging-repository"> for detailed instructions for this step.</a></p>
<code>svn co --depth=immediates https://svn.apache.org/repos/asf/axis/site/ site ; cd site/axis2/java ; svn rm rampart ; svn mv rampart-staging rampart ; svn commit</code>
289
+
290
+
<p>It may take several hours before all the updates have been synchronized to the relevant ASF systems. Before proceeding, check that the Maven artifacts for the release are available from the Maven central repository, and the <ahref="https://axis.apache.org/axis2/java/rampart/"> Rampart Maven site has been synchronized.</a></p>
291
+
292
+
<p>Verify the binary and source distributions can be downloaded from the<ahref="https://axis.apache.org/axis2/java/rampart/download.html"> Rampart download page.</a></p>
293
+
294
+
<p>Once everything is in place, send announcements to [email protected] and [email protected]. Since the two lists have different conventions, audiences and moderation policies, to send the announcement separately to the two lists.</p>
295
+
296
+
<p>Sample announcement:</p>
297
+
298
+
<p>Apache Rampart Team is pleased to announce the release of Rampart x.y.z. The release is available for download at:</p>
<p>Apache Rampart provides implementations of the WS-Sec* specifications for Apache Axis2, based on Apache WSS4J and the Apache Axiom DOOM implementation.</p>
0 commit comments