Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DCCBD200B2B for ; Tue, 28 Jun 2016 13:40:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DB57A160A56; Tue, 28 Jun 2016 11:40:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 61FFC160A06 for ; Tue, 28 Jun 2016 13:40:02 +0200 (CEST) Received: (qmail 88492 invoked by uid 500); 28 Jun 2016 11:40:01 -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 88483 invoked by uid 99); 28 Jun 2016 11:40:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2016 11:40:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C42FDCC4CE for ; Tue, 28 Jun 2016 11:40:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.513 X-Spam-Level: X-Spam-Status: No, score=0.513 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-1.287] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Epj6qyNsK9Kx for ; Tue, 28 Jun 2016 11:39:59 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 40E9B5F297 for ; Tue, 28 Jun 2016 11:39:58 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 65AADE010F for ; Tue, 28 Jun 2016 11:39:57 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 615E63A1275 for ; Tue, 28 Jun 2016 11:39:57 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r991594 - in /websites/staging/directory/trunk/content: ./ apacheds/developer-guide.html api/developer-guide.html Date: Tue, 28 Jun 2016 11:39:57 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160628113957.615E63A1275@svn01-us-west.apache.org> archived-at: Tue, 28 Jun 2016 11:40:04 -0000 Author: buildbot Date: Tue Jun 28 11:39:57 2016 New Revision: 991594 Log: Staging update by buildbot for directory Modified: websites/staging/directory/trunk/content/ (props changed) websites/staging/directory/trunk/content/apacheds/developer-guide.html websites/staging/directory/trunk/content/api/developer-guide.html Propchange: websites/staging/directory/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Tue Jun 28 11:39:57 2016 @@ -1 +1 @@ -1749272 +1750479 Modified: websites/staging/directory/trunk/content/apacheds/developer-guide.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/developer-guide.html (original) +++ websites/staging/directory/trunk/content/apacheds/developer-guide.html Tue Jun 28 11:39:57 2016 @@ -457,13 +457,28 @@ $
Publish Source Distribution Package
-

First of all, create a new directory on people.apache.org/public_html to store the pacckages :

-
$ ssh people.apache.org
-$ mkdir public_html/apacheds-<version>
-$ exit
+

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by the other committers, in order to be chekced while validating the release. As the ~/people.apache.org server is not anymore available for that purpose, we use the distribution space for that purpose.

+

If you haven't checked out this space, do it now :

+
$ mkdir -p ~/apacheds/dist/dev/directory
+$ svn co https://dist.apache.org/repos/dist/dev/directory ~/apacheds/dist/dev/directory
+
+ + +

That will checkout the full project distributions.

+

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

+
$ mkdir -p ~/apacheds/dist/dev/directory/apacheds
+$ svn co https://dist.apache.org/repos/dist/dev/directory/apacheds ~/apacheds/dist/dev/directory/apacheds
+
+ -$ cd target/checkout/target -$ scp apacheds-parent-<version>-source-release.zip* people.apache.org:public_html/apacheds-<version> +

Now, create a sub-directory for the version you have generated (here, for version 2.0.0-M22) :

+
$ mkdir ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
+
+ + +

and copy the packages and signature to this area :

+
$ cd target/checkout/target
+$ cp apacheds-parent-<version>-source-release.zip* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
 
@@ -471,8 +486,8 @@ $ scp apacheds-parent-<version>-so

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 working. Then check that the server is correctly running.

Create the installers

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

-
$ cd apacheds/target/checkout/installers
-$ mvn clean install -Pinstallers
+
$ cd apacheds/target/checkout/installers
+$ mvn clean install -Pinstallers
 
@@ -480,67 +495,58 @@ $ mvn We are meant to create all the installers. It's possible to create installers for a specific platform by using a different profile : - o Debian : mvn clean install -Pdebian - o Rpm : mvn clean install -Prpm - o Windows : mvn clean install -Pwindows - o Mac OS X : mvn clean install -Pmac - o Binary : mvn clean install -Pbin - o Archive : mvn clean install -Parchive +
    +
  • Debian : mvn clean install -Pdebian
  • +
  • Rpm : mvn clean install -Prpm
  • +
  • Windows : mvn clean install -Pwindows
  • +
  • Mac OS X : mvn clean install -Pmac
  • +
  • Binary : mvn clean install -Pbin
  • +
  • Archive : mvn clean install -Parchive
  • +
