Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Tell people we need to roll back, clone the repo to my hard drive, open up git, undo the commit that merged the bad code in, push it. All done.

"Production"? Does that mean something that goes to the customers? Very few of our customers keep up with releases so it's generally not a big deal. We can have a release version sitting around for weeks before any customer actually installs it; some customers are happy with a five year old version and occasional custom patches.

I bet it's a bigger problem for those for whom the product is effectively a running website, but those of us operating a different software deployment model have a different set of problems.



You’re being downvoted but it’s a totally reasonable reply for normal vendor software.


Something I remind myself of regularly is that the entire software world I have ever experienced is actually a tiny, tiny piece of the real software world.


Yeah, these strategies are really only critical to client-server architectures where newly deployed code is immediately used by customers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: