On Tue, Dec 18, 2012 at 11:23 AM, Rob Lanphier robla@wikimedia.org wrote:
Hi everyone,
My understanding is that some new extensions intended for widespread deployment aren't getting deployed to test2.wikipedia.org before going to other production wikis. As I was discussing this with Chris McMahon, he pointed out that there's no stated policy that this should be done.
test2.wikipedia.org is basically a standard configuration wiki on the production cluster that we use as the final place for testing before going out to other production wikis. Pretty much anything destined for one of our top wikis or to a substantial number of smaller wikis should go to test2. That's especially true now that our QA team is relying on test2 as an automated test target.
Is there any reason why this shouldn't be a stated policy? If not, where should we state the policy so that people are aware of it?
test is very similar, only it doesn't run off the full cluster, just a single apache (and uses the nfs copy, so it's good to use before scapping). Whatever policy we come up with should clarify when to use test vs test2.
-Chad