The Artima Developer Community
Sponsored Link

Agile Buzz Forum
What's the Point Zero for Anyway?

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
What's the Point Zero for Anyway? Posted: Feb 8, 2005 2:30 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: What's the Point Zero for Anyway?
Feed Title: Travis Griggs - Blog
Feed URL: http://www.cincomsmalltalk.com/rssBlog/travis-rss.xml
Feed Description: This TAG Line is Extra
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Travis Griggs - Blog

Advertisement
Chris Petrilli claims that the practice of versioning with 0.X.Y.Z is useless. He calls on said releasee's to release with real version 1.0's. And then 2.0. Etc.

I'll take it a bit further. Why put the .0 there anyway? It's a waste. Just release with version 0. And then 1. And then 2. If and when you branch, use a some sort of suffix to split it free. What is with the .0 though? How often is it really worth while? The supposition seems to be an attempt to communicate "this is the real thing". But everyone knows from experience, that a .0 release rarely lives up to it's author's expectation. It is a later point release that becomes everybody's favorite.

Left with this ambiguity, no ignorant person can look at your personalized/customized value judgements about when to increment what part of the version, and discern whatever it is you had in mind. The only real value is that a) this version is later or earlier than that other version, b) an urban concensus has congealed around known good releases ("ah, it's the 3.14.59 version that you wanted, *that's the good one!!")

My theory on this silliness is that it's what our tools teach us to do. It's all in whatever template your versioning system tends to proffer as the default version. A long time ago, certain case/source code tools liked to default to w.x.y.z value. So out came 1.0.0.0, and then 1.0.0.1, followed by 1.0.0.2. This was patently and obviously preposterous, so that faded quick, and we moved into the realm of just X.Y.Z. The religion of the "major-minor-maintenance". A lot of stuff is still there. But I've noticed more people are in the A.B versions now. In the VW Store system, this is the default. I hope we move beyond this soon too. Automated build systems' inability to deduce what is major and what is minor leave me to hope we'll get there yet.

For years, I watched NT 4.0a boot. I knew the 4.0a thing was a total marketting moniker. What really mattered was that it said "build 1381".

Read: What's the Point Zero for Anyway?

Topic: Programming, thirty years later Previous Topic   Next Topic Topic: Update to the new RSS book

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use