Table of Contents
	1. What is MaxSVN
	2. !!! WARNING TO !!!NOT!!! USE MaxSVN IN PRODUCTION ENVIRONMENTS !!!
	3. Minimum system requirements
	4. Details about the MaxSVN distribution
	4.1 Patches used to build MaxSVN
	4.2 Verifying the file integrity
	4.3 Validating the download package
	4.4 Modifying the Neon integration
	5. Version scheme and release schedule
	5.1 Version scheme for released-based builds
	5.2 Version scheme for development-based builds
	5.2.1 development branch based builds
	5.2.2 trunk based builds
	5.3 Release Schedule
	6. A word on licensing
	7. Thanks
	8. Acknowledgment
	9. Trademark Notes



1. What is MaxSVN?

MaxSVN (http://luke1410.de/index.php?id=97) is a highly experimental
distribution of Apache™ Subversion® (SVN) for Windows, distributed by Stefan
Hett (luke1410@gmx.de).

Please report bugs and feature requests in the bugtracker:
http://www.luke1410.de:8090/browse/MAXSVN

The name 'Max' originates from an old nickname Stefan used back in the early
days before the internet got known to a broughter audience and is not to be
mistaken for something like "maximum".
Furthermore, MaxSVN is a distinct product and even though it distributes the
Apache Subversion project and relies on other software from the Apache Software
Foundation, it is not at all associated with the Apache Software Foundation.
(Apache Subversion is a project of the Apache Software Foundation - please take
a look here, if you are not familiar with the Apache Subversion project
https://subversion.apache.org/)

The main purpose of MaxSVN is to be used for development of Subversion itself
and for providing a distribution which can be used to test features/builds as
early as possible.
The aim is to provide:
- a distribution which tests SVN against the latest build tools on Winodws and
  the latest versions of its dependencies
- provide early access to versions of SVN while they are in development
- provide a distribution which can be used to debug/test issues urself (by
  providing symbol files)

That said:



2. !!! WARNING TO !!!NOT!!! USE MaxSVN IN PRODUCTION ENVIRONMENTS !!!

!!! IT IS NOT SUITABLE FOR PRODUCTION USE !!!

Please stick with one of the other freely available distributions of SVN for
Windows. A list of the major ones can be found here:
https://subversion.apache.org/packages.html#windows
(if you know of another distribution not listed here, do not hesitate to send
it to me at luke1410@gmx.de)

These distributions also provide the commandline tools which MaxSVN provides,
but are more thoroughly tested and provide certain other advantages over the
MaxSVN distribution which are relevant for production use (for instance:
installers, auto upgrading, separate support channels, etc.).

CollabNet Subversion:
	download: free but requires registration
	license: distribution dependent (except for the Subversion Edge product
	         they are free for private and commercial use)
	further features: auto-updater and Apache server (Subversion Edge
	                  contains a lot of additional features)
SilkSVN:
	download: free (without prior registration)
	license: free for private and commercial use
	further features: none
TortoiseSVN:
	download: free (without prior registration)
	license: free for private and commercial use
	further features: GUI integration into the Explorer with a bunch of
                          additional features
VisualSVN:
	download: free (without prior registration)
	license: free for open source developers, private/personal use,
                 Microsoft® MVPs, and academic institutions
	further features: Visual Studio® integration
WANdisco Subversion:
	download: free but requires registration
	license: unknown
	further features: unknown
Win32SVN:
	download: free (without prior registration)
	license: free for private and commercial use
	further features: none



3. Minimum system requirements

MaxSVN requires Windows Vista or a later Windows OS (64-bit). Windows XP,
previous versions and 32-bit OS' are not supported.
You will also require the Visual Studio 2015 Runtime being installed on the
machine. It can be downloaded directly from Microsoft at:
https://www.microsoft.com/en-us/download/details.aspx?id=48145




4. Details about the MaxSVN distribution

MaxSVN is built using the following build tools:
	Visual Studio 2015 CE (Update 2)
	AWK 20070501
	CMake 3.5.2
	Perl 5.22.1.2201 (ActivePerl)
	Python™ 2.7.11
	SCons 2.5.0

MaxSVN is built using the following dependencies:
	Apache httpd 2.4.20
	APR 1.5.2
	APR-util 1.5.4
	APR iconv 1.2.1
	Expat 2.1.1
	Neon 0.30.1 (for MaxSVN < 1.8)
	OpenSSL 1.0.2h
	PCRE 8.38
	serf 1.3.8
	SQLite 3.13.0 (amalgamation)
	ZLib 1.2.8

Following dependencies are not built in (yet):
	Berkeley DB: It's considered deprecated in 1.9 and is likely to be
                     dropped in a future version.
	Apache httpd: Apache is currently not built with OpenSSL/ZLib
                      integration.
                      (it's considered irrelevant for the purpose of building
                      Subversion)
	libintl: Currently not built in.
	Gnu gettext: Currently not built in.
	Bindings (Java, Ruby, SWIG): Not built in (out of scope atm for this
                                     distribution).

MaxSVN is tested on Windows 10 (1115) (64-bit).

4.1 Patches used to build MaxSVN
To resolve build issues and test failures MaxSVN applies patches where
necessary to the otherwise unchanged clean source code of SVN and its
depdendencies. A list of the patches incorporated in a particular release can
be retrieved by using the Patch version/s field in the MaxSVN bugtracker.
For instance the following link will present all patches used/incorporated in
MaxSVN 1.9.3-1:
http://www.luke1410.de:8090/browse/MAXSVN-52?jql=project%20%3D%20MAXSVN%20AND%20%22Patch%20Version%2Fs%22%20%3D%201.9.3-1

4.2 Verifying the file integrity
The used RAR and ZIP formats have built-in checksums to verify the data
integrity of the package. You can use the different archive tools to ensure the
package was downloaded correctly and isn't broken.
In addition to this, you can calculate the SHA-1 or MD5 hash of the archive and
compare it against the hash value noted at the download page.

4.3 Validating the download package
In order to validate the downloaded package was really published by its creator
and wasn't altered with by someone else, ASCII armored signatures are provided
for each download package (using an OpenPGP key). The corresponding key can be
downloaded from the homepage: http://www.luke1410.de/typo3/index.php?id=8, the
webpage's foaf.rdf-file or from a public key server.
Fingerprint: 7B8CA7F6451AD89C8ADC077B376A3CFD110B1C95

4.4 Modifying the Neon integration
A note to satisfy the LGPLv3 (for Neon):
You can always rebuild MaxSVN from the Subversion source combined with the
libraries mentioned above. That way you can also built MaxSVN with you own
modified version of Neon.



5. Version scheme and release schedule
MaxSVN uses two different version schemes. One for builds based on already
released SVN versions and another style for builds based on the development
branches.
Using a different version scheme for development branch based builds is a
preemtive measure to ensure that people spotting MaxSVN and not being familiar
with the difference between MaxSVN and SVN mistakenly believe that an SVN
version might have already been released and are reporting issues to the SVN
developers.
See http://www.luke1410.de:8090/browse/MAXSVN-11 for further details.

5.1 Version scheme for released-based builds
[SVN major version].[minor version].[SVN patch number]-[MaxSVN build]

The SVN version number makes up the first three digits of the MaxSVN version
number.
It's being added a build number for that version (separated with a dash)
indicating successive MaxSVN builds based on the same underlying SVN version.

5.2 Version scheme for development-based builds
5.2.1 development branch based builds
[development branch]-dev-[SVN patch number]-r[revision number]-[MaxSVN build]

The first part of the version number consists of the branch name the version is
based on (for instance: 1.8.x or 1.9.x).
[SVN patch number] equals that version of the branch which has already been
released. I.e. if the last released version of the 1.9.x branch is 1.9.2 the
[SVN patch number] will be 2 for any following builds based on the 1.9.x-branch
(until 1.9.3 is released, at which point the next 1.9.x-branch version will
start using the number "3").
[revision number] is the revision number of the branch used to make the build.
[MaxSVN build] is then the build number of this particular SVN-code-based build
and increases whenever a new build is done without the used SVN code having
changed.

5.2.2 trunk based builds
trunk-dev-r[code revision number]-[MaxSVN build]

This scheme follows the same style as the development branch based builds with
the exception that it uses "trunk" for the first part of the version number and
drops the [last SVN patch number] part.

5.3 Release Schedule
In general releases of MaxSVN are planned to be done whenever any new SVN
version is about to be released. I.e. if there is a new 1.7.x release, new
versions for all relevant MaxSVN versions are prepared.

Relevant in this regards means:
- any still maintained version
- any version which uses a dependency/build tool for which an update is
  available
- any version for which new code is available in the SVN repository (excluding
  changes which only touch text files)

Still maintained versions are always:
- the latest publically released SVN version of each major version (1.7, 1.8, etc.)
- the current development versions of each major SVN version (1.7, 1.8, etc.) if
  they have relevant changes (i.e. code changes) compared to the corresponding
  latest publically realeased version

In other words:
For the SVN 1.9-based versions this means that 1.9.0-x will be maintained until
SVN 1.9.1 is publically released. At this point 1.9.1-x will be maintained.
In addition: During the maintenance period of 1.9.0 there will also be
1.9.x-dev-0-rXXXXXXX-x releases which are based on the current SVN 1.9
development branch.
At the point where SVN 1.9.1 is prepared for public release 1.9.0-x will no
longer be maintained and there will be a new release of 1.9.1-x without the.



6. A word on licensing
MaxSVN is distributed under the MIT license.

The distribution is based on the following open source projects which
themselves fall under the noted licenses:

Apache Subversion:
The basis for this distribution is Subversion which is licensed under the
Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Apache HTTP Server (httpd):
The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems including UNIX and
Windows NT.
Apache httpd is used to build Subversion and therefore part of MaxSVN. The
library is licensed under the Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Apache Portable Runtime (APR):
A dependency used to build MaxSVN.
This library is used to build Subversion and therefore part of MaxSVN. The
library is licensed under the Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Apache Portable Runtime Library:
A dependency used to build MaxSVN.
This library is used to build Subversion and therefore part of MaxSVN. The
library is licensed under the Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Apache Portable Runtime Iconv Library:
A dependency used to build MaxSVN.
This library is used to build Subversion and therefore part of MaxSVN. The
library is licensed under the Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Expat:
Expat is an XML parser library written in C. It is a stream-oriented parser in
which an application registers handlers for things the parser might find in the
XML document (like start tags).
This library is used to build Apache Portable Runtime Library and therefore
part of MaxSVN. The library is licensed under the MIT/X Consortium license.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

Neon (for MaxSVN 1.7.x):
neon is an HTTP and WebDAV client library, with a C interface.
This library is used to build Subversion and therefore part of MaxSVN. The
library is licensed under the GNU Library GPL v3 (GNU Lesser General Public
License v3).
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

OpenSSL:
OpenSSL is a cryptography toolkit implementing the Secure Sockets Layer (SSL
v2/v3) and Transport Layer Security (TLS v1) network protocols and related
cryptography standards required by them.
This library is used to build Subversion and therefore part of MaxSVN. OpenSSL
is licensed under the combined OpenSSL and SSLeay licenses.
The licenses are distrbuted alongside the package to satisfy the requirements
to distribute MaxSVN. They are NOT to be mistaken for alternative licenses of
this distribution!

Pearl Compatible Regular Expressions (PCRE):
The PCRE library is a set of functions that implement regular expression
pattern matching using the same syntax and semantics as Perl 5.
The library is used to build Apache httpd and therefore part of MaxSVN. The
library is licensed under the BSD license.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

serf:
Serf is  high performance C-based HTTP client library built upon the Apache
Portable Runtime (APR).
This library is used to build Subversion and therefore part of MaxSVN. Serf is
licensed under the Apache License 2.0.
The license is distrbuted alongside the package to satisfy the requirements to
distribute MaxSVN. It is NOT to be mistaken for an alternative license of this
distribution!

SQLite:
SQLite is an in-process library that implements a self-contained, serverless,
zero-configuration, transactional SQL database engine.
SQLite is used to build Subversion and therefore part of MaxSVN. SQLite is
public domain.

ZLib:
zlib is designed to be a free, general-purpose, legally unencumbered -- that
is, not covered by any patents -- lossless data-compression library for use on
virtually any computer hardware and operating system.
ZLib is used to build Subversion and therefore part of MaxSVN. ZLib is licensed
under the ZLib License.



7. Thanks
Thanks go to all the developers of Subversion who have been spending years on
that project and still providing this CVS under an open source license.
Special thanks go to the following developers who spent their time to get this
distribution to a point where it was finally in a distributable state:
- "Bert"
- "danielsh"
- "jcorvel"
And last but not least also a big thanks to "stefan2" who took my feedback on
the svn mergeinfo normalizer tool and incorporated all of that within a very
short time period into Subversion. Without his effort and work I would have
never went this path which lead to this distribution.



8. Acknowledgment
MaxSVN uses the following software/libraries and hereby acknowledges all the
effort the people/teams/comnpanies behind these products have contributed to
make MaxSVN available:
Apache Subversion: https://subversion.apache.org/
Apache HTTP Server: http://httpd.apache.org/
Apache Portable Runtime (APR): https://apr.apache.org/
Apache Portable Runtime Library: https://apr.apache.org/
Apache Portable Runtime Iconv Library: https://apr.apache.org/
Expat: http://www.libexpat.org/
Neon: http://www.webdav.org/neon/
OpenSSL: http://www.openssl.org/
	This product includes software developed by the OpenSSL Project for use
	in the OpenSSL Toolkit. (http://www.openssl.org/)
	This product includes cryptographic software written by Eric Young
	(eay@cryptsoft.com)
	This product includes software written by Tim Hudson
	(tjh@cryptsoft.com)
PCRE: http://www.pcre.org/
serf: http://serf.apache.org/
SQLite: https://www.sqlite.org/
ZLib: http://www.zlib.net/



9. Trademark Notes
Apache, Apache HTTP Server, and Apache Subversion are trademarks of The Apache Software Foundation.
Microsoft and Visual Studio are trademarks of the Microsoft Corporation.
Python is a trademark of the Python Software Foundation.