Hi,
Jared Rhine wrote:
Summary: There's a new "qasharing.osafoundation.org" server plus Cosmo
instance dedicated to being the target for Chandler sharing tests.
Great! I hope that having it as a virtual machine on the same hardware
as osaf.us won't hamper osaf.us perf though I'm pretty sure that right
now it's not an issue.
* 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.
I think Build/Release should be that maintainer since they own the well
being of the build/test system (including TBoxes).
* 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).
The "call" should be made during the biweekly Chandler Engineering
meeting so that QA and devs (who have a stake in the test system
stability) can raise issues if any. Build/release is already part of
this meeting.
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!
This is very helpful. Thanks for doing this.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
