4 ms·
I wasn't referring to task difficulty, just the extreme time delay between when something is ready and when it is put into production.
by tdavis 18y ago
I wasn't referring to task difficulty, just the extreme time delay between when something is ready and when it is put into production.
- trapper 18y agoI was referring to development & production deployments in both examples.
- jodrellblank 18y agoThe delay is between when it's first claimed finished by the author(s) and when it's agreed to be ready by everyone involved. After that it can be deployed instantly... I guess it would be possible to note in a bug tracking app "we would have deployed here" and then see how many, and what kind of bugs were found between then and actual deployment, which checks found them, and whether any of those were rollback-causers. That would give an estimate of how much good the checks did in each case, and a way to choose which checks are ineffective for their cost. (Ish - some checks may only trigger once, ever, to be priceless).