[sf-perl] Escalation or something else?

Michael Friedman friedman at highwire.stanford.edu
Sun May 4 20:11:56 PDT 2008


It all depends on the situation. I work on web apps. We release  
weekly. If something comes up an hour before the release, we don't  
install it and fix it before the next release.

If instead you have to make a 4 pm deadline to get the image to the CD  
printer to run off 20,000 discs and if you miss it it will cost you a  
$10,000 fine, you'll probably ship with it as is.

On the other hand, if you don't release constantly, why is a new  
feature only being tested an hour before release? That seems like a  
systemic problem right there.

My $.02,
-- Mike

On May 4, 2008, at 6:54 PM, Neil Heller wrote:

> In the following situation, what is your opinion of the best course of
> action?
> As a developer, you have completed a module and have moved it for  
> testing.
> A tester discovers a bug of mid-severity.
> You say "that's no bug, that's a feature.  Besides, the release is 1  
> hour
> away."
> Does the tester escalate the problem to his manager?
> Does the code get released with the bug (feature)?
> Does something else happen?
> _______________________________________________
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm

Michael Friedman                     HighWire Press
Phone: 650-725-1974                  Stanford University
FAX:   270-721-8034                  <friedman at highwire.stanford.edu>

More information about the SanFrancisco-pm mailing list