The year/month scheme is much more honest about what's going on.
Possibly migrate the 'minor' version to a datecode and separate it from
the major revision number:
LibreOffice 7. 202404 release. (or 2404) and for bleeding edge
(2404.151515) where that's coded date--hh--mm, (there won't ever be
the version
or when passing the version to web-help)
* e.g. bugzilla notifications, tools that work on branch-names or
similar needs adjustments in addition
* FOSDEM/spring gives more time to prepare artwork, etc
The decision is to stay with the current 7.x family, and call the next
version
the version
or when passing the version to web-help)
* e.g. bugzilla notifications, tools that work on branch-names or
similar needs adjustments in addition
* FOSDEM/spring gives more time to prepare artwork, etc
The decision is to stay with the current 7.x family, and call the next
version
