4 ms·
> Maybe I am severely misinterpreting what happened here (apologies if I did), but to me it sounds like a he is blaming Google's review process when he should b
by jstarfish 3y ago
> Maybe I am severely misinterpreting what happened here (apologies if I did), but to me it sounds like a he is blaming Google's review process when he should be looking at his release and test practices.
While you make all good points, you're a career SWE who's already witnessed or made all of these mistakes enough to articulate what he should have done.
His own release and test practices be damned-- if devs can't quickly push a hotfix for a launch bug, I assume there is no framework to respond to anything more pressing (like security issues) in a timely manner either.
If you discover one of your libraries has been compromised, what's the quickest path to remediation in that scenario (that doesn't involve your app being de-listed altogether)?
- JCharante 3y ago> if devs can't quickly push a hotfix for a launch bug This is exactly why he should be very careful before pushing updates. It takes days to put out a fix and deploying on launch date instead of doing a soft launch would terrify any developer.
- penjelly 3y agoin my exp you have to fix it yourself if you want turnaround. so either log a bug and open a pr on the lib with a reasonable fix or fork and fix it yourself and publish or selfhost with jfrog/etc