-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just got a bunch of strange test failures because there had been sampledata changes, and I didn't run "make schema". They were Soyuz test failures, so I asked Julian about it, and he got Muharem involved. So there was a cost in terms of wasted time.
I don't like to run make schema more than I have to, because it's slow and it clears any local changes I've made. And I only *know* I have to run it if there have been schema changes. Would it make sense to have a policy of landing sampledata updates in db-devel instead? That's where I'd expect to find database changes, and schema updates might have forced me to run "make schema" anyway. Alternatively, automated detection of stale sampledata would have caught the issue early. Thoughts? Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksNbTEACgkQ0F+nu1YWqI3FawCeK2DdtXhkWqtDyDDQce/Yt2uO /ycAoIHQX7Ty27BeIkAqN8w1swtXhkbI =1SQ4 -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
