would define the subject matter as "bug fixes, testing and review", not "restructuring, testing and review." Different code structures are clearest to different hackers. Restructuring, on average, adds bugs even more quickly than feature development adds them.
+1 to this. Rewriting or restructuring code because you don't trust it (even though you have no reported real-world bugs) is a terrible idea.
Stopping all feature development to do it is even worse.
I would always 100% support a decision to push back new releases because of bugfixes for known issues, but if you think you might be able to find bugs in code you don't like, you should do that on your own time. Iff you find actual bugs, then you talk about halting new releases.
