Re:Software Update Destroys $286M Japanese Satellite
by samwestdev on Monday May 09, 2016 @06:12PM
(#11663643)
Guys always read the change log before upgrading
[ Parent
| on HN ]
Re:Software Update Destroys $286M Japanese Satellite
by askafriend on Monday May 09, 2016 @06:14PM
(#11663654)
You mean changelogs like these? https://twitter.com/cirbif/status/728114363563839488
Re:Software Update Destroys $286M Japanese Satellite
by aaron695 on Monday May 09, 2016 @06:35PM
(#11663773)
I find this useless advice.
I didn't write or are aware of much of the code I'm part of.
Or remember some of the code I did write.
Or even understand the ramifications of what the change log means.
All assuming it's a well written change log.
You need external process to ensure upgrades don't break things.
Not a 'read the change log' policy so someone can blame you post breakage cause then it'll be easy to find issues in the change log.