hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Httpcomponents Wiki] Update of "HttpComponentsCoreReleaseProcess" by SebastianBazley
Date Sat, 12 Jun 2010 23:43:37 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki" for change notification.

The "HttpComponentsCoreReleaseProcess" page has been changed by SebastianBazley.
The comment on this change is: Update for Nexus deployment.
http://wiki.apache.org/HttpComponents/HttpComponentsCoreReleaseProcess?action=diff&rev1=23&rev2=24

--------------------------------------------------

  
   * Upload the content of the staging directory, RELEASE_NOTES.txt, release packages and
corresponding MD5 and signature files to a publicly accessible web space such as people.apache.org
  
-  * Deploy pre-release snapshots to the Apache Maven snapshot repository
+  * Deploy pre-release snapshots to the Apache Nexus snapshot repository.
+    The snapshots will appear at https://repository.apache.org/content/repositories/snapshots/org/apache/httpcomponents/
+    (This is also where the Hudson snapshots appear)
  
  {{{  
  mvn deploy
@@ -213, +215 @@

  
   * Sign packages using the helper script (see previous section)
  
+  * Deploy the Maven artefacts to the Nexus staging repository
+ 
+ {{{
+ mvn deploy -P release
+ }}}
+ 
+ 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.
+ 
+ All official ASF release artifacts MUST be signed.
+ 
+   * Login to Nexus (same login/password as for SVN and people), and navigate to the staging
repository
+    * Check that the correct files are present (e.g. binary, source, Javadoc), and "Close"
the upload directory.
+    * This will allow the files to be seen publicly, but the files won't be added to the
Central Maven repo yet.
+    * 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).
+    * Check that the files at the public URL look OK.
+    * If not, you can delete them all and try again.
+ 
+   * 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).
+ 
  == Release vote ==
  
   * Upload RELEASE_NOTES.txt, release packages and corresponding MD5 and signature files
to a publicly accessible web space such as people.apache.org
@@ -223, +248 @@

  [VOTE] HttpComponents Core ${VERSION} release
  
  Please vote on releasing these packages as HttpComponents Core ${VERSION}. The vote is open
for the 
- next 72 hours, and only votes from HttpComponents PMC members are binding. The vote passes
if at least 
+ 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:
@@ -232, +257 @@

  Release notes:
  [link]
  
+ Maven artefacts:
+ [link]
+ 
+ SVN tag:
+ [link]
  --------------------------------------------------------------------------
   Vote:  HttpComponents Core ${VERSION} release
   [ ] +1 Release the packages as HttpComponents Core ${VERSION}.
@@ -241, +271 @@

  
  == Release vote result ==
  
-  * Tally votes after the voting deadline elapsed (usually 72 hours)
+  * Tally votes after the voting deadline elapsed (usually 72 hours, but may be extended
if not enough votes have been cast)
  
   * If the vote fails, address concerns / problems stated as reasons for negative votes and
re-vote
+    * Login to Nexus and "Delete" the staged uploads
  
   * If the vote succeeds, send results to dev@hc.apache.org and private@hc.apache.org
  
@@ -289, +320 @@

        <filePermissions>644</filePermissions>
      </server>
      <server>
-       <id>apache.releases</id>
+       <id>apache.releases.https</id>
        <username>${your apache id}</username>
        <passphrase>${your GPG pass phrase}</passphrase>
        <directoryPermissions>775</directoryPermissions>
        <filePermissions>644</filePermissions>
      </server>
      <server>
-       <id>apache.snapshots</id>
+       <id>apache.snapshots.https</id>
        <username>${your apache id}</username>
        <passphrase>${your GPG pass phrase}</passphrase>
        <directoryPermissions>775</directoryPermissions>
@@ -308, +339 @@

  
   * Deploy release artifacts to the Maven2 repository
  
+ Login to the Nexus repository, and "Promote" the staging directory.
+ This will cause the artifacts to be released to the Central Maven repo.
- {{{
- mvn deploy -P release
- }}}
- 
-   The 'release' profile parameter will cause release artifacts to be signed prior to deployment
to the remote 
-   repository
- 
-   The command assumes presence of a functional gpg setup on the local system
- 
-   Make sure to enter your GPG Passphrase when prompted for while deploying the artifacts.
All official ASF 
-   release artifacts MUST be signed
- 
- {{{
- [INFO] [gpg:sign {execution: sign-artifacts}]
- GPG Passphrase:****************
- }}}
  
   * Deploy release packages
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message