On Fri, Apr 15, 2011 at 12:10 PM, Gerard Meijssen <[email protected] > wrote:
> Hoi, > It makes sense for translatewiki.net to run on trunk. This way we are > exposed to the latest messages and get as much localisation done before > code > actually hits production servers. Running another project just because it > will run trunk only makes sense when it running trunk has added value. > > What you can do is adopt translatewiki.net as your barometer for code > quality and help it run as smoothly as possible. > translatewiki.net is a great help, but don't forget that it doesn't run all the same extensions as are used in Wikimedia production sites. Regressions affecting things like CentralAuth can and do strike with very little warning; we've had several in the last few weeks that are only being caught because I have it set up on my workstation's dev instance and I see the breakages while I'm testing unrelated things. It's important to actually be exercising the same code and the same configurations that are running in production. And when some bugs still don't get caught during that testing, it helps *a lot* to have only a minimal change set to look at since your last deployment. Changes can be rolled back more easily, and the problems found and fixed and redeployed more easily. -- brion _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
