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=2&rev2=3

  cp gradle.properties.template gradle.properties
  }}}
  
- Edit gradle.properties file and update MAVEN_HOME, HC_DEV and signing.keyId 
properties
+ Edit gradle.properties file and update 'MAVEN_HOME', 'HC_DEV' and 'signing.*' 
properties
  
  'MAVEN_HOME' must refer to the local Maven installation
  
@@ -95, +95 @@

  
  'signing.keyId' must contain id of the personal GPG key to be used for 
signing release artifacts. 
  
+ 'signing.secretKeyRingFile' must refer to the personal GPG ring file.
+ 
- 'signing.password' may be left empty. In this case the script will be 
prompting for a pass phrase every time access to the key is needed   
+ 'signing.password' may be left empty. In this case the script will be 
prompting for a pass phrase 
+ every time access to the key is needed.   
  
   * Make sure that the scripts are valid by listing available tasks
  
@@ -139, +142 @@

  RC tag to be created: 
https://svn.apache.org/repos/asf/httpcomponents/httpcore/tags/4.3.1-RC1
  }}}
  
- Optionally run 'previewRC' task to see what changes have been made to the 
current snapshot. 
+ Optionally run preview task to see what changes have been made to the current 
snapshot. 
  The RC tag will be created by copying those changes to the tag location 
  
  {{{
@@ -183, +186 @@

  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.
  
@@ -194, +194 @@

  
  The command assumes presence of a functional gpg setup on the local system.
  
-  * Mark release artifacts as Closed in the Nexus artifact repository
+  * Mark release artifacts as 'Closed' in the Nexus artifact repository
  
  Login to the ASF Nexus repository manager at the following location
  
@@ -211, +211 @@

  
https://repository.apache.org/content/repositories/orgapachehttpcomponents-nnn/,
  should be copied into the Release Vote e-mail (see below).
  
+  * Check out staging dist repository
+ 
+ {{{
+ gradlew -q checkoutDistStage
+ }}} 
+ 
+  * Assemble release dist packages
+ 
+ {{{
+ gradlew -q assemble
+ }}} 
+ 
+ The build scrip will prompt for key pass-phrase if the 'signing.password' 
parameter has been left 
+ empty in gradle.properties.
+ 
+  * Prepare dist packages for import into the staging repository
+ 
+ {{{
+ gradlew -q prepareDist
+ }}}
+ 
+ Optionally run preview task to see what files have been scheduled for import 
into the staging 
+ repository.  
+ 
+ {{{
+ gradlew -q previewDist
+ }}}
+ 
+ {{{
+ Local changes for release dist 
https://dist.apache.org/repos/dist/dev/httpcomponents/
+ 
/home/oleg/src/apache.org/httpcomponents/release-httpcore-4.3.1/build/repos-dist-dev-httpcomponents
+ A       httpcore-4.3.1-RC1
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.zip.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.zip
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.tar.gz.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.zip
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.zip
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.tar.gz
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.tar.gz.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.tar.gz.asc
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.tar.gz.asc
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.zip.asc
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.tar.gz.asc
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.zip.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.tar.gz.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.tar.gz
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.zip.md5
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-osgi-bin.tar.gz
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-bin.zip.asc
+ A       httpcore-4.3.1-RC1/RELEASE_NOTES-4.3.x.txt
+ A       httpcore-4.3.1-RC1/httpcomponents-core-4.3.1-src.zip.asc
+ }}}
+ 
+  * Commit dist packages to the staging repository
+ 
+ {{{
+ gradlew -q commitDist
+ }}}
+ 
+ == Release vote ==
+ 
+  * Prepare release vote content
+ 
+ {{{
+ gradlew -q prepareVote
+ }}}
+ 
+ {{{
+ ----------------8<-------------[ cut here ]------------------
+ [VOTE] Release HttpComponents Core 4.3.1 based on RC1
+ 
+ Please vote on releasing these packages as HttpComponents Core 4.3.1.
+ The vote is open for the at least 72 hours, and only votes from
+ HttpComponents PMC members are binding. The vote passes if at least
+ three binding +1 votes are cast and there are more +1 than -1 votes.
+ 
+ Packages:
+ https://dist.apache.org/repos/dist/dev/httpcomponents/httpcore-4.3.1-RC1
+ revision 3948
+ 
+ Release notes:
+ 
https://dist.apache.org/repos/dist/dev/httpcomponents/httpcore-4.3.1-RC1/RELEASE_NOTES-4.3.x.txt
+ 
+ Maven artefacts:
+ [link]
+ 
+ SVN tag:
+ https://svn.apache.org/repos/asf/httpcomponents/httpcore/tags/4.3.1-RC1
+ revision 1551921
+ 
+ --------------------------------------------------------------------------
+ Vote: HttpComponents Core 4.3.1 release
+ [ ] +1 Release the packages as HttpComponents Core 4.3.1.
+ [ ] -1 I am against releasing the packages (must include a reason).
+ ----------------8<-------------[ cut here ]------------------
+ }}}
+ 
+  * Call release vote on [email protected]  
+ 
+ Prepare release vote message from the generated release vote content. Make 
sure to insert 
+ Maven artefacts link taken from the Nexus Repository Manager. Send the 
message to [email protected]
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to