There is a reason why we have prioritisation and bug triages.

I am working on a project with an associate and one of the first things I did was install a kanban board to keep track of issues and features, and to have a place where we can share information on the state of the project and build.

This way, we can be honest and communicate about the compromises between time until a feature is ready to use, and not worrying about things that they are not concerned about. If a feature is going to make things much better for their business, and not break things that are already there, and the current bugs only occur in unlikely circumstances? Ship time.

All software has bugs. We need to test the software to be aware of the bugs that exist and take appropriate action.

The alternative is Duke Nukem Forever and Time

Of course, this is an engineering tradeoff. You can also ship broken code that makes things worse. The engineering aspect is that you make the correct tradeoff between the reality of what can happen in reality with what you are trying to achieve in theory.