@mkj@nick@norden.social@nick@hhmx.de Right, but the vast majority of our end users don't know what version numbers mean, so going from eg 7.1 to 9.3 doesn't say anything to them. Using year.month gives them a bit more context. We've done research and listened to our users, and many want this.
Of course, others won't be happy. Any time we make any change, some people are happy, some not. Version numbers don't just exist in a vacuum, and we'll provide more context about the degree of change in our announcements.
@nick@norden.social@nick@hhmx.de Oh sure, it was never arbitrary for us – but for the vast majority of end users, who aren't familiar with release schedules, version numbering systems etc., "7.6" doesn't say much.
And you're right about keeping sysadmins and engineers in the loop, so any changes in those contexts will be clear in our announcements, release notes and other places. But please do let us know if we can improve something! 😊
@nick@norden.social@nick@hhmx.de Not maintenance – as mentioned, we'll have two big updates every year, with lots of new features, exactly the same as now. Nothing changes in the release engineering.
Re: the other point, it's not about advertising. Many people are using old versions of LibreOffice, and having a year+month version number (and communicating that well) can help. For the vast majority of end users, that year+month number says more than just some arbitrary thing that we choose. That's our view anyway 😊
@nick@norden.social@nick@hhmx.de Ah OK, we see what you mean. LibreOffice will continue to have two big updates a year (plus many small revisions), so that doesn't change. The big number will be fixed to the year so we can't change that for a huge "generation" update, yes. But the software is also mature now after 12 years of development so we think this is a better approach. Good to have feedback though...
@nick But it's the same – LibreOffice 7.6 (big number, smaller number) becomes 24.2. The release schedule is staying the same. Nothing changes in how we make the software, but the version numbers now reflect the year and month the software was released, rather than being just arbitrary X.X numbers.
@sysgeek Nothing to worry about – it doesn't change anything about our schedule. It's only a numbering change. If we have to delay a release to fix something important, we'll always do it! 😊