https://bugzilla.wikimedia.org/show_bug.cgi?id=33644
--- Comment #10 from Erik Moeller <[email protected]> 2012-02-01 18:13:01 UTC --- Hi Peter, I'm well aware of the good work you, Mark and others have been doing on the deployment beta sites, and they should definitely be part of the staging process. However, they are and always will be only an approximation of actually running code on the production cluster. There may still be small differences which result in bugs -- some oddness about the configuration of the bits cluster, or memcached, or Lucene, ... Because of these unavoidable differences, mature engineering organizations have multiple staging/testing steps. We do, although we're not quite routinely utilizing them. Software should first be deployed into an ever-improving beta site (for which purpose we can hopefully soon get rid of prototype.wikimedia.org* completely). Provided all code is reviewed and passes initial QA, it should then be deployed into a testing mode on the production cluster. That can be done in different ways -- dark launches (where a URL parameter is used to call up some code that's not yet officially released), opt-in launches, or test wikis running on the production cluster. For AFTv5 specifically, it's useful to have the latter option prior to production deployment. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
