Id say every 3rd deployment or so, especially when new features are added, there is a lot of stress around cutting a release and deploying. People on the team become extra scrutinous of people who break the release build or don't have the features completed, or havent submitted enough tickets. Which, as a manager I appreciate the peer pressure, but I doubt the stress is good for moral of the members who are on the receiving end of it and I think the same feedback without the urgency behind it would be pedagogically more valuable.

Second, when a release is made and a bug is found there are branches mad from main (not develop) to fix the bugs, that must then be merged into develop (referred to as a merge-back) which increases surface area for errors as well as more time spend untangling the emerging web of branches. Now, in the hands of a capable engineer this isnt a massive lift, but also there are processes to automate all of this and that capability would be better spent day dreaming about a side project as far as I am concerned.

Have I persuaded you?