Developers with commit access to the Apache source tree normally use Subversion to keep their local copies of the source tree up to date automatically. This is a very useful ability that also allows for getting change history of files, diffs between arbitrary versions, etc. This is also the method used to commit changes to the source tree.

For those who do not have commit access to the source tree, anonymous Subversion access offers an alternative way to do most of this using read-only access to the Subversion repository. The obvious difference is that you can't commit changes using anonymous Subversion access.

Anonymous Subversion access is available as follows:

APR 2.0 (development version, incorporating both APR and APR-UTIL from earlier versions):

svn co https://svn.apache.org/repos/asf/apr/apr/trunk/ apr

APR 1.6 (current release version)

svn co https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/ apr

APR-UTIL 1.6 (current release version)

svn co https://svn.apache.org/repos/asf/apr/apr-util/branches/1.6.x/ apr

APR 1.7 (incremental dev version)

svn co https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x/ apr

APR-UTIL 1.7 (incremental dev version)

svn co https://svn.apache.org/repos/asf/apr/apr-util/branches/1.7.x/ apr

APR-ICONV

svn co https://svn.apache.org/repos/asf/apr/apr-iconv/trunk/ apr-iconv

You can also browse the repository using ViewVC.

Developers can check out the site as follows:

  svn co https://svn.apache.org/repos/asf/apr/site/trunk/ apr-site

After generating HTML and committing, the site is updated automatically via rsync.

Developers can check out the test package directory as follows:

  svn co https://dist.apache.org/repos/dist/dev/apr apr-dev

After committing, the site is updated automatically via svnpubsub.

Developers can check out release directory as follows:

  svn co https://dist.apache.org/repos/dist/release/apr apr-release

After committing, the site is updated automatically via svnpubsub.

Users access this directory via mirrors, and it takes around 24 hours for most mirrors to be updated. Thus, an approved test release is published in the following sequence:

1. Test packages are approved.
2. Approved test packages are moved (svn mv) from apr-dev to apr-release.
3. Wait 24 hours, then check mirrors to ensure that most or all are up-to-date.
4. Update site to point to new release and send the announcement.
5. If the new release replaces an old in the same MAJ.MIN, remove the old (replaced) release from apr-release.