Sample release publication

### How to use GitHub

* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.

---

## Feature request

Releases of new major versions (`x.y.0`) are frequently problematic (e.g., [the recent 4.0.0 release](https://github.com/nextcloud/desktop/issues/8915)), often causing significant issues for hundreds of users.

While it’s true that some bugs are only detected after widespread deployment, we should still mitigate risks, for example, by rolling out these versions incrementally.

Drawing inspiration from A/B testing in web marketing, could we implement a phased release strategy?
1. **`x.y.0` versions** → Deploy to **10% of users**
2. **`x.y.1` versions** → Deploy to **40% of users**
3. **`x.y.2` versions** → Deploy to **100% of users**

This approach would allow us to continue releasing new versions while minimizing risks.