Was sagt Scrum zu Releases während des Sprints?

And what does your Scrum Team think about that?

Scrum says: At/to the end of the Sprint the team delivers potentially releasable functionality; and the PO can decide when it is released.

Therefore Scrum does not prohibit releases during the Sprint. If the PO and the team in this request are in agreement when the two sides "finished" on the definition of and have the definition of "feature" agreed, if you have no fear of the loss of time due to frequent releases can give it a try and discuss in retrospect, if you also want to handle it more so. So Scrum does not forbid an intermediary release.

If the PO and the team want to have releases during the Sprint as soon as one of the features is Done, if they have agreed on the DoD (Definition of Done) and have the same understanding of what they mean by "feature", if they are not afraid to loose the time due to frequent releases, they can try it out. In the following retrospective they can decide, whether it was good or not. 

As such, one can only welcome this way of release handling, as this shortens the time to market for the singular functionalities/features. But it can possibly create a risk for the undisturbed development during the sprint, because the team will probably have to face the reaction of the users or stakeholders after each of the releases, or the PO falls into the temptation to cancel the sprint and to re-plan.