Some suggestions and potential issues when it hits the incubator PMC
vote:
(looking at the source tarball)
1) Consider putting all the parts in a directory rather than have the
tarball unpack into the current working directory
2) Consider explaining about the incubation status in the README.
Generally we like the status to be prominent for users, in this case
[EMAIL PROTECTED]:/tmp/qpid$ grep -ir incubat *
RELEASE_NOTES.txt:Apache Incubator Qpid Java M1 Release Notes
src/java/build.properties:build.release.name=incubator
[EMAIL PROTECTED]:/tmp/qpid$
it isn't very prominent.
3) The Exolab JMS Compliance Test Suite might not be okay to include
in the distro as it is listed as (c) and all rights reserved. There
is a file in src/java/client/test/lib/jmscts/license.jmscts.txt which
implies that not all rights are, in fact reserved.
4) Where is the Jython license? (not referenced in LICENSE.txt like
others) It may not be relevant as I don't see Jython anywhere in the
actual distro, but it is listed as included in the NOTICE.txt
5) The build failed for me:
[EMAIL PROTECTED]:/tmp/qpid/src/java$ ant
... snipped ...
dist-bin:
[copy] Warning: /private/tmp/qpid/src/java/cluster/bin not
found.
[copy] Warning: /private/tmp/qpid/src/java/cluster/etc not
found.
BUILD FAILED
/private/tmp/qpid/src/java/build.xml:46: The following error
occurred while executing this line:
/private/tmp/qpid/src/java/build.xml:38: Invalid file: /private/
tmp/qpid/src/java/systests
Glad to see a release candidate so soon!
-Brian
On Nov 15, 2006, at 11:45 AM, Rajith Attapattu wrote:
Hi All,
The M1 release candidates are available for download at the following
location.
http://people.apache.org/~rajith/qpid-release/
Regards,
Rajith Attapattu
