Comments on: Beat on “state of the dolphin” (or: Why Software is never really ready until a .20 release) http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/ Ramblings which occasionally resemble reality. This is the blog of Stewart Smith. Mon, 30 Aug 2010 10:19:35 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: thoughts on MySQL release cycle | Ramblings http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-87662 thoughts on MySQL release cycle | Ramblings Fri, 10 Aug 2007 01:13:21 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-87662 [...] passed the dot-twenty rule for a release that doesn’t annoy [...] [...] passed the dot-twenty rule for a release that doesn’t annoy [...]

]]> By: Eric Bergen » MySQL User Conference 2006 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-29601 Eric Bergen » MySQL User Conference 2006 Tue, 02 May 2006 03:30:48 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-29601 [...] It was interesting walking around the conference meeting different people from various backgrounds and professions. The conference sessions were well suited to the crowd. Some where internals oriented, some howto, and some for the business people. I would like to see more internals presentations next year but that is because I’m more of an internals guy. Overall the sessions were of great quality and the ones I was able to attend were very informative. In between sessions people broke off into little conversation groups. This conversation settled around either constructive critisism about mysql or mysql ab (bugs.mysql ect) or thinking through a problem and coming up with a solution. One of the projects I want to do because of this conversation is run some stats on the bugs database vs mysql releases and the frequency of those releases. I have a feeling there is a sharp increase in the number of bugs due to premature releases in the 5.1 tree. The bugs site has statistics on the number of bugs by month but no correlation to the patch version of mysql at the time. I think it’s important to collect these metrics to see how accurate the dot-twenty theory is. I have a feeling it’s pretty close but that a more exact version can be found based on the time between releases and the number of bugs filed against that release. That’s for another blog entry. [...] [...] It was interesting walking around the conference meeting different people from various backgrounds and professions. The conference sessions were well suited to the crowd. Some where internals oriented, some howto, and some for the business people. I would like to see more internals presentations next year but that is because I’m more of an internals guy. Overall the sessions were of great quality and the ones I was able to attend were very informative. In between sessions people broke off into little conversation groups. This conversation settled around either constructive critisism about mysql or mysql ab (bugs.mysql ect) or thinking through a problem and coming up with a solution. One of the projects I want to do because of this conversation is run some stats on the bugs database vs mysql releases and the frequency of those releases. I have a feeling there is a sharp increase in the number of bugs due to premature releases in the 5.1 tree. The bugs site has statistics on the number of bugs by month but no correlation to the patch version of mysql at the time. I think it’s important to collect these metrics to see how accurate the dot-twenty theory is. I have a feeling it’s pretty close but that a more exact version can be found based on the time between releases and the number of bugs filed against that release. That’s for another blog entry. [...]

]]> By: Jason A http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-28592 Jason A Thu, 20 Apr 2006 20:49:19 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-28592 Explained here: http://people.planetpostgresql.org/xzilla/index.php?/archives/183-Debian-PostgreSQL-Versioning.html Explained here:

http://people.planetpostgresql.org/xzilla/index.php?/archives/183-Debian-PostgreSQL-Versioning.html

]]> By: zillablog http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-28571 zillablog Thu, 20 Apr 2006 15:53:04 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-28571 <strong>Debian PostgreSQL Versioning</strong> Stewart over at Flaming Spork posits the theory that software at version X.X.0 can be expected to not work, that by X.X.10 it get's pretty good, and by X.X.20 it is actually something you can use without worry. He names a number of projects that foll... Debian PostgreSQL Versioning

Stewart over at Flaming Spork posits the theory that software at version X.X.0 can be expected to not work, that by X.X.10 it get’s pretty good, and by X.X.20 it is actually something you can use without worry. He names a number of projects that foll…

]]> By: MacPlusG3 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-28480 MacPlusG3 Wed, 19 Apr 2006 13:50:38 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-28480 Yeah... after looking at postgresql.org I'm a bit confused too. $ dpkg -l postgresql Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii postgresql 7.5.9 object-relational SQL database management sy stewart@willster:~/$ psql Welcome to psql 7.4.8, the PostgreSQL interactive terminal. fascinating. Yeah… after looking at postgresql.org I’m a bit confused too.

$ dpkg -l postgresql
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii postgresql 7.5.9 object-relational SQL database management sy
stewart@willster:~/$ psql
Welcome to psql 7.4.8, the PostgreSQL interactive terminal.

fascinating.

]]> By: pabloj http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/comment-page-1/#comment-28479 pabloj Wed, 19 Apr 2006 13:26:17 +0000 http://www.flamingspork.com/blog/2006/04/19/beat-on-state-of-the-dolphin-or-why-software-is-never-really-ready-until-a-20-release/#comment-28479 " ...The version of postgresql is 7.5.9 over here… " Uhhh? ” …The version of postgresql is 7.5.9 over here… ”

Uhhh?

]]>