This will build only one single target.

Sign those installers using the sign.sh script, and copy them in people.apache.org/public_html/apacheds-

-
$ cd apacheds/target/checkout/target/installers/target/installers
-$ scp apacheds-<version>* people.apache.org:public_html/apacheds-<version>
+
$ cd apacheds/target/checkout/target/installers/target/installers
+$ cp apacheds-<version>* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22
 

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 nsis if you don't want to use many different servers.

-

Update your index.html file on people.apache.org/public_html to make the packages visible. Here is an example of possible content :

-
<h2>Last Directory Server <version> sources tarballs</h2>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-parent-<version>-source-release.zip">apacheds-parent-<version>-source-release.zip</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-parent-<version>-source-release.zip.asc">apacheds-parent-<version>-source-release.zip.asc</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-parent-<version>-source-release.zip.md5">apacheds-parent-<version>-source-release.zip.md5</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-parent-<version>-source-release.zip.sha1">apacheds-parent-<version>-source-release.zip.sha1</a><br>
-
-<h2>Last Directory Server <version> installers</h2>
-    <h3>Plain 32 bits binary installers</h3>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-32bit.bin">apacheds-<version>-32bit.bin</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-32bit.bin.asc">apacheds-<version>-32bit.bin.asc</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-32bit.bin.md5">apacheds-<version>-32bit.bin.md5</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-32bit.bin.sha1">apacheds-<version>-32bit.bin.sha1</a><br/>
-    <br/>
-    <h3>Plain 64 bits installers</h3>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-64bit.bin">apacheds-<version>-64bit.bin</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-64bit.bin.asc">apacheds-<version>-64bit.bin.asc</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-64bit.bin.md5">apacheds-<version>-64bit.bin.md5</a><br/>
-    <img src="/icons/compressed.gif" alt="[   ]"><a href="apacheds-<version>/apacheds-<version>-64bit.bin.sha1">apacheds-<version>-64bit.bin.sha1</a><br/>
-    <br/>
-...
-
- -
Vote

Start a 72h vote at the dev mailing list.

Release

If the vote succeeds Apacheds project can be released.

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

Move the distribution packages (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)

-

The best solution would be to checkout the directory in people.apache.org, to copy the packages in the right place, and to check in the changes :

-
$ ssh people.apache.org
-# svn co https://dist.apache.org/repos/dist/release/directory/apacheds/dist/ apacheds-dist
-# cd apacheds-dist
-# mkdir <version>
-# cp ../public_html/apacheds-<version>/* <version>
-# svn ci <version>
-...
-# exit
+

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by users. We use the distribution space for that purpose.

+

Move the distribution packages (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)

+

If you haven't checked out this space, do it now :

+
$ mkdir -p ~/apacheds/dist/release/directory
+$ svn co https://dist.apache.org/repos/dist/release/directory ~/apacheds/dist/release/directory
+
+ + +

That will checkout the full project distributions.

+

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

+
$ mkdir -p ~/apacheds/dist/release/directory/apacheds/dist
+$ svn co https://dist.apache.org/repos/dist/release/directory/apacheds/dist ~/apacheds/dist/release/directory/apacheds/dist
+
+ + +

Then move the packages from 'dev' to 'release' :

+
# cd dist/release/directory/apacheds/dist
+# cp ~/apacheds/dist/dev/directory/apacheds/<version> .
+# svn add <version>
+# svn ci <version>
+...
+# exit
 $
 
-

The packages should now be available on http://www.us.apache.org/dist/directory/api/dist/

+

The packages should now be available on http://www.us.apache.org/dist/directory/apacheds/dist/

Deploy the Javadocs and XRef

We now can deploy the generated Javadoc and cross-reference pages. They are generated in the following directory :

target/checkout/target/site

Modified: websites/staging/directory/trunk/content/api/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/api/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/api/developer-guide.html Tue Jun 28 11:39:57 2016
@@ -458,34 +458,34 @@ stty echo
 
 
 

