Slashdot Mirror


How Fast is Your Turnaround Time?

petrus.burdigala writes "I work for a mid-sized commercial software company (~20 Mloc) and we are frequently challenged by our supervisors to get fixes around the clock. Overall, we manage to get a 'bullet-proof' patch in about 4-5 weeks (from coding->QA->Build/Packaging->shipment), which I consider not so bad. But the other day, we got an urgent request from our support team to come up with a decent fix in 48 hours. I think they're a tiny bit unrealistic. So I wanted to get feedback from my peers: are we doing that bad? It takes months for other software vendors to issue zero-day exploit fixes, are our customers being unreasonable?"

1 of 418 comments (clear)

  1. Patching Bugs by ishpeck · · Score: 0, Offtopic

    My company can patch bugs within the same day the product's released. Never gone more than two days between a customer's bug report and a fix.

    But we don't let bugs slip by. I know since I'm on the QA team. Never a bug. Never once... :P

    --

    "If I were to ask you a hypothetical question, what would you like it to be about?"