>But once you let that one fly, there's no zero-bug policy left, right? If you know what the fix entails and have decided that the fix will make the product wo

>But once you let that one fly, there's no zero-bug policy left, right? If you know what the fix entails and have decided that the fix will make the product worse then that seems different than just not fixing a bug because it's not important enough to look into. If you don't know why the product is broken and what the fix will entail then there could be serious underlying problems that you don't know about and which are getting more expensive to fix with every passing day, but it sounds like that isn't a factor in this case. To me a zero bug policy doesn't mean that the product will work for every person and every use case, but rather that it's working as intended and there aren't things that are broken for reasons that no one understands.