launchpad-dev team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

> The db-stable report is at :
> https://devpad.canonical.com/~lpqateam/qa_reports/deployment-db-stable.html.
> Just like the The db-stable report is at :
> https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
> report, you should look at this ~12 (*) hours after sending a change
> to EC2 (4-5 hours in EC2, 4-5 + up to 4-5 for the run before to
> complete in buildbot, then 2 hours to deploy on staging).

Just a comment. 12 hours is a rather unreasonable expectation.
Specifically, nobody *should* be working 12 hours after they have
submitted something. Either they do it at the beginning of their day,
and 12 hours is past when they should stop. Or they do it at the end of
their day, and 12 hours is before they start again.

I realize many of us don't work a regular 8-hour block. But I'm pretty
sure that is the official expectation.

I don't have a great answer for this, but it really means 'check the
next day'. If that is too long of a delay, then you really need a
different process.

Maybe I'm being a stickler, but you shouldn't have to log on before you
go to bed so that you don't back up the deployment queue. If you *can*
that's nice and helpful, but it certainly shouldn't be an expectation.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2UGXkACgkQJdeBCYSNAAOOmQCdHLPtq0t+M2NU7VPkPNFPJbIT
mikAoJ9WR7xtgupSH6Fct6OUUkf33jpP
=nCSG
-----END PGP SIGNATURE-----