[Maria-developers] MariaDB 5.5.37 release prep
![](https://secure.gravatar.com/avatar/4a806abaa17dcdb8f4ed6f1e0214ebc6.jpg?s=120&d=mm&r=g)
All, I've begun release prep for MariaDB 5.5.37. Draft changelog and release notes are at: - https://mariadb.com/kb/en/mariadb-5537-release-notes/ - https://mariadb.com/kb/en/mariadb-5537-changelog/ Please let me know ASAP of any notable things that should be mentioned in the release notes. Thanks! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com
![](https://secure.gravatar.com/avatar/114d2706a98c55129bf9e8aefa9e1d0a.jpg?s=120&d=mm&r=g)
Hey Daniel, Thanks for getting this started. Release notes:
XtraDB updated to the version from percona-server-5.5.36-34.0 TokuDB updated to version 7.1.5
upgraded from what? What was the previous version? Is there a link of readable changes (not code diffs) that occurred for this? Even including major additions and fixes here as sub-points would be good too as there are core and important parts of MariaDB. The change log mentions several assertion fixes, memory leaks, and potentially wrong results that should be in the release notes. It should also include major features and improvements, like the audit plugin that you've done, and improved performance in queries. I think there should be a separate section dealing with packaging errors broken up by platform. Also change log entries like Revision #4110.1.1 and others mentioning the internal functions of mysql not working in a particular way give really no clue as to the impact is for those not familiar with the code base. Trees of merges in changelog don't actually mean anything substantial to me. Is the audience of the change log the developers that have done the work? or some wider user base of mysql users? If so its not there yet. ----- Original Message -----
All,
I've begun release prep for MariaDB 5.5.37.
Draft changelog and release notes are at: - https://mariadb.com/kb/en/mariadb-5537-release-notes/ - https://mariadb.com/kb/en/mariadb-5537-changelog/
Please let me know ASAP of any notable things that should be mentioned in the release notes.
Thanks!
-- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
-- -- Daniel Black, Engineer @ Open Query (http://openquery.com.au) Remote expertise & maintenance for MySQL/MariaDB server environments.
![](https://secure.gravatar.com/avatar/e8e9eed7b5349571d2199b811463bcfe.jpg?s=120&d=mm&r=g)
For the TokuDB release, the changelog is available on the TokuDB "Users Guide" PDF at annex D (page 46) : http://www.tokutek.com/download.php?download_file=mysql-5.5.36-tokudb-7.1.5-... There doesnt seems to be a changelog directly available from a webpage at the moment. Le 17/04/2014 01:12, Daniel Black a écrit :
Hey Daniel,
Thanks for getting this started.
Release notes:
XtraDB updated to the version from percona-server-5.5.36-34.0 TokuDB updated to version 7.1.5 upgraded from what? What was the previous version? Is there a link of readable changes (not code diffs) that occurred for this? Even including major additions and fixes here as sub-points would be good too as there are core and important parts of MariaDB.
The change log mentions several assertion fixes, memory leaks, and potentially wrong results that should be in the release notes. It should also include major features and improvements, like the audit plugin that you've done, and improved performance in queries.
I think there should be a separate section dealing with packaging errors broken up by platform.
Also change log entries like Revision #4110.1.1 and others mentioning the internal functions of mysql not working in a particular way give really no clue as to the impact is for those not familiar with the code base. Trees of merges in changelog don't actually mean anything substantial to me. Is the audience of the change log the developers that have done the work? or some wider user base of mysql users? If so its not there yet.
----- Original Message -----
All,
I've begun release prep for MariaDB 5.5.37.
Draft changelog and release notes are at: - https://mariadb.com/kb/en/mariadb-5537-release-notes/ - https://mariadb.com/kb/en/mariadb-5537-changelog/
Please let me know ASAP of any notable things that should be mentioned in the release notes.
Thanks!
-- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
![](https://secure.gravatar.com/avatar/4a806abaa17dcdb8f4ed6f1e0214ebc6.jpg?s=120&d=mm&r=g)
On Wed, Apr 16, 2014 at 7:12 PM, Daniel Black
Thanks for getting this started.
You're welcome!
Release notes:
XtraDB updated to the version from percona-server-5.5.36-34.0 TokuDB updated to version 7.1.5
upgraded from what? What was the previous version? Is there a link of readable changes (not code diffs) that occurred for this? Even including major additions and fixes here as sub-points would be good too as there are core and important parts of MariaDB.
The versions of TokuDB in MariaDB are listed on the TokuDB page in the Knowledge Base: https://mariadb.com/kb/en/tokudb/ Likewise, the versions of XtraDB included in MariaDB are listed on the About XtraDB page: https://mariadb.com/kb/en/about-xtradb/ I've added a link to the release notes page to point people at the Percona changelog.
The change log mentions several assertion fixes, memory leaks, and potentially wrong results that should be in the release notes. It should also include major features and improvements, like the audit plugin that you've done, and improved performance in queries.
Please provide a list of the items you think should be in the release notes and I'll be happy to add them. You are, naturally, free to add them to the release notes page yourself if you'd like.
I think there should be a separate section dealing with packaging errors broken up by platform.
This would be a good thing to have. Would you like to do it?
Also change log entries like Revision #4110.1.1 and others mentioning the internal functions of mysql not working in a particular way give really no clue as to the impact is for those not familiar with the code base. Trees of merges in changelog don't actually mean anything substantial to me. Is the audience of the change log the developers that have done the work? or some wider user base of mysql users? If so its not there yet.
The changelog is no more than a list of every change made with the original message the developer made when making the push, the date and time of it, and a link to the change on launchpad so interested persons can see the code that was changed. I tend to think of the changelog as being more for developers (not just the MariaDB developers) and the release notes for everyone. The release notes could certainly be improved. It's just a matter of finding people to do the improving. Thanks for the feedback! -- Daniel Bartholomew, MariaDB Release Manager MariaDB | http://mariadb.com
participants (3)
-
Daniel Bartholomew
-
Daniel Black
-
Jean Weisbuch