-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/29/2011 04:24 PM, Aaron Bentley wrote: > On 11-03-29 12:11 AM, Robert Collins wrote: >> - We make the 'please merge db-stable rev XXX to devel' a team >> responsibility, just like nodowntime deploys. I'll happily put the TA >> team up as a backstop for this - we'll make sure it happens. > > I don't understand. A db merge is harmful because it prevents further > nodowntime deployments. Do we really want to do this frequently? > > Aaron
I think you missed this part: > - We stop tagging bugs with milestones - we deploy only a few changes > in each deploy, and we don't do feature releases at the same time. We > also will be doing *more* downtime deploys as we get faster DB > deployments sorted out. > So coupled with more "please merge db-stable rev XXX" is "more downtime deploys". I know one of the feature issues Francis highlighted was getting the "time to deploy feature" down to 45(?) days. And if you have to have 2 downtime db deploys (estimated average cost?) then you can't do it with a downtime only once per month. I would say that if you can get downtime to something like a consistent <30min or whatever, then it is probably fine to have more than one a month. But that doesn't give you much "stuff is fubar, rollback" time. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2R7aEACgkQJdeBCYSNAAPPngCePQYOktba6j8oQsi9PLaN7MfU 2ooAoJAjQEOU422av17UmQnskeTZKKUM =HUkl -----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
