A few days behind schedule, we can announce that the new beta – version 5.0.14 – has reached our mirrors. A bunch of improvements and fixes are incorporated in this release. The software rendering mode has been changed to using Windows GDI instead of the mesa-library. This change brings a big (and badly needed) performance boost when using MySQL Workbench without openGL rendering. There are further improvements like the brushed up property editor, new view-options on the overview page or manually resizable table-objects. Code has been cleaned up extensively and over 30 bugs has been squashed since 5.0.13. Take a look at our Releases Page to read all the dirty details.
Please check out the new release and see whats new and better.
We are about to release the next Beta version of MySQL Workbench. There are no new additions like in the last release. This will strictly be a bug-fix build. Apart from several smaller fixes this build will see an improved software rendering performance. Alfredo has blogged about the changes in his last post. And the changes are really paying off. Tax tested it on several machines and found the speed to be acceptable even on older machines.
The slow and flickering software rendering has been one of the major points of complain (except from the yet missing Linux and OS X versions that will be released later this year). Now that this is out of the way we are marching towards the RC level, fast.
If there are no new obstacles the release build will happen later today. Markus from the web team will get online on Saturday or early Sunday to update the download pages. Then we will send out the announce emails asap.
The latest Version of our beta-candidate 5.0.13 is finally available on our servers. About 70 bugs have been addressed since 5.0.12.Workbench now features a nifty update module (can be found via the help item in the main menu) and additionally the Standard Edition has a new Catalog Diff Report Module that allows you to compare two database-catalogs and creating a text-report. This Diff-Report Module lets you select two catalogs which can be taken from the actual document, a file or a live connection to a database-server. The interface of the new module is likely to go through some changes during the next stages to GA but we decided to introduce the feature in this beta version.Have a look at the Releases Page for detailed Information on the progress of the project.
We finally got WB 5.0.12 released. It was a bit complicated to get it out because everybody was on his way to the MySQL All Company Meeting here in Orlando, Fl, and with all the meetings going on. 5.0.12 is a next important step to get closer to RC. We did not fix as many bugs as for the last releases – partly caused by the vacations around X-Mas but as well because the number of serious issues is going down. There is still a lot to be done though but the light at the end of the tunnel is clearly visible already.
Btw., if somebody did not get the news yet (which I don’t think is possible), MySQL has been aquired by Sun. It is the biggest topic here at the All Company Meeting and I think it was the best thing that could happen for MySQL as a product and for the community. What it means for the MySQL Workbench project for the moment is, that nothing will change. We will continue our road to GA as planned and are currently putting together the feature set for the WB 5.1 release. But I think there might be some very good things happening for the community in the future.
We just unleashed version 5.0.11 Beta of MySQL Workbench. We fixed the nasty bug, that prevented us from releasing .11 earlier. To find out what’s new take a look at this page (You can trace all changes in detail here).
Although the filenames say 5.0.11a (notice the trailing ‘a’), what’s actually inside the packages is our official 5.0.11 beta release. That’s because we had already uploaded the files to our mirrors when we found that index-related bug on monday – so the fastest way for this release was, to add the suffix.
Please fetch the new release right away and keep up your good work with testing and reporting bugs.
For all new contributors devoted to quality, FAQ was slightly updated with new section.
We are working hard on the next release of MySQL Workbench and are trying to follow our plan of getting a release out every second week. A lot of things have already been addressed, some new things came up. But we are clearly moving into the right direction and our investments in unit tests and UI tests seems to pay off as expected. More details in a post later this week.
I just sent out the mail to the mailing lists to officially announce the 5.0.10 release. I have added an additional page that will keep track of the changes we make and it is available here. The change log file is included in the source package as well of course.
I am curious how the level of regression bugs will be. For Workbench we have a unit testing framework in place as well as an ever expanding suite of UI tests. We are using TestComplete and as long as the tool does not crash itself (which happens quite a lot, sadly) it is quite useful to automated the UI testing.
Please keep testing and reporting bugs. We will keep working hard to fix reported issues as fast as possible.
Today at 19:25 CET I announced the availability of the first official Beta release of MySQL Workbench.I wrote that this marks a milestone for my team and this is absolutely true. We have very high ambitions with this project for the years to come and getting the core of the implementation done right is crucial for any success. Sure there are still bugs, sure we still have to remove some rough edges but the core is there. And after 20 years coding since I wrote my first lines in Basic when I was 12, let me tell you – this core is right. And now we can stabilize and improve upon it.The last months have been quite a challenge for my team and myself. Working 50-80h weeks do mean serious compromises on your personal life but if you believe in something you are ready to walk the extra miles to get it done right.So at this point I would like to thank every member of the team (and the girlfriends who have been extra-forgiving) and all the people inside of MySQL who made this possible – you rock!We will continue to keep working hard for the next months to fix all bugs that our community and our SE Beta testers will report to get the tool stable and into RC and GA as soon as possible.MikeZp.s.: I’m sorry if this posting may sound a bit greasy but this was an emotional moment 🙂
If you are on Linux or OS X you might ask why we have decided to first release on the Windows platform. And why the releases for Linux and OS X will happen a few months later. Here is why.
We believe we can deliver better quality if we focus on one platform first. By having the whole team focusing on one platform we can get a release out sooner than it would be possible by supporting all three platforms from the beginning.
And the sooner we release, the earlier we get bug reports. And this benefits the quality. When we are going to release on the other platforms the back-end code will already be well community-tested. And even the first releases on Linux and OS X will have a decent quality.
But why did we choose Windows as the first platform? Actually, it was not us – it was you, our users. Looking at the bug reports we got for the old GUI tools it is clear that 90% of the reports are for Windows. And that made the choice easy.
The question remains why we do not use Java or a cross platform GUI toolkit. The answer for that is that a lot of developers do not want Java to be installed on their development machine. I personally love Java as a language but I can see their point, so that was not an option. For the cross platform GUI toolkits – we have tried a number of them. But non of them really delivered what we needed.
So I hope our fellow Linux and OS X users (I’m on OS X now as well) will understand our motivation behind this decision and will be even more happy when they are going to try Workbench on their platform and find it working very well.