The release cannot be delayed, but quality suffers. What is the priority?

In a situation where a release cannot be delayed but quality suffers, the priority depends on the context, but usually it is more important to minimize risks for users and the business. If the quality leaves much to be desired, it is worth:

• Assessing the criticality of issues: bugs that could lead to crashes, data loss, or security vulnerabilities require immediate fixing.
• Implementing monitoring and quick response to incidents after the release.
• Planning quick patches and updates.

Thus, the priority is to ensure stability and minimize negative impact on users, even if it means releasing a version with known but non-critical issues. It is also important to improve development processes so that in the future, quality does not suffer due to tight deadlines.