From commits-return-36197-apmail-directory-commits-archive=directory.apache.org@directory.apache.org Wed Feb 27 14:56:25 2013 Return-Path: X-Original-To: apmail-directory-commits-archive@www.apache.org Delivered-To: apmail-directory-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76887EE5B for ; Wed, 27 Feb 2013 14:56:25 +0000 (UTC) Received: (qmail 76959 invoked by uid 500); 27 Feb 2013 14:56:25 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 76890 invoked by uid 500); 27 Feb 2013 14:56:25 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 76883 invoked by uid 99); 27 Feb 2013 14:56:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 14:56:25 +0000 X-ASF-Spam-Status: No, hits=-1994.3 required=5.0 tests=ALL_TRUSTED,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MIME_HTML_ONLY X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 14:56:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id r1REu0vY019150 for ; Wed, 27 Feb 2013 14:56:00 GMT Date: Wed, 27 Feb 2013 09:56:00 -0500 (EST) From: confluence@apache.org To: commits@directory.apache.org Message-ID: <33167063.34201.1361976960035.JavaMail.confluence@thor> Subject: [CONF] Apache Directory Development > Releasing ApacheDS MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Auto-Submitted: auto-generated X-Virus-Checked: Checked by ClamAV on apache.org

Releasing ApacheDS

Page edited by Emmanuel L=C3=A9charny


Changes (3)

=20 =20
=20 <= /tr> =20
...

{noformat}
$ cd apacheds/target/checkout/
$ mvn clean install -Pinstall= ers
{noformat}
...
Sign those installers using t= he sigh.sh script, and copy them in people.apache.org/public.html

=
{noformat}
$ cd apacheds/target/checkout/target/installers/target= /installers
$ scp apacheds-2.0.0-M11* people.apache.org:public_html/apa= cheds-2.0.0-M11
{noformat}

Note : you will need a Debian, a Fedora and a Windows server to gener= ate dedicated binaries for those platforms, or you can use rpmbuild, dpkg o= r nsis if you don't want to use many different servers.

h3. 9. Vote
Start a 72h v= ote at the dev mailing list.
...

Full Content

Introduction

This will show you how to build and release the ApacheDS subproject. Ke= ep an eye out for warning and note sections that show version specific diff= erences in this process.

Manual Step

Some things have not yet been automated with maven and require users to = manually edit some files. Below are the steps to follow.

Update th= e apacheds/pom.xml

The current apacheds/pom.xml contains references to LDAP API SNAPSHOTs, = which is not good. You have to bump up those references to the latest LDAP-= API version.

Update service/apacheds.sh and service/apacheds.bat

Edit the apacheds.sh/bat files in the service project directory to updat= e the revision numbers used in that file to reference non-SNAPSHOT releases= .

Release process

Since we are using Nexus for releases the release process is as follows = (see also http://www.apac= he.org/dev/publishing-maven-artifacts.html#staging-maven).

1. Test the Project<= /h3>
$ mvn release:prepare -DdryRun=3Dtrue

Replace the version by the new version. Be careful, and remove the 'apac= heds-parent-' which is proposed for the new tag. We should just use the ver= sion number.

2. Deploy a Snapsho= t

$ mvn deploy

This is useful to verify your settings in ~/.m2/settings.xml (Nexus pass= word and GPG key)

3. Prepare the Re= lease

$ mvn release:clean
$ mvn release:prepare

This creates a tag here: http://svn.apac= he.org/viewvc/directory/apacheds/tags/

4. Stage the Releas= e

$ mvn release:perform

This deploys the release to a staging repository. Go to https://repository.apache.org/index.html#stagingRepo= sitories and close the staging repository.

5. Build the Site

$ cd target/checkout
$ mvn site

This creates and deploys the site via ssh to people.apache.org/www/direc= tory.apache.org/apacheds/gen-docs.

Edit the people.apache.org/www/directory.apache.org/apacheds/gen-docs/in= dex.html file and add the deployed site to the list.

3D""Now, you have to sign the binary package= s which are in apacheds/target/checkout/target.

Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the= key ID)

6. Publish Source and Binary Distribution Packages

$ cd target/checkout/target
$ scp apacheds-parent-<version>-source-release.zip* people.apache.org=
:public_html/apacheds-2.0.0-M10

7. Test the new v= ersion

The best way to do that is to download the sources, extract them, build = the server and the installers, and check if the installers are correctly wo= rking. Then check that the server is correctly running.

8. Create the i= nstallers

We now have to create the installers. Go into the target/checkout direct= ory and run :

$ cd apacheds/target/checkout/
$ mvn clean install -Pinstallers

This will create the installers in the target/checkout/installers/target= /installers directory

Sign those installers using the sigh.sh script, and copy them in people.= apache.org/public.html

$ cd apacheds/target/checkout/target/installers/target/installers
$ scp apacheds-2.0.0-M11* people.apache.org:public_html/apacheds-2.0.0-M11

Note : you will need a Debian, a Fedora and a Windows server to generate= dedicated binaries for those platforms, or you can use rpmbuild, dpkg or n= sis if you don't want to use many different servers.

9. Vote

Start a 72h vote at the dev mailing list.

10. Release

If the vote succeeds Apacheds project can be released.

Go to https://repository.apache.o= rg/index.html#stagingRepositories and release the staging repository so= all artifacts are published to Maven central.

Move the distribution packages to the dist SVN repository: https://dist.apache.org/repos/dis= t/release/directory/apacheds/dist/$(version)
Move the sources releases to the dist SVN repository: https://dist.apache.org/repos/dist/release/dir= ectory/apacheds/$(version)