Isabella Kennedy arrived at 7:03 p.m. Eight pounds, 12 oz. Mom and baby are fine. Now, for the important bit…
I had trouble versioning this one. Was she Deane 2.0 or 5.0? She is my daughter — a direct descendent of 1.0 — hence a 2.0.
However, she’s the fifth member of the family. Since my wife and I work the bugs out of the child-rearing process with each release, I think she needs to be a 5.0 to reflect the maturity of the product.
But do I count my wife? I really didn’t work any bugs out of her (she’s still trying to work them out of me). Maybe she and I are 1.0 together, making Isabella a 4.0 release (Alec would have been 2.0; Gabrielle, 3.0).
Perhaps that’s the closest I’m going to get. I could throw in the fact that Alec is my stepson, technically making him a merge or integration of some kind. When you merge a 1.0 and 2.0, what version do you end up with? 1.5?
Forget it. I’m sticking with a 4.0 release. I would push it further, but I don’t want to seem like a geek or anything.
Frigits: I'm a big fan of refrigerators, being as that's where all the food is. But here's another reason to like them. I found Frigits in a little gift shop, and played non-stop for 15 minutes until my wife walked by and I suddenly pretended to be interested in a…
Well, here we are at #4,000. This puts us just 1,000 posts away from our stated goal of 5,000. Along with the 4,000 posts, we have 6,050 comments as of this writing, and that's very cool. We appreciate all the interaction everyone has with the site. Interestingly, we…
While I was hanging out at the hospital waiting for the new addition, I got to wondering if RSS has to be "pull" by definition. Could you "push" updates from a site to a client? Say you have a notification client — a little app that sits on your desktop.…
Congratulations!
Hi Deane... congratulations... I hope all is well with mum and 4.0!
Woo hoo! Awesome! Congrats Deane!
Woo hoo! Congrats!
The trouble I see with your versioning system is that a new version number is an indication of a revision to an existing product, implying that bugs have been fixed, features added, and performance has been tweaked, and the new release is intended to supplant earlier releases.
As a Dad of four, I know that in reality each kid is a unique product, with unique features, capabilities, and bugs. Those bugs usually get worked out in time, so maybe each birthday, or each phase of each kid's life, would be a new version. But even so, I think all my kids are still in alpha, or maybe beta. I'm a little protective that way.
Psalm 127:4-5
Congrats buddy! Where are the pictures?
I think Dave's right. What you're working with here are forks based off of a code merge of two seperate original projects. I think each kid is on their own branch. You're going to need to get them into a versioning system to keep track of it all.
Congratulations Deano!
Congratulations, Deane!
Third child? version 2.2
the next generation would be 3.0 etc
Long distance congrats, bud!!!
Congratulations on the new kid, Deane. It's good to affirm that there are other tech guys out there with the skill and social graces for procreation.
Perhaps the version number system is flawed and you should switch to something like MX, SC, XP, or '04?
Please, Owen; anything but that!
But you know, come to think of it, my 5 year old could be the ME version, because the world revolves around him. ;o)
I'm thinking year-based numbering. Gabrielle would be "Deane 2001"; Isabella, "Deane 2004".