From commits-return-27917-apmail-directory-commits-archive=directory.apache.org@directory.apache.org Mon Oct 11 20:45:22 2010
Return-Path: 
Delivered-To: apmail-directory-commits-archive@www.apache.org
Received: (qmail 36464 invoked from network); 11 Oct 2010 20:45:21 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 11 Oct 2010 20:45:21 -0000
Received: (qmail 50411 invoked by uid 500); 11 Oct 2010 20:45:21 -0000
Delivered-To: apmail-directory-commits-archive@directory.apache.org
Received: (qmail 50369 invoked by uid 500); 11 Oct 2010 20:45:21 -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 50362 invoked by uid 99); 11 Oct 2010 20:45:21 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Oct 2010 20:45:21 +0000
X-ASF-Spam-Status: No, hits=-1994.3 required=10.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; Mon, 11 Oct 2010 20:45:20 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9BKj0o4007359
	for ; Mon, 11 Oct 2010 20:45:00 GMT
Date: Mon, 11 Oct 2010 16:45:00 -0400 (EDT)
From: confluence@apache.org
To: commits@directory.apache.org
Message-ID: <15286881.22493.1286829900016.JavaMail.confluence@thor>
Subject: [CONF] Apache Directory Development > Releasing Skins
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated

    Releasing Skins
    Page edited by             Stefan Seelmann

                         Changes (5)

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

            1. Prepare the pProject 

            {noformat} 
$ mvn release:prepare -DdryRun=true 
{noformat} 

            2. Deploy a sSnapshot 

            {noformat} 
$ mvn deploy 

            ...

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

            3. Prepare the rRelease 

            {noformat} 
$ mvn release:clean 

            ...

            This creates a tag here: [http://svn.apache.org/viewvc/directory/skins/tags/] 

            4. Stage the rRelease 

            {noformat} 
$ mvn release:perform 

            ...

            This deploys the release to a staging repository. Go to [https://repository.apache.org/index.html#stagingRepositories] and close the staging repository. 

            6. Deploy the Site 
{noformat} 
$ cd target/checkout 
$ mvn site-deploy 
{noformat} 

This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/skins/gen-docs. 

            5. Inform dev list 
For internal projects we use a simplified release process [http://www.mail-archive.com/dev@directory.apache.org/msg29764.html]. Inform the dev list to publish (release) the Skins project. After a 4 hr grace period the Skins project can be released, therefor go to [https://repository.apache.org/index.html#stagingRepositories] and release the staging repository. 

                            Full Content

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

1. Prepare the Project

$ mvn release:prepare -DdryRun=true

2. Deploy a Snapshot

$ mvn deploy

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

3. Prepare the Release

$ mvn release:clean
$ mvn release:prepare

This creates a tag here: http://svn.apache.org/viewvc/directory/skins/tags/

4. Stage the Release

$ mvn release:perform

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

6. Deploy the Site

$ cd target/checkout
$ mvn site-deploy

This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/skins/gen-docs.

5. Inform dev list

For internal projects we use a simplified release process http://www.mail-archive.com/dev@directory.apache.org/msg29764.html. Inform the dev list to publish (release) the Skins project. After a 4 hr grace period the Skins project can be released, therefor go to https://repository.apache.org/index.html#stagingRepositories and release the staging repository.

            Change Notification Preferences

        View Online
        |
        View Changes