directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r875299 - in /websites/staging/directory/trunk/content: ./ apacheds/developer-guide.html apacheds/index.html
Date Mon, 19 Aug 2013 13:29:44 GMT
Author: buildbot
Date: Mon Aug 19 13:29:44 2013
New Revision: 875299

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/apacheds/index.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug 19 13:29:44 2013
@@ -1 +1 @@
-1515406
+1515407

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 Mon Aug 19 13:29:44
2013
@@ -127,6 +127,30 @@
 <h1 id="developers-guide">Developers Guide</h1>
 <h2 id="getting-the-source-building-the-trunks">Getting the source, Building the trunks</h2>
 <p>To get the source, build the <em>trunks</em> and get along with Maven,
follow the instruction given in this page: <a href="advanced-ug/0.2-building-trunks.html">AUG
: 0.2. Building trunks</a></p>
+<h2 id="versioning-scheme">Versioning Scheme</h2>
+<p>The version number of <em>ApacheDS</em> has the following form:</p>
+<DIV class="info" markdown="1">
+    &lt;major>.&lt;minor>.&lt;micro> \[-M&lt;milestone number>
or -RC&lt;release candidate number>]
+</DIV>
+
+<p>This scheme has three number components:</p>
+<ul>
+<li>The <strong>major</strong> number increases when there are incompatible
changes in the API.</li>
+<li>The <strong>minor</strong> number increases when a new feature is introduced.</li>
+<li>The <strong>micro</strong> number increases when a bug or a trivial
change is made.</li>
+</ul>
+<p>and an optional label that indicates the maturity of a release:</p>
+<ul>
+<li><strong>M</strong> (Milestone) means the feature set can change at
any time in the next milestone releases. The last milestone release becomes the first release
candidate after a vote.</li>
+<li><strong>RC</strong> (Release Candidate) means the feature set is frozen
and the next RC releases will focus on fixing problems unless there is a serious flaw in design.
The last release candidate becomes the first GA release after a vote.</li>
+<li>No label implies <strong>GA</strong> (General Availability), which
means the release is stable enough and therefore ready for production environment.</li>
+</ul>
+<DIV class="info" markdown="1">
+    A **stable** version is a version with a frozen set of features, and a frozen **API**.
We don't release a version if all the integration tests are not passing, so any release should
be considered stable enogh to be used.<BR/>
+    Although we may add new features between two milestones, and the data structure may change,
which may imply that the data have to be extracted and reimported in order for the server
to be operational.<BR/>
+    The configuration might also evolve between two versions.
+</DIV>
+
 <h2 id="coding-standards">Coding standards</h2>
 <p>The applicable coding standards for ADS 1.5 are described in <a href="coding-standards.html">Coding
Standards</a></p>
 <p>There are some more rules, as we are using <strong>Java 5</strong> now
:</p>

Modified: websites/staging/directory/trunk/content/apacheds/index.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/index.html (original)
+++ websites/staging/directory/trunk/content/apacheds/index.html Mon Aug 19 13:29:44 2013
@@ -125,35 +125,12 @@
 
 
 
-    <h1 id="apachedswzxhzdk3">ApacheDS&trade;</h1>
+    <h1 id="apachedswzxhzdk1">ApacheDS&trade;</h1>
 <p><strong>ApacheDS&trade;</strong> is an extensible and embeddable
directory server entirely written in Java, which has been certified LDAPv3 compatible by the
Open Group. Besides LDAP it supports Kerberos 5 and the Change Password Protocol. It has been
designed to introduce triggers, stored procedures, queues and views to the world of LDAP which
has lacked these rich constructs.</p>
-<h2 id="versioning-scheme">Versioning Scheme</h2>
-<p>The version number of <em>ApacheDS</em> has the following form:</p>
 <DIV class="info" markdown="1">
-    &lt;major>.&lt;minor>.&lt;micro> \[-M&lt;milestone number>
or -RC&lt;release candidate number>]
-</DIV>
-
-<p>This scheme has three number components:</p>
-<ul>
-<li>The <strong>major</strong> number increases when there are incompatible
changes in the API.</li>
-<li>The <strong>minor</strong> number increases when a new feature is introduced.</li>
-<li>The <strong>micro</strong> number increases when a bug or a trivial
change is made.</li>
-</ul>
-<p>and an optional label that indicates the maturity of a release:</p>
-<ul>
-<li><strong>M</strong> (Milestone) means the feature set can change at
any time in the next milestone releases. The last milestone release becomes the first release
candidate after a vote.</li>
-<li><strong>RC</strong> (Release Candidate) means the feature set is frozen
and the next RC releases will focus on fixing problems unless there is a serious flaw in design.
The last release candidate becomes the first GA release after a vote.</li>
-<li>No label implies <strong>GA</strong> (General Availability), which
means the release is stable enough and therefore ready for production environment.</li>
-</ul>
-<p><strong>ApacheDS</strong> 1.0 is considered a dead branch. <strong>ApacheDS</strong>
<strong>1.5.X</strong> are intermediary versions toward <strong>ApacheDS</strong>
<strong>2.0</strong>, which is currently being developped.</p>
-<DIV class="tip" markdown="1">
-    Users should start with the latest *2.0* version, even if it's not stabilized yet. 
-</DIV>
+**ApacheDS** 1.0 is considered a dead branch. **ApacheDS** **1.5.X** are intermediary versions
toward **ApacheDS** **2.0**, which is currently being developped.
 
-<DIV class="info" markdown="1">
-    A **stable** version is a version with a frozen set of features, and a frozen **API**.
We don't release a version if all the integration tests are not passing, so any release should
be considered stable enogh to be used.<BR/>
-    Although we may add new features between two milestones, and the data structure may change,
which may imply that the data have to be extracted and reimported in order for the server
to be operational.<BR/>
-    The configuration might also evolve between two versions.
+Users should start with the latest *2.0* version, even if it's not stabilized yet. 
 </DIV>
 
 <h2 id="important-new-features-in-apacheds-20">Important new features in ApacheDS 2.0</h2>



Mime
View raw message