You aren't running trunk in production, right? Right?
And what's wrong with that?
One of the nice things about the MediaWiki development process is that our trunk generally *is* usable. Sure, every one in a while someone fails to test their code properly before committing and breaks something, but generally you can just report the regression on #mediawiki and it'll get fixed or reverted promptly.
Anyway, we really should encourage more people to run trunk. It's the only efficient way to catch bugs before we put out a tarball.
I don't think we should encourage people to run trunk in production. We should encourage people to run release candidates in production, and possibly betas for those that know the software *really* well. We should likely encourage people to run trunk on their live testing environments, though.
Occasionally security issues pop up in trunk that get caught in code review. People who run trunk are much more likely to have security problems, so on a production site, it's a problem. Similarly, it's possible that commits may come in that can cause data loss, which will later get caught in code review.
Our trunk usually stays stable enough that developers can have a usable working environment, but I don't think it's stable enough to run on any site where you care about security or your data.
- Ryan Lane