Summary: There's a new "qasharing.osafoundation.org" server plus Cosmo instance dedicated to being the target for Chandler sharing tests.
Background: A few months back, we pointed the Chandler trunk sharing tests to osaf.us, in order to get more testing of Cosmo 0.5 stuff into Chandler 0.7a4. They've been pointed there since. We said this was a temporary situation, convenient for satisfying the requirements we had for a stable server running 0.5. qacosmo can't be the target for sharing tests because it's updated weekly and as-needed. What we really needed (per earlier discussions) was a new Cosmo instance solely dedicated to running sharing tests. This way, no other work would destabilized the sharing tests, plus build/release could decide when extra value would be had by pointing tinderboxen at say a pre-release of Cosmo or to confirm backwards compatibility maybe. Additionally, Heikki had asked for a target machine "outside the office", so as to better simulate real-world "open internet" sharing. So, I've created a new (virtual) server to assist with all these goals: qasharing.osafoundation.org. This instance is hosted at colocation (SF GNi, not Redwood City ISC), has 1Gb of RAM, 50Gb of disk, 4Gb of swap, JRockit 27.1.0, and a running instance of Cosmo 0.6-CP-r3342-20070116 on port 8080, and accounts for the asking. This is offered hoping that a couple of things will happen: * We identify a maintainer for the Cosmo instance that Chandler sharing tests will point at. I can assist if needed, as changes should be pretty infrequent. * We jointly decide that, as with our run-up to Cosmo 0.5, it'd be useful to point the sharing tests at a pre-RC/RC of Cosmo 0.6, and that we should maybe do that in the next 5-10 days. (After Cosmo 0.6 is released, the target would be updated to 0.6 final and remain there for stable daily testing.) * osaf.us production instance needn't have Chandler testing load and data from tinderboxes. * We move to use qasharing.osafoundation.org as the permanent home of the sharing tests. Build/release makes the call for when the Cosmo instance gets updated (instead of on the hosted service's schedule). I hope this is helpful. I think it's in line with all previous discussions, but if something else is needed for a better process, or comments, questions, feedback, please followup. Thanks! -- Jared _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
