Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 06 Apr 2011 22:14:19 -0000
Message-ID: <20110406221419.26258.20280@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCassandra_Wiki=5D_Update_of_=22HowToPublishToMavenCentral=22?=
 =?utf-8?q?_by_StephenConnolly?=

Dear Wiki user,

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

The "HowToPublishToMavenCentral" page has been changed by StephenConnolly.
http://wiki.apache.org/cassandra/HowToPublishToMavenCentral?action=3Ddiff&r=
ev1=3D5&rev2=3D6

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

  =

  Please read the [[http://www.apache.org/dev/publishing-maven-artifacts.ht=
ml#common|Common Procedures]] for details of how to close, drop and release=
 stanging repositories.
  =

+ =3D=3D Making a release =3D=3D
+ =

+ Note: this process assumes that you are working on a stream where [[https=
://issues.apache.org/jira/browse/CASSANDRA-1851|CASSANDRA-1851]] has been a=
pplied.
+ =

+ To make a release:
+ =

+  1. Make a full build from a real clean base, i.e. use the following sequ=
ence of commands:
+   {{{
+ ant realclean
+ ant publish -Drelease=3Dtrue
+ }}}
+  That will build all the required artifacts and sign them with your GPG s=
ignature and publish them to a staging repository on [[http://repository.ap=
ache.org|repository.apache.org]]
+ =

+  2. Login to [[http://repository.apache.org|repository.apache.org]] with =
your Apache LDAP username and password. Select ''Staging Repositories'' and=
 find
+  the open repository that you just deployed to and close it. Make note of=
 the URL of the staging repository (it will look something like {{{https://=
repository.apache.org/content/repositories/''staging repository id''/}}}
+  3. Goto [[http://svn.apache.org/viewvc/cassandra/|The ViewVC for Apache'=
s SVN server]] and get the URLS for CHANGES.txt and NEWS.txt for the versio=
n you want to release. Shorten these URLs using [[http://s.apache.org|Apach=
e's URL shortening service]].
+  3. Goto [[https://issues.apache.org/jira/browse/CASSANDRA?selectedTab=3D=
com.atlassian.jira.plugin.system.project%3Aversions-panel|The Versions tab =
in JIRA]]. Select the Version being released, and Copy the Release Notes UR=
L. It will look something like {{{https://issues.apache.org/jira/secure/Rel=
easeNote.jspa?projectId=3D12310865&version=3D#########}}}. Shorten that url=
 using [[http://s.apache.org|Apache's URL shortening service]].
+  3. Call a release vote on the [[mailto:dev@cassandra.apache.org|dev@cass=
andra.apache.org]] mailing list. e.g.
+   {{{
+ Subject: [VOTE] Release Apache Cassandra X.Y.Z
+ =

+ I propose the following artifacts for release as X.Y.Z.
+ =

+ SVN: https://svn.apache.org/repos/asf/cassandra/''path to branch''@''peg =
revision''
+ Artifacts: https://repository.apache.org/content/repositories/''staging r=
epository id''/org/apache/cassandra/apache-cassandra/X.Y.Z/
+ Staging repository: https://repository.apache.org/content/repositories/''=
staging repository id''/
+ =

+ The will remain open for 72 hours, (longer if need be).
+ =

+ [1]: ''http://s.apache.org/link'' (CHANGES.txt)
+ [2]: ''http://s.apache.org/link'' (NEWS.txt)
+ [3]: ''http://s.apache.org/link'' (Release notes from JIRA)
+ =

+ }}}
+=20