Sign In

Communications of the ACM

Kode Vicious

Version Aversion

numbers in movable type

Credit: Alicia Kubista

The way you number your releases communicates more than you might think.

The full text of this article is premium content


David Allen

Whatever version scheme you have, I recommend it be written down and published for your team and customers. In some of our projects, we followed the naming and it worked fine. In others, we used a pattern. Or was that Oh well. That is why we document it - my memory is so bad and the possible schemes are endless.

Displaying 1 comment

Log in to Read the Full Article

Sign In

Sign in using your ACM Web Account username and password to access premium content if you are an ACM member, Communications subscriber or Digital Library subscriber.

Need Access?

Please select one of the options below for access to premium content and features.

Create a Web Account

If you are already an ACM member, Communications subscriber, or Digital Library subscriber, please set up a web account to access premium content on this site.

Join the ACM

Become a member to take full advantage of ACM's outstanding computing information resources, networking opportunities, and other benefits.

Subscribe to Communications of the ACM Magazine

Get full access to 50+ years of CACM content and receive the print version of the magazine monthly.

Purchase the Article

Non-members can purchase this article or a copy of the magazine in which it appears.