The New Bugzilla::DB::Schema

[Shane H. W. Travis]

On Thu, 10 Mar 2005, Gervase Markham wrote:

> Is there any chance of more of a heads-up about this sort of change,
> given that it automatically obsoletes every patch which modifies the
> schema?
...
> Please a) could we have a bit more warning about patch-breaking patches,

Honest question: why?

I understand that it's frustrating when someone else's patch invalidates
yours and you have to go back and fix the bitrot *again*. (This change also
broke my patch on bug 98123, causing me to have to update the patch to v7 so
I know where you're coming from.

But as I said... even if one knew it was coming, what good would it do?
*Someone* has to do the work of making the code in patch A play nice with
the code in patch B wherever they conflict. It's just as frustrating for the
Patch A author when someone checks in yet another !@$%# patch that they have
to adapt and move.

So as I said, I'm wondering... what good would it do to have more advance
notice? Mental preparation -- steeling oneself to the fact that one's patch
isn't going to land *this* time either? Incentive to work faster so your
patch lands first, this forcing the other guy do the work instead of you?

I really don't know, and I'm curious.

Shane H.W. Travis       | The greatest of all mistakes is to do nothing
travis at sedsystems.ca    |  because you can only do a little.
Saskatoon, Saskatchewan |   Do what you can.  -- Sydney Smith