[j-devel] Steps to a release

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

We've made great progress over the last 2 months making ABCL more
compliant with the ANSI standard (reducing ANSI tests failures). We've
also improved the quality of our build infrastructure a lot,
especially the case where people don't have a Lisp handy to bootstrap.

That calls for a release to make this fact public :-) I think we need
a few steps before we can make the actual release:

1) Describe the changes between 0.0.10 and the new release (0.0.11)

2) We need to verify the tarballs created by our new build.xml file
actually can be built either using Ant or using the Lisp way.

3) We need to verify that the tarballs as well as the jars created out
of them are "the same" (contain the same files) as a build out of the
repository

4) It must be clear what the license for ABCL is, both from our
website as well as from the tarball (is it currently?)


and after a release, we should probably work on:

* documentation on how to get started with ABCL on the website
* examples on how to use ABCL from your own Java application


Takers?

Bye,

Erik.