CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Developers Guide — Apache Directory</title> <link href="/css/common.css" rel="stylesheet" type="text/css"/> <link href="/css/apacheds.css" rel="stylesheet" type="text/css"/> <link rel="shortcut icon" href="/images/server-icon_16x16.png" /> <script src="https://www.apachecon.com/event-images/snippet.js"></script> </head> <body> <div class="top-bottom-spacer"></div> <div id="container"> <div id="header"> Apache Directory <a href="/"><div id="headerClick"></div></a> <div id="subProjectsNavBar"> <a href="/"> Main </a>  |  <a href="/apacheds/"> ApacheDS </a>  |  <a href="/studio/"> Studio </a>  |  <a href="/api/"> LDAP API </a>  |  <a href="/mavibot/"> Mavibot </a>  |  <a href="/scimple/"> SCIMple </a>  |  <a href="/fortress/"> Fortress </a>  |  <a href="/kerby/"> Kerby </a> </div> </div> <div id="content"> <div id="leftColumn"> <div id="navigation"> <a class="acevent" data-format="wide" data-width="170"></a> <h5>ApacheDS 2.0</h5> <ul> <li><a href="/apacheds/">Home</a></li> <li><a href="/apacheds/news.html">News</a></li> <li><a href="/apacheds/features.html">Features</a></li> <li><a href="/apacheds/production-readiness.html">Production Readiness</a></li> </ul> <h5>Downloads</h5> <ul> <li><a href="/apacheds/downloads.html">ApacheDS 2.0.0.AM27</a>  <img src="/images/new_badge.svg" alt="" style="margin-bottom:-3px;" border="0"></li> <li><a href="/apacheds/download-old-versions.html">Older versions</a></li> </ul> <h5>Documentation</h5> <ul> <li><a href="/apacheds/basic-user-guide.html">Basic User Guide </a></li> <li><a href="/apacheds/advanced-user-guide.html">Advanced User Guide</a></li> <li><a href="/apacheds/developer-guide.html">Developer Guide</a></li> <li><a href="/apacheds/kerberos-user-guide.html">Kerberos User Guide</a></li> <li><a href="/apacheds/configuration/ads-2.0-configuration.html">Configuration</a></li> <li><a href="/apacheds/gen-docs/latest/apidocs">JavaDocs</a></li> <li><a href="/apacheds/gen-docs/latest/xref">Cross-Reference</a></li> </ul> <h5>Support</h5> <ul> <li><a href="/mailing-lists-and-irc.html">Mailing Lists & IRC</a></li> <li><a href="/sources.html">Sources</a></li> <li><a href="/issue-tracking.html">Issue Tracking</a></li> <li><a href="/commercial-support.html">Commercial Support</a></li> </ul> <h5>Community</h5> <ul> <li><a href="/contribute.html">How to Contribute</a></li> <li><a href="/team.html">Team</a></li> <li><a href="/original-project-proposal.html">Original Project Proposal</a></li> <li><a href="/special-thanks.html" class="external-link" rel="nofollow">Special Thanks</a></li> </ul> <h5>About Apache</h5> <ul> <li><a href="https://www.apache.org/">Apache</a></li> <li><a href="https://www.apache.org/licenses/">License</a></li> <li><a href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li> <li><a href="https://www.apache.org/foundation/thanks.html">Thanks</a></li> <li><a href="https://www.apache.org/security/">Security</a></li> </ul> </div> </div> <div id="rightColumn"> <h1 id="developers-guide">Developers Guide</h1> <h2 id="getting-the-source-building-the-trunks">Getting the source, Building the trunks</h2> To get the source, build the trunks 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> <h2 id="versioning-scheme">Versioning Scheme</h2> The version number of ApacheDS has the following form: <DIV class="info" markdown="1"> <major>.<minor>.<micro> \[-M<milestone number> or -RC<release candidate number>] </DIV> This scheme has three number components: <ul> <li>The major number increases when there are incompatible changes in the API.</li> <li>The minor number increases when a new feature is introduced.</li> <li>The micro number increases when a bug or a trivial change is made.</li> </ul> and an optional label that indicates the maturity of a release: <ul> <li>M (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>RC (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 GA (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. 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. The configuration might also evolve between two versions. </DIV> <h2 id="coding-standards">Coding standards</h2> The applicable coding standards for ADS 2.0 are described in <a href="coding-standards.html">Coding Standards</a> There are some more rules, as we are using Java 8 now : <ul> <li>Use generics as much as you can. Generic are a good way to avoid casting, and it enforce the usage of the correct type.</li> <li>If you can avoid Iterators, do so. There is this cool construction with a for( Type t:<collection instance> ) : use it !</li> <li>Use assert. It’s usefull, especially instead of a bunch of if (<test is wrong>) then throw Exception* when controlling incoming parameters</li> <li>Use the new Enum type !</li> </ul> <h2 id="releasing-apacheds">Releasing ApacheDS</h2> Here is a guide on how to cut a new release. This is a long process, expect it to last a few hours ! First, you need to have a recent version of Maven (we are using 3.0.4) and a recent version of the JDK (Java 8 is required). <h3 id="maven-settings">Maven Settings</h3> You’ll need a settings section for the Nexus and people.apache.org servers with a password or a path to the SSH key used. Here’s what my settings.xml file in ~/.m2 looks like: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><settings> <servers>  <server> <id>apache.snapshots.https</id> <username>username</username> <password>********</password> </server>  <server> <id>apache.directory</id> <username>username</username> <privateKey>/Users/username/.ssh/id_rsa</privateKey> <filePermissions>664</filePermissions> <directoryPermissions>775</directoryPermissions> </server>  <server> <id>apache.releases.https</id> <username>username</username> <password>********</password> </server>  <server> <id>stagingSite</id>  <username>elecharny</username> <filePermissions>664</filePermissions> <directoryPermissions>775</directoryPermissions> </server> </servers> <profiles> <profile> <id>apache-public</id> <pluginRepositories> <pluginRepository> <id>apache.public</id> <url>https://repository.apache.org/content/groups/public/</url> </pluginRepository> </pluginRepositories> </profile> <profile> <id>apache-release</id>  <properties> <gpg.passphrase>********</gpg.passphrase> <gpg.keyname>elecharny@apache.org</gpg.keyname> </properties> </profile> </profiles> </settings> </code></pre></div>Just replace your username, passwords and paths. Note that the username and password is your Apache LDAP account. <DIV class="info" markdown="1"> You'll need to provide the passphrase in the settings.xml to access the gpg secret key installed on your host. This is due to a bug with the passphrase prompt in the maven-gpg-plugin. So unfortunately we must provide the passphrase in the settings.xml file in clear text. This should change in the future when this bug is fixed. Note that this passphrase is put into the release profile which we activate to properly sign and release the artifacts and poms via the release plugin. </DIV> <h3 id="gpg-key">GPG Key</h3> All subprojects are configured to deploy signatures for the artifacts uploaded to the repository. The gpg plugin will check use the default gpg key for the user deploying the project with the release:perform directive of the release plugin. This will prompt you for the passphrase for the default key. If you do not have one setup the build will fail. You can generate and upload a PGP key to a PGP keyserver using the following commands: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">gpg --gen-key gpg --fingerprint gpg --keyserver subkeys.pgp.net --send-keys <your key's id from last command> </code></pre></div><DIV class="info" markdown="1"> Make sure to have created the .pgpkey in your p.a.o/~ directory and to have added your public key to the KEYS file. See also https://people.apache.org/~henkp/repo/faq.html#4 </DIV> <h3 id="releasing-apacheds-1">Releasing ApacheDS</h3> Now that your environment has been setup, we will show you how to build and release the ApacheDS subproject. Keep an eye out for warnings and note sections that show version specific differences in this process. <h4 id="manual-steps">Manual Steps</h4> Some things have not yet been automated with maven and require users to manually edit some files. Below are the steps to follow. <h5 id="update-the-apachedspomxml">Update the apacheds/pom.xml</h5> 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. <h5 id="update-serviceapachedssh-and-serviceapachedsbat">Update service/apacheds.sh and service/apacheds.bat</h5> Edit the apacheds.sh/bat files in the service project directory to update the revision numbers used in that file to reference non-SNAPSHOT releases. <h4 id="release-process">Release process</h4> Since we are using Nexus for releases the release process is as follows (see also <a href="https://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven">Publishing maven artifacts</a>. <h5 id="test-the-project">Test the Project</h5> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mvn release:prepare -DdryRun=true </code></pre></div>Replace the version by the new version. Be careful, and remove the ‘apacheds-parent-’ which is proposed for the new tag. We should just use the version number. <h5 id="deploy-a-snapshot">Deploy a Snapshot</h5> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mvn deploy -Darguments="-DskipTests" </code></pre></div>This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key) <h5 id="prepare-the-release">Prepare the Release</h5> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mvn release:clean $ mvn release:prepare </code></pre></div>This creates a tag <a href="https://svn.apache.org/viewvc/directory/apacheds/tags/">here</a> <h5 id="stage-the-release">Stage the Release</h5> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mvn release:perform -Darguments="-DskipTests" </code></pre></div>This deploys the release to a staging repository. Go to <a href="https://repository.apache.org/index.html#stagingRepositories">Staging Repositories</a> and close the staging repository. (The -Darguments="-DskipTests" parameter is there to avoid running the tests again…) <h5 id="build-the-site">Build the Site</h5> We will now build the site. This will be done from the target/checkout directory : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ cd target/checkout </code></pre></div>In order to generate the site, you have to comment some modules in the apacheds pom.xml file : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"> ...   ...  </code></pre></div>Then you can start the maven command : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mvn site </code></pre></div>This creates the site and the Javadocs. <DIV class="info" markdown="1"> Now, you have to sign the sources packages which are in apacheds/target/checkout/target. Use your PGP key ID (the pub key, 4096R/[XXXXXXX] where [XXXXXXX] is the key ID) Note we should not sign with MD5 or SHA-1. </DIV> You can get the keys by typing : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">gpg --list-keys </code></pre></div>You can use this small script that does the job (copy-paste this code in a file named sign.sh in your path) : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">#!/bin/sh echo "PGP Key ID: " read DEFAULT_KEY echo "PGP Key Password: " stty -echo read PASSWORD stty echo echo "" for FILE in $(find . -maxdepth 1 -not '(' -name "sign.sh" -or -name ".*" -or -name "*.md5" -or -name "*.sha1" -or -name "*.asc" ')' -and -type f) ; do if [ -f "$FILE.asc" ]; then echo "Skipping: $FILE" continue fi echo -n "Signing: $FILE ... " # SHA-512 if [ ! -f "$FILE.sha512" ]; then gpg -v --default-key "$DEFAULT_KEY" --print-md SHA512 "$FILE" > "$FILE".sha512 echo " - Generated '$FILE.sha512'" else echo " - Skipped '$FILE.sha512' (file already existing)" fi # ASC if [ ! -f "$FILE.asc" ]; then echo "$PASSWORD" | gpg --default-key "$DEFAULT_KEY" --detach-sign --armor --no-tty --yes --passphrase-fd 0 "$FILE" echo " - Generated '$FILE.asc'" else echo " - Skipped '$FILE.asc' (file already existing)" fi done </code></pre></div>Then to sign the packages : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ sign.sh PGP Key ID: <your PGP key> PGP Key Password: <Your password> -n Signing: ./apacheds-parent-<version>-source-release.zip ... - Generated './apacheds-parent-<version>-source-release.zip.md5' - Generated './apacheds-parent-<version>-source-release.zip.sha1' - Generated './apacheds-parent-<version>-source-release.zip.asc' $ </code></pre></div><h5 id="publish-source-distribution-package">Publish Source Distribution Package</h5> 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 <a href="https://dist.apache.org/repos/dist/dev/directory">distribution</a> space for that purpose. If you haven’t checked out this space, do it now : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mkdir -p ~/apacheds/dist/dev/directory $ svn co https://dist.apache.org/repos/dist/dev/directory ~/apacheds/dist/dev/directory </code></pre></div>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 : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mkdir -p ~/apacheds/dist/dev/directory/apacheds $ svn co https://dist.apache.org/repos/dist/dev/directory/apacheds ~/apacheds/dist/dev/directory/apacheds </code></pre></div>Now, create a sub-directory for the version you have generated (here, for version 2.0.0-M22) : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mkdir ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 </code></pre></div>and copy the packages and signature to this area : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ cd target/checkout/target $ cp apacheds-parent-<version>-source-release.zip* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 </code></pre></div>Last, not least, commit your changes <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ svn add ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 $ svn ci ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 -m "ApacheDS 2.0.M22 packages" </code></pre></div><h5 id="test-the-new-version">Test the new version</h5> 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. <h5 id="create-the-installers">Create the installers</h5> We now have to create the installers. Go into the target/checkout directory and run : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ cd apacheds/target/checkout/installers $ mvn clean install -Pinstallers </code></pre></div>This will create the installers in the target/checkout/installers/target/installers directory <DIV class="info" markdown="1"> We are meant to create all the installers. It's possible to create installers for a specific platform by using a different profile : <UL> <LI>Debian : mvn clean install -Pdebian</LI> <LI>Rpm : mvn clean install -Prpm</LI> <LI>Windows : mvn clean install -Pwindows</LI> <LI>Mac OS X : mvn clean install -Pmac</LI> <LI>Binary : mvn clean install -Pbin</LI> <LI>Archive : mvn clean install -Parchive</LI> </UL> <pre><code>This will build only one single target. </code></pre> </DIV> <DIV class="info" markdown="1"> If the packaging tool path is not correct, you can set it on the command line : <UL> <LI>Debian : mvn clean install -Pdebian -Dinstallers.dpkg=<path to the dpkg installer></LI> <LI>Rpm : mvn clean install -Prpm -Dinstallers.rpmbuild=<path to the rpmbuild installer></LI> <LI>Windows : mvn clean install -Pwindows -Dinstallers.makensis=<path to the makensis installer></LI> <LI>Mac OS X : mvn clean install -Pmac -Dinstallers.packageMaker=<path to the PackageMaker installer></LI> </UL> Typically, recent versions of Mac OSX moved the tools from /usr/bin to /usr/local/bin Keep in mind that you will have to sign and move each target package before building the next one, as the clean instruction will remove the content of the target directory… </DIV> Sign those installers using the sign.sh script, and copy them in ~/apacheds/dist/dev/directory/apacheds/<version> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ cd apacheds/target/checkout/target/installers/target/installers $ cp apacheds-<version>* ~/apacheds/dist/dev/directory/apacheds/2.0.0-M22 </code></pre></div>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. <h5 id="vote">Vote</h5> Start a 72h vote at the dev mailing list. <h5 id="release">Release</h5> If the vote succeeds Apacheds project can be released. Go to <a href="https://repository.apache.org/index.html#stagingRepositories">https://repository.apache.org/index.html#stagingRepositories</a> 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 users. We use the <a href="https://dist.apache.org/repos/dist/release/directory">distribution</a> space for that purpose. Move the distribution packages (sources and binaries) to the dist SVN repository: <a href="https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)">https://dist.apache.org/repos/dist/release/directory/apacheds/dist/$(version)</a> If you haven’t checked out this space, do it now : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ mkdir -p ~/apacheds/dist/release/directory $ svn co https://dist.apache.org/repos/dist/release/directory ~/apacheds/dist/release/directory </code></pre></div>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 : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ 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 </code></pre></div>Then move the packages from ‘dev’ to ‘release’ : <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"># cd dist/release/directory/apacheds/dist # cp ~/apacheds/dist/dev/directory/apacheds/<version> . # svn add <version> # svn ci <version> ... # exit $ </code></pre></div>The packages should now be available on <a href="https://www.apache.org/dist/directory/apacheds/dist/">https://www.apache.org/dist/directory/apacheds/dist/</a><version> <h5 id="deploy-the-javadocs-and-xref">Deploy the Javadocs and XRef</h5> We now can deploy the generated Javadoc and cross-reference pages. They are generated in the following directory : target/checkout/target/site We will copy two directories : <ul> <li>apidocs</li> <li>xref</li> </ul> They are uploaded to <a href="https://nightlies.apache.org/">https://nightlies.apache.org/</a> via WebDAV protocol. First create the folders for the version: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ curl -u <your asf id> -X MKCOL 'https://nightlies.apache.org/directory/apacheds/<version>/' $ curl -u <your asf id> -X MKCOL 'https://nightlies.apache.org/directory/apacheds/<version>/apidocs' $ curl -u <your asf id> -X MKCOL 'https://nightlies.apache.org/directory/apacheds/<version>/xref' </code></pre></div>I used Rclone to copy folders via WebDAV. After intallation run rclone config and configure the nightlies connection: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">$ rclone config name: nightlies type: webdav url: https://nightlies.apache.org vendor: other user: yourasfid pass: yourasfpassword (will be stored encrypted) </code></pre></div>Then copy the directories: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash">cd target/checkout/target/site rclone copy --progress apidocs nightlies:/directory/apacheds/<version>/apidocs rclone copy --progress xref nightlies:/directory/apacheds/<version>/xref </code></pre></div>Finally update the links in the static/apacheds/gen-docs/.htaccess of the directory-site repo: <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text">RewriteRule ^latest$ https://nightlies.apache.org/directory/apacheds/<version>/ [QSA,L] RewriteRule ^latest/(.*)$ https://nightlies.apache.org/directory/apacheds/<version>/$1 [QSA,L] </code></pre></div>Save and commit the file. <h5 id="update-the-web-site">Update the web site</h5> You can now update the site, add a news on the front page, and publish the site. There are a few places to modify : <ul> <li>/config.toml : update the version_apacheds variable with the new version.</li> <li>/source/_index.md : same here, update the  section, which contains the version.</li> <li>/source/apacheds/news.md : add the news on top of this page</li> <li>/source/apacheds/download-old-versions.md : add a new line on top of the array, which refers to the latest version before the new one</li> </ul> PS: You can check the result of your modification on <a href="https://builds.apache.org/job/Directory/job/site/">the build system</a>. If you have made an error, the web site won’t be updated, without notice, but there! Commit the changes, and publish the web site, you are done ! <h5 id="inform-the-world-">Inform the world !</h5> After 24h, you can now inform the world about the release. Send a mail to the users and dev mailing list, and one to the <a href="mailto:announce@apache.org">announce@apache.org</a> You are done ! </div> <div id="endContent"></div> </div> <div class="footer-wrapper"> <div id="footer"> © 2003-2025, <a href="https://www.apache.org">The Apache Software Foundation</a> - <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a> Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio, Apache LDAP API, Apache Triplesec, Triplesec, Apache Mavibot, Mavibot, Apache eSCIMo, eSCIMo, Apache SCIMple, SCIMple, Fortress, Apache Fortress, EnMasse, Apache EnMasse, Apache Kerby, Kerby, Apache, the Apache feather logo, and the Apache Directory project logos are trademarks of The Apache Software Foundation. </div> </div> </div> <div class="top-bottom-spacer"></div> </body> </html>