What we had talked about with Kevin and I think is a good plan is the following:

Daily Builds: Keep until a new Stable Release is put out, then wipe clean and start over

Stable Builds: Keep until a new release candidate is put out then wipe clean

Release Candidates: Keep until a new release is put out then wipe clean.

Releases: business decision, not set rule.

With this strategy it all rolls up and keeps only what might be relevant on the website.

The agrument that, "for a daily build they can download the source and build it", is not entirely accurate. First, that would be a lot more work than downloading an installer executable or executable jar, and would be too geared towards a developer. Second the build from the source currently does not create an installer, it simply allows you to run from the Eclipse environment, nor does it create the server only jars. Is there a demand? I don't know right now, but the whole concept that is brought forward over and over again about open source is that being open source means you provide updates to builds often so that someone can take advantage of the latest features if they so choose to. Just my thoughts - at least we are discussing it