Last modified: 2013-05-02 19:41:55 UTC
Might be dependent on getting a real het deploy setup, but ideally we should have test.wp.o running HEAD of trunk, updating no less often than once an hour or so.
That would be dangerous if it were to use the common Wikimedia configuration, as there are various way to interfere with foreign databases.
This would probably be better as a prototype instance... And our trunk vs deploy{ment/able} code isn't always the same and test.w is designed to be able test stuff that is about to be deployed to the full cluster.
test is for testing deployment tree before pushing to all wikis. running trunk doesn't help much there. anyone can run trunk on their laptops I guess ;-)
It doesn't have to be test.wp.o. But the point remains the same: we should have public wiki somewhat resembling the cluster that has a copy running trunk at all times.
Even better, wait until Ryan's virt cluster stuff is done. Then we could make a little family of wikis running trunk in the following configurations: en, commons repo, a rtl language, etc.
Marking as LATER (perhaps WONTFIX), this would be part of the virtual cluster / "prototype family" project.
Welcome to Wikimedia Labs! :)