I vote option 2
- create a separate binary QA release, something like
apache-river-qa-2.1.x-bin.zip next to apache-river-2.1.x-bin.zip
If someone has problems on an untested platform (we probably can't test
all environments) a user can run the QA tests.
Cheers,
Peter Firmstone.
Jonathan Costers wrote:
Thanks Jukka
The build seems to work again:
http://hudson.zones.apache.org/hudson/job/River-trunk/168/
This brings up something else: will we include the QA harness and test
binaries in the River distribution?
Currently, I added them to the main River release bundle, but I'm not sure
if we should do that.
Options:
- include QA binaries in main binary River release (makes the bundle become
much larger)
- create a separate binary QA release, something like
apache-river-qa-2.1.x-bin.zip next to apache-river-2.1.x-bin.zip
- do not release QA binaries at all, only include QA harness and test code
in the source release
The same question could be asked about the "hello example", which is
currently not released as part of the binary bundle.
Rationale:
- Most people just using the River libraries probably usually don't care too
much about running the QA tests (it should be done by the River
contributors)
- Releasing the QA binaries and adding a way to run them standalone (outside
Ant) would maybe increase the number of times the tests are being run, which
would benefit issue detection
Team, your thoughts?
Best
Jonathan
2009/4/20 Jukka Zitting <[email protected]>
Hi,
On Sun, Apr 19, 2009 at 12:01 AM, Jonathan Costers
<[email protected]> wrote:
OK, here is what I think we should use for now:
cd $WORKSPACE/jtsk/trunk
ant all.clean release qa.run
OK, done.
BR,
Jukka Zitting
