Hi, I was looking at what it would take to do the AR2 release, and one thing that comes up is the lack of any integrated test runs in the Ant build. We have a Hudson CI build that automatically runs the tests, but that's just a single environment. I'd feel much more comfortable doing a release if I could be confident that everyone who reviews a release candidate has run the test suite in their environment.
As discussed in RIVER-301, having a simple way to build *and test* River would be very good. Unfortunately, as Tom points out based on his experience, moving the current qatests into the River build is a complex task. Even building the qatests by themselves is difficult due to lack of documentation and the ancient Makefiles. So, unless anyone comes up with a brilliant solution to RIVER-301, I was thinking that we could simplify testing by releasing the current qatests separately. This release would also contain pre-built qatests artifacts that should be much easier to integrate into the main jtsk build. WDYT? BR, Jukka Zitting
