[Maria-developers] MariaDB 5.2.6 release preparations
Hi Daniel, We are ready to release MariaDB 5.2.6! I tagged the release with the tag mariadb-5.2.6. The tree is lp:maria/5.2. This release introduces packages for Ubuntu 11.04 "Natty". I updated the scripts in lp:mariadb-tools, but you need to be aware if something on the download pages needs changing. Apart from this we merged XtraDB from Percona Server 5.1.56-12.7. Monty also merged latest MySQL 5.1 tree, but this does not correspond to any particular released version, so I afraid you have nothing but the bzr changelog to tell which bugfixes are included. The built packages should be in the usual place. The build number from Buildbot is 907. This release also introduces the new windows MSI/.zip packages that Wlad and Philip set up. Philip sent mail about how to obtain those (I think on a private mailing list), or you can ask one of them for help if needed. Unfortunately, despite Philip spending a lot of effort (and half his sanity I'm afraid) to get the windows hosts to run stably, there are still intermittent problems, so the 32-bit packages are not ready yet. However, I requested a rebuild from Buildbot, and they should hopefully appear eventually. I think that is it, let me know if there is anything else you need! - Kristian.
This release also introduces the new windows MSI/.zip packages that Wlad and Philip set up.
Daniel, please note that the Windows packages are *.ZIP and *.MSI. If you see an .EXE package, it was produced by the old NSIS installer. Such a package should not be made available for download. Philip Stoev
On Wed, 11 May 2011 16:27:04 +0300 "Philip Stoev" <pstoev@askmonty.org> wrote: Philip> > This release also introduces the new windows MSI/.zip Philip> > packages that Wlad and Philip> > Philip set up. Philip> Philip> Daniel, please note that the Windows packages are *.ZIP and Philip> *.MSI. If you see an .EXE package, it was produced by the old Philip> NSIS installer. Such a package should not be made available Philip> for download. Understood. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
On Wed, 11 May 2011 14:36:40 +0200 Kristian Nielsen <knielsen@knielsen-hq.org> wrote: Kristian> Hi Daniel, Kristian> Kristian> We are ready to release MariaDB 5.2.6! Kristian> Kristian> I tagged the release with the tag mariadb-5.2.6. The tree is Kristian> lp:maria/5.2. Kristian> Kristian> This release introduces packages for Ubuntu 11.04 "Natty". I Kristian> updated the scripts in lp:mariadb-tools, but you need to be Kristian> aware if something on the download pages needs changing. Kristian> Kristian> Apart from this we merged XtraDB from Percona Server Kristian> 5.1.56-12.7. Monty also merged latest MySQL 5.1 tree, but Kristian> this does not correspond to any particular released version, Kristian> so I afraid you have nothing but the bzr changelog to tell Kristian> which bugfixes are included. Kristian> Kristian> The built packages should be in the usual place. The build Kristian> number from Buildbot is 907. Kristian> Kristian> This release also introduces the new windows MSI/.zip Kristian> packages that Wlad and Philip set up. Philip sent mail about Kristian> how to obtain those (I think on a private mailing list), or Kristian> you can ask one of them for help if needed. Unfortunately, Kristian> despite Philip spending a lot of effort (and half his sanity Kristian> I'm afraid) to get the windows hosts to run stably, there are Kristian> still intermittent problems, so the 32-bit packages are not Kristian> ready yet. However, I requested a rebuild from Buildbot, and Kristian> they should hopefully appear eventually. Kristian> Kristian> I think that is it, let me know if there is anything else you Kristian> need! Thanks Kristian! The files have been uploaded to the primary mirror and are in the process of being replicated to the various MariaDB mirrors. Please take a look at the Release Notes and Changelog pages and let me know if anything is missing or needs to be changed. https://kb.askmonty.org/v/mariadb-526-release-notes https://kb.askmonty.org/v/mariadb-526-changelog FYI: The "Download" link on the above two pages is not active yet. Once all the mirrors have the files I will activate it. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
Daniel Bartholomew <dbart@montyprogram.com> writes:
Please take a look at the Release Notes and Changelog pages and let me know if anything is missing or needs to be changed.
"For MariaDB 5.2.6 we have merged in all of the changes from the MariaDB 5.1 source tree including all of the upstream changes from MySQL 5.1.57/58. The MySQL 5.1.57 and 5.1.58 release notes have details of what changes were made upstream by MySQL." Unfortunately, this is not what was done :-( Instead, we have some part of MySQL 5.1.57 (but not everything), and some part of .58. The precise point at which we merged is the bzr revision revid:nirbhay.choubey@oracle.com-20110427115410-vpeshiv6u5snkvzi The only real way of getting the list of exactly what MySQL changes are included in the merge is to compare the history for this revision using bzr. Not the way I would have prefered to do things, but that is how it was done.
Otherwise things look fine, as far as I can tell. Thanks! - Kristian.
On Thu, 12 May 2011 10:24:51 +0200 Kristian Nielsen <knielsen@knielsen-hq.org> wrote: Kristian> Daniel Bartholomew <dbart@montyprogram.com> writes: Daniel> Please take a look at the Release Notes and Changelog pages Daniel> and let me know if anything is missing or needs to be Daniel> changed. Daniel> Daniel> https://kb.askmonty.org/v/mariadb-526-release-notes Kristian> "For MariaDB 5.2.6 we have merged in all of the changes from Kristian> the MariaDB 5.1 source tree including all of the upstream Kristian> changes from MySQL 5.1.57/58. The MySQL 5.1.57 and 5.1.58 Kristian> release notes have details of what changes were made upstream Kristian> by MySQL." Kristian> Kristian> Unfortunately, this is not what was done :-( Kristian> Kristian> Instead, we have some part of MySQL 5.1.57 (but not Kristian> everything), and some part of .58. Kristian> Kristian> The precise point at which we merged is the bzr revision Kristian> Kristian> revid:nirbhay.choubey@oracle.com-20110427115410-vpeshiv6u5snkvzi Kristian> Kristian> The only real way of getting the list of exactly what MySQL Kristian> changes are included in the merge is to compare the history Kristian> for this revision using bzr. Kristian> Kristian> Not the way I would have prefered to do things, but that is Kristian> how it was done. Ok, sorry about that. I saw the commit message "Merge with MySQL 5.1.57/58" from http://bazaar.launchpad.net/~maria-captains/maria/5.2/revision/2643.124.2 and just assumed that it meant all of 5.1.57 and .58 were merged. Any suggestions for how to phrase it? I've removed "all of the" from the phrase "including all of the upstream changes from MySQL 5.1.57/58", and I've removed the links to the MySQL changelogs, but it's possible people might still assume that everything from 5.1.57/58 was merged. Creating a list of each change that we actually pulled in seems like overkill for a Release Notes page (it's supposed to just be the abbreviated highlights of the release). I suppose another option would be to remove that whole paragraph from the Release Notes. Let me know if you have any ideas on what to do. Daniel> https://kb.askmonty.org/v/mariadb-526-changelog Kristian> Kristian> Otherwise things look fine, as far as I can tell. Ok, thanks! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
Please take a look at the Release Notes and Changelog pages and let me know if anything is missing or needs to be changed.
https://kb.askmonty.org/v/mariadb-526-release-notes https://kb.askmonty.org/v/mariadb-526-changelog
FYI: The "Download" link on the above two pages is not active yet. Once all the mirrors have the files I will activate it.
Two items must be mentioned for windows - for the first time we have 64-bit windows packages - there is an upgrade wizard for converting MySQL instances to MariaDB Philip Stoev
Daniel Bartholomew <dbart@montyprogram.com> writes:
Any suggestions for how to phrase it? I've removed "all of the" from the phrase "including all of the upstream changes from MySQL 5.1.57/58", and I've removed the links to the MySQL changelogs, but it's possible people might still assume that everything from 5.1.57/58 was merged.
Yeah, it is not an easy job to write this up. I suggest just saying like it is, eg. like this: "MariaDB includes a merge from from MySQL 5.1 bazaar trunk. This merge does not correspond to a particular version of MySQL, but includes part of MySQL 5.1.57 and part of 5.1.58. The actual revision merged is revid:nirbhay.choubey@oracle.com-20110427115410-vpeshiv6u5snkvzi" And hopefully the next merge will be made properly so we will not have stuff like this. - Kristian.
On Thu, 12 May 2011 19:11:37 +0300 "Philip Stoev" <pstoev@askmonty.org> wrote: Daniel> Please take a look at the Release Notes and Changelog pages Daniel> and let me know if anything is missing or needs to be changed. Daniel> Daniel> https://kb.askmonty.org/v/mariadb-526-release-notes Daniel> https://kb.askmonty.org/v/mariadb-526-changelog Daniel> Daniel> FYI: The "Download" link on the above two pages is not active Daniel> yet. Once all the mirrors have the files I will activate it. Philip> Two items must be mentioned for windows Philip> - for the first time we have 64-bit windows packages Philip> - there is an upgrade wizard for converting MySQL instances to Philip> MariaDB I've added these to the Release Notes. Thanks! -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
On Thu, 12 May 2011 18:49:03 +0200 Kristian Nielsen <knielsen@knielsen-hq.org> wrote: Kristian> Daniel Bartholomew <dbart@montyprogram.com> writes: Daniel> Any suggestions for how to phrase it? I've removed "all of Daniel> the" from the phrase "including all of the upstream changes Daniel> from MySQL 5.1.57/58", and I've removed the links to the Daniel> MySQL changelogs, but it's possible people might still Daniel> assume that everything from 5.1.57/58 was merged. Kristian> Yeah, it is not an easy job to write this up. I suggest just Kristian> saying like it is, eg. like this: Kristian> Kristian> "MariaDB includes a merge from from MySQL 5.1 bazaar trunk. Kristian> This merge does not correspond to a particular version of Kristian> MySQL, but includes part of MySQL 5.1.57 and part of 5.1.58. Kristian> The actual revision merged is Kristian> revid:nirbhay.choubey@oracle.com-20110427115410-vpeshiv6u5snkvzi" Ok, thanks. I've updated the Release Notes with your revised wording. Kristian> And hopefully the next merge will be made properly so we will Kristian> not have stuff like this. Yes. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
Hi Daniel On 13/05/2011, at 12:05 AM, Daniel Bartholomew wrote:
Ok, sorry about that. I saw the commit message "Merge with MySQL 5.1.57/58" from http://bazaar.launchpad.net/~maria-captains/maria/5.2/revision/2643.124.2 and just assumed that it meant all of 5.1.57 and .58 were merged.
Any suggestions for how to phrase it? I've removed "all of the" from the phrase "including all of the upstream changes from MySQL 5.1.57/58", and I've removed the links to the MySQL changelogs, but it's possible people might still assume that everything from 5.1.57/58 was merged.
Creating a list of each change that we actually pulled in seems like overkill for a Release Notes page (it's supposed to just be the abbreviated highlights of the release).
People must be able to assess what the version contains. I've previously noted that an external reference is less than optimal, but is there a precise changelog of the MariaDB release that lists exactly which modifications were made (and as a matter of interest, which upstream version they came from, where relevant). While I agree with you that the release notes don't necessarily have to contain everything, as that's what a changelog is for. However, the changelog should be there. So in a nutshell, I think the list of each change pulled *should* be made, the remaining issue being where to publish it - I'm fine with MariaDB release notes referring to MariaDB changelog for more detail. Ref to a bzr branch merge is not sufficient, IMHO... it would put a lot of hassle on the shoulders of users and other parties (many of whom don't even have the expertise to assess the bzr log info to that extent) and that kind of stuff seriously hinders adoption - and it can even trigger people moving away. Regards, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Remote expertise & maintenance for MySQL/MariaDB server environments. Follow us at http://openquery.com/blog/ & http://twitter.com/openquery
On Fri, 13 May 2011 11:59:07 +1000 Arjen Lentz <arjen@openquery.com> wrote: Arjen> Hi Daniel Hello! Arjen> On 13/05/2011, at 12:05 AM, Daniel Bartholomew wrote: <snip> Daniel> Creating a list of each change that we actually pulled in Daniel> seems like overkill for a Release Notes page (it's supposed to Daniel> just be the abbreviated highlights of the release). Arjen> People must be able to assess what the version contains. Arjen> I've previously noted that an external reference is less than Arjen> optimal, but is there a precise changelog of the MariaDB release Arjen> that lists exactly which modifications were made (and as a Arjen> matter of interest, which upstream version they came from, where Arjen> relevant). Yes. There is a changelog for this release (and all prior releases). For 5.2.6, the changelog is here: https://kb.askmonty.org/v/mariadb-526-changelog The Changelog is linked to from the download page and from the release notes. Arjen> While I agree with you that the release notes don't necessarily Arjen> have to contain everything, as that's what a changelog is for. Arjen> However, the changelog should be there. So in a nutshell, I Arjen> think the list of each change pulled *should* be made, the Arjen> remaining issue being where to publish it - I'm fine with Arjen> MariaDB release notes referring to MariaDB changelog for more Arjen> detail. Arjen> Arjen> Ref to a bzr branch merge is not sufficient, IMHO... it would Arjen> put a lot of hassle on the shoulders of users and other parties Arjen> (many of whom don't even have the expertise to assess the bzr Arjen> log info to that extent) and that kind of stuff seriously Arjen> hinders adoption - and it can even trigger people moving away. If you have any suggestions for improving the changelog, let me know. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
participants (4)
-
Arjen Lentz -
Daniel Bartholomew -
Kristian Nielsen -
Philip Stoev