MARIADB company, smoking with the same non-profit organization, developing a database server mariadb , was anosaled a significant change in the schedule for forming the MARIADB Community Server assembly and its support schemes. Until now, MariaDB has formed one significant branch once a year and ensured its support for about 5 years. According to the new scheme, significant releases containing functional changes will emerge once a quarter and maintain only a year.
In the official report talking about “desire to accelerate innovation to the community,” that, in fact, no more than marketing, as the MARIADB team also practiced the budget of new functionality in intermediate issues, which seriously dispelled with statements about adherence The rules of semantic versioning, as well as more than once, the cause of regressive changes that even allowed the full review of the issues.
Apparently, a new release scheme is a means of promoting the Enterprise Server assembly produced by MariaDB Corporation exclusively for its subscribers. Changing the development cycle and reducing the Community-assembly accompaniment time will make it less attractive for use in working environments, which is perceived as an attempt to attract new subscribers to a paid edition.
As a new development schedule is reflected on Linux distributions is not clear yet. In a press release, it is said without clarifying details that “collaboration with distributions” is going on to provide support for a longer period and preparation of a special version, which will be best suited for the accompaniment model of each distribution. Considering that now the delivery of the MariaDB server is even such leading distributions as RHEL, noticeably lags behind the current versions, one can expect that the change in the development model will only aggravate the situation.