Publish Source and Binary Distribution Packages

-

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by the other committers, in order to be chekced while validating the release. As the ~/people.apache.org server is not anymore available for that purpose, we use the distribution space for that purpose.

-

If you haven't chekced out this space, do it now :

-
$ mkdir -p ~/apacheds/dist/dev/directory
-$ svn co https://dist.apache.org/repos/dist/dev/directory ~/apacheds/dist/dev/directory
+

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by the other committers, in order to be checked while validating the release. As the ~/people.apache.org server is not anymore available for that purpose, we use the distribution space for that purpose.

+

If you haven't checked out this space, do it now :

+
$ mkdir -p ~/apacheds/dist/dev/directory
+$ svn co https://dist.apache.org/repos/dist/dev/directory ~/apacheds/dist/dev/directory
 

That will checkout the full project distributions.

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

-
$ mkdir -p ~/apacheds/dist/dev/directory/api
-$ svn co https://dist.apache.org/repos/dist/dev/directory/api ~/apacheds/dist/dev/directory/api
+
$ mkdir -p ~/apacheds/dist/dev/directory/api
+$ svn co https://dist.apache.org/repos/dist/dev/directory/api ~/apacheds/dist/dev/directory/api
 

Now, create a sub-directory for the version you have generated (here, for version 1.0.0-RC1) :

-
$ mkdir ~/apacheds/dist/dev/directory/api/1.0.0-RC1
+
$ mkdir ~/apacheds/dist/dev/directory/api/1.0.0-RC1
 

and copy the packages and signature to this area :

-
$ cd distributions/target
-$ cp apache-ldap-api-<version>-* ~/apacheds/dist/dev/directory/api/1.0.0-RC1
+
$ cd distributions/target
+$ cp apache-ldap-api-<version>-* ~/apacheds/dist/dev/directory/api/1.0.0-RC1
 

Last, not least, commit your changes

-
$ scn add ~/apacheds/dist/dev/directory/api/1.0.0-RC1
-$ scn ci ~/apacheds/dist/dev/directory/api/1.0.0-RC1 -m "Apache LDAP API 1.0.0-RC1 packages"
+
$ svn add ~/apacheds/dist/dev/directory/api/1.0.0-RC1
+$ svn ci ~/apacheds/dist/dev/directory/api/1.0.0-RC1 -m "Apache LDAP API 1.0.0-RC1 packages"
 
@@ -499,18 +499,28 @@ $ scn Release

If the vote succeeds LDAP API project can be released.

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

+

The sources, binaries and their signatures, have to be pushed in a place where they can be downloaded by usersWe use the distribution space for that purpose.

Move the distribution packages (sources and binaries) to the dist SVN repository: https://dist.apache.org/repos/dist/release/directory/api/dist/$(version)

-

The best solution would be to checkout the directory in people.apache.org, to copy the packages in the right place, and to check in the changes (we assume you have a dist-all/api directory in your home directory. if not, create it) :

-
$ ssh people.apache.org
-# cd dist-all/api
-# svn co https://dist.apache.org/repos/dist/release/directory/api/dist/ dist
-# cd dist
-# mkdir <version>
-# cp ~/public_html/ldap-api-<version>/* <version>
-# svn add <version>
-# svn ci <version>
-...
-# exit
+

If you haven't checked out this space, do it now :

+
$ mkdir -p ~/apacheds/dist/release/directory
+$ svn co https://dist.apache.org/repos/dist/release/directory ~/apacheds/dist/release/directory
+
+ + +

That will checkout the full project distributions.

+

You may want to checkout only the part that you are going to generate, to avoid getting Gb of data :

+
$ mkdir -p ~/apacheds/dist/release/directory/api/dist
+$ svn co https://dist.apache.org/repos/dist/release/directory/api/dist ~/apacheds/dist/release/directory/api/dist
+
+ + +

Then move the packages from 'dev' to 'release' :

+
# cd dist/release/directory/api/dist
+# cp ~/apacheds/dist/dev/directory/api/<version> .
+# svn add <version>
+# svn ci <version>
+...
+# exit
 $