The Artima Developer Community
Sponsored Link

Java Answers Forum
Version Numbering - Best Practice?

3 replies on 1 page. Most recent reply: Dec 5, 2003 1:50 PM by fatih karakurt

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 3 replies on 1 page
Vincent O'Sullivan

Posts: 724
Nickname: vincent
Registered: Nov, 2002

Version Numbering - Best Practice? Posted: Dec 3, 2003 6:02 AM
Reply to this message Reply
Advertisement
When I release application versions (primarily front end stuff) I apply the following version numbering rules:

Major: Increment if a massive change has happened to the UI. e.g Numerous UI changes that imply a significant change in the way application is (or can be) used. Reset minor and build numbers to zero.

Minor: Increment if UI has changed (unless the UI changes are very trivial fixes) but application usage and capabilities are basically unchanged.

Build: Increment with each release.

This seems reasonable to be but there's a bit of a debate here on whether the Major number should be incremented if the Minor number becomes "too big". Also, should a Minor version release reset the Build number (or, conversely, should the Build number ever be reset).

Opinions welcome - particularly with regard to the build number.

Vince.


al

Posts: 11
Nickname: allelopath
Registered: Jun, 2003

Re: Version Numbering - Best Practice? Posted: Dec 4, 2003 11:58 PM
Reply to this message Reply
I've never seen any standards with version numbering, but would be interested to know if there were.

My practice is similar to yours. If you are worried about minor numbers getting too big, e.g. you don't want version 1.234, you could go to three decimal points, so to speak, e.g.
version 1.2.34

Joe Parks

Posts: 107
Nickname: joeparks
Registered: Aug, 2003

Re: Version Numbering - Best Practice? Posted: Dec 5, 2003 6:08 AM
Reply to this message Reply
The versioning scheme for Java, for example, says that all minor versions within a major version are bytecode-compatible. That is, something compiled with 1.0 will (or, is supposed to) run in 1.5.

fatih karakurt

Posts: 3
Nickname: karakfa
Registered: Oct, 2003

Re: Version Numbering - Best Practice? Posted: Dec 5, 2003 1:50 PM
Reply to this message Reply
Another practice is: major.minor and add another digit for maintenance releases (no new functionality). Eg.

version 1.0
version 1.1
version 1.11 (maintenance on 1.1)

Flat View: This topic has 3 replies on 1 page
Topic: Connect 4 game Previous Topic   Next Topic Topic: Java on Cell Phones

Sponsored Links



Google
  Web Artima.com   

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