-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11-05-18 02:38 PM, Robert Collins wrote: > On Thu, May 19, 2011 at 1:18 AM, Aaron Bentley <aa...@canonical.com> wrote: >> But it would be an awesome one to change, because it would allow us to >> spin up instances of Launchpad at will. That would allow us to QA our >> work immediately after it hits (db-)devel. > > I don't see how it permits that any more efficiently than we do today > - we already spin up new code in < 30 minutes after it hits trunk.
By "trunk", do you mean stable or devel? I mean devel. > The > bulk of the delay is in code updates. We can't just spin up some vms > and solve the problem because we're dealing with constraints like a > 300GB DB that takes a day to restore. For stuff that doesn't make schema changes, can't we just backend onto our current qastaging db server? > I suspect that in the short term we need a 1:1 mapping for the API, > but the behaviours of the model objects would not be duplicated to the > template service, only the surface - what attributes exist. Methods > for the API we would want to explicitly map I think. This could work, but I think there's a risk that we'd take on a lot of extra redundancy. Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3UFvAACgkQ0F+nu1YWqI01eQCfQh5WK2b1TLuKnoB25HWbPrjO k30An0lDhMRw2PiaRO73bUkYxgQ1Hm5/ =le7D -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
