For v 2.0+ we need to create an actual distribution package

[martindholmes]

In addition to supplying a sample config file with full comments, we should actually have a script which builds a distribution for end-users. We can exclude lots of bits and pieces such as the ci and jenkins folders, the documentation config file, and so on, making for a less cluttered package. We should also have a decent version of the built documentation, which needs to function locally (so can't have a search), but could point to the online version which does.

[martindholmes]

Starting a plan for this. We need:

1. a buildRelease.xml ant file.
2. a diagnostics.xsl file which checks a bunch of things before a release can be made.

The ant file should run the diagnostics, and parse the results to discover whether it's possible to proceed.
If not, it reports the fixes needed. These may be things like not being on a release branch; not having a documentation whatsnew div with the version matching the EDITION file; and more, as we think of things.
If so, it will:

• build the documentation to create the single HTML version for distribution;
• create a folder called release-x.y.z;
• copy all content into it;
• create zip and tar.gz archives of that folder.

Questions remaining:

1. Do we include the test content so the user can run a local test, or is that confusing?
2. Do we provide a sample template for a config file?
3. Do we include the documentation build process as another potentially useful test?