Hacker News new | ask | show | jobs
by 0cf8612b2e1e 405 days ago
A change is a change. I have certainly made a few “safe, meaningless, no possible way it could break something” edits which blew up in some unexpected way. Why take the risk for some inconsequential update? Someone has to sign off on why this commit needs to be fast tracked outside the normal process.
1 comments

Almost any software I can think of has different processes for testing/validating changes depending on impact/priority.

e.g. I'm typing this on Firefox, which has a much different process for point release vs their 4-week release cycle.