Should the release be moved upon discovering a problem? Why or why not?

Moving a release upon discovering a problem is usually not recommended, especially if the problem is critical or affects functionality.

Why not:

• A release with an error can lead to a degraded user experience or even data loss.
• Fixing the problem after release is more difficult and costly.
• The product and team reputation may suffer.

However, if the problem is minor and does not affect core functions, and a delay in release is critical (for example, due to business requirements), it is possible to move the release with a subsequent quick patch.

Ideally:

• Detect and fix problems before release
• Use automated testing
• Implement CI/CD practices with the ability to quickly rollback

Thus, the decision depends on the nature of the problem and the business context, but in most cases, it is better not to release with known errors.