Apologies for the delay, Maarten. I didn't have a chance to discuss that with the team in charge last week, but we did this week. The primary reason for Plesk to switch and stick to the current release scheme for all that time is due to the aim to deliver fast to major part of our audience in all possible meanings: stability, security, new scenarios. We understand that regardless of the utmost efforts we put in pre-release tests in order to ensure a stable build occasionally issues do arise and could result in unpleasant experience for some users. Still, it is hard or even impossible to do so with long-term release tears. For example security: panel relies on huge amount of third-party software (as we actually configure it). security updates and new versions are released very often. With old release tiers we will not be able to adopt it and deliver. The same for stability: software vendors release new versions with new functions and new problems - we need to adopt and deliver our product for this changes fast. The feedback (from all users) on how the process could be improved was forwarded to the corresponding team. It will be definitely taken into account and implemented in the feature if they decide the long-term impact of it will bring positives.