Simetrical wrote:
On 9/7/07, brion(a)svn.wikimedia.org
<brion(a)svn.wikimedia.org> wrote:
They force operational work before we can update
the software again
Do they?
Yes.
I assumed that Wikimedia updates didn't actually
run
update.php, with schema changes done manually instead. I deliberately
committed nothing that depended on them, so if you updated the rest of
the software nothing would break from not doing the schema change
until you're ready.
I'd strongly recommend against doing that -- then we have inconsistent
state which causes all kinds of fun problems:
* newly created wikis get the new fields while old ones don't have them
* if the fields then get reverted or changed, we end up with some wikis
with the wrong fields present
* batched updates end up failing because multiple updates stomp on each
other's half-done implementations
* other code gets committed assuming the fields are there, breaking
unexpectedly on the live site
I was going to commit code actually using the new
stuff only after the schemas were updated, presumably in another batch
some time from now. What's problematic in that scenario?
They should come in together, so we can sensibly plan for it.
-- brion vibber (brion @
wikimedia.org)