Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki" for change notification.
The "HttpComponentsReleaseProcess" page has been changed by OlegKalnichevski: https://wiki.apache.org/HttpComponents/HttpComponentsReleaseProcess?action=diff&rev1=1&rev2=2 * Make sure there are no open Jira issues targeted for this release - HttpCore - https://issues.apache.org/jira/browse/HTTPCORE + * HttpCore - https://issues.apache.org/jira/browse/HTTPCORE - HttpClient - https://issues.apache.org/jira/browse/HTTPCLIENT + * HttpClient - https://issues.apache.org/jira/browse/HTTPCLIENT - HttpAsyncClient - https://issues.apache.org/jira/browse/HTTPASYNC + * HttpAsyncClient - https://issues.apache.org/jira/browse/HTTPASYNC * Review RELEASE_NOTES.txt and make sure all important issues closed since the previous release are included in the release notes @@ -105, +105 @@ == Building release artifacts == + * Check out the latest snapshot from the release branch + + {{{ + gradlew -q checkoutSnapshot + }}} + * Prepare release tag - Execute 'prepareRelease' task. - {{{ gradlew -q prepareRelease }}} @@ -122, +126 @@ }}} * Prepare RC tag - - Execute 'prepareRC' {{{ gradlew -q prepareRC @@ -156, +158 @@ * Create RC tag - Execute 'commitRC' task to commit the RC tag + {{{ + gradlew -q commitRC + }}} + * Check out RC from the RC tag + + {{{ + gradlew -q checkoutRC + }}} + + * Build RC and install it to the local Maven repository + + {{{ + gradlew -q buildRC + }}} + + This task will execute 'maven install site' as an external command. Make sure the task terminates + successfully without any error. + + * Deploy RC to the staging artifact repository + + {{{ + gradlew -q deployRC + }}} + + The build scrip will prompt for key pass-phrase if the 'signing.password' parameter has been left + empty in gradle.properties. + + This task will execute 'maven -Prelease deploy -Dmaven.test.skip=true' as an external command. + Make sure the task terminates successfully without any error. + + The 'release' profile parameter will cause release artifacts to be signed prior to deployment to Nexus + where will be held in the staging repository until they are promoted or deleted. + + The command assumes presence of a functional gpg setup on the local system. + + * Mark release artifacts as Closed in the Nexus artifact repository + + Login to the ASF Nexus repository manager at the following location + + https://repository.apache.org/index.html#welcome + + a. Login to Nexus (same login/password as for SVN and people), and navigate to the staging repository + a. Check that the correct files are present (e.g. binary, source, Javadoc), and "Close" the upload directory. + a. This will allow the files to be seen publicly, but the files won't be added to the Central Maven repo yet. + a. You can then delete any unwanted files (such as .asc.md5 and .asc.sha1) (N.B. You cannot delete files until the upload is closed). + a. Check that the files at the public URL look OK. + a. If not, you can delete them all and try again. + + Important! The public URL, which will look something like + https://repository.apache.org/content/repositories/orgapachehttpcomponents-nnn/, + should be copied into the Release Vote e-mail (see below). + --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
