avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Benett <char...@benett1.demon.co.uk>
Subject Re: Tasks to be done prior to release.
Date Tue, 08 May 2001 11:56:48 GMT

Berin Loritsch wrote:
> Avalon Framework, Excalibur, and LogKit are now in Code Freeze.
> Please note, LogKit will NOT use the org.apache.avalon.log
> package, but instead will be released in the current package.
> Since there was no critical reason for forcing the migration,
> and Avalon needs a release more than the migration, we will
> use its existing package.
> Task 1
> ------
> At this point we should be focused on debugging.  As most everything
> works at this point, we need to check robustness.  Unless we come up
> with a showstopper here, we should be good to go on Friday.

The fixes to the ThreadPool class appear to work OK. Cornerstone and
james updated.

> Task 2
> ------
> We need to do a minimum Documentation check.  If the generated docs
> refer to something that is not a part of Excalibur or Framework, then
> it needs to be fixed (document debugging).  Please do not concentrate
> on writing _new_ docs at this stage.
> Task 3
> ------
> Decide on compilation policy for released packages.  My proposition:
> Beta Releases: Debug info "on" and Optimization "off"
> Final Release: Debug info "off" and Optimization "on"

I'd suggest leaving optimization off, if folks want to optimize they can
do so from source.


To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org

View raw message