On Oct 30, 2006, at 11:32 PM, Dain Sundstrom wrote:
In a typical Geronimo release we tend to spend a significant amount
of time in what I'll call the "Fit and Finish" phase. This
involves tying up loose ends such as log levels, tools L&F, startup
times, licenses and so on. Basically, the phase includes fixing
all the nits that cause people to vote -1 for a release (BTW no
vetos in a release vote).
Please, take a moment and respond to this email with any items you
feel should be cleaned up before we release the software. That way
we can hopefully get these items out in the open and addressed
while we are finishing the TCK testing. Please note that just
because an item is mentioned doesn't mean it must be completed
before a release. The only thing required for a release it to
successfully pass a vote of the PMC, so if the item is critical to
you, spend a few minutes fixing it.
With any luck we should be able to have the server ready to ship
about the same time we finish the TCK testing.
As I've mentioned previously, all source files must comply with the
new ASF source header and copyright notice policy (see http://
www.apache.org/legal/src-headers.html). I created GERONIMO-2537 to
track this...
Appear to be some scripts that can be used to automatically make the
updates (see the FAQ). However, they seem to be accessible only by
ASF Members?!!
I'd also suggest that we run RAT (http://code.google.com/p/arat/). To
audit the compliance of Geronimo to Apache release requirements and
best practices... RAT was developed (at least in part) to aid
incubating Apache projects.
IMO, fixing the startup time of the web console config under jetty
(see GERONIMO-2507) is a must fix...
--kevan
