.

seminar on

Software Versioning

Presented by:
Arjun Thakur
[09203003]
 Software Versioning
 Introduction
 Practices
 Change Significance
 Designating Development Stages
 Separating Sequences
 Use of Characters
 Negative Numbers & Dates
 Internal Version Numbers
 Excel in Market
 Case Study
 Introduction
 Software versioning is the process of assigning
either unique version names or unique version
numbers to unique states of computer
software.
 These numbers are generally assigned in
increasing order .
 Practices
 There are various practices for software
versioning.
 Different corporations use different practices.
 Practices

Most Significant 1.2.1.2

Second Sequence

First Sequence
 Change Significance

 Software versions are used to convey degree of

change between two consecutive releases.

 First sequence is changed for the most

significant change.

 Second sequence is changed for relatively less

significant change.
 Change Significance

1.x.1
2.x.1
2.x.2
 Major change(code is completely rewritten)

 Minor change(change in GUI, documentation)

 Designating Development State
 The third sequence represents the development
stage.
 Alpha software
 Beta software
 Release candidate
 Commercially distributable
 Designating Development State

1.2.0.1 Alpha


1.2.1.2 Beta


1.2. 2.3 RC


1.2.3.0 CD
 Separating Sequences
 There are various formats in practice.

1.3 (the most widely used)

1-3
1/3
 Use of Characters & Words
 
Instead of numbers characters can also be used
e.g.
1.2.0 1.2.a
1.2.2 1.2.rc

e.g. Lotus 1-2-3 release 1a

 Negative Numbers & Dates

 Small Eiffel Compiler

-1.0 0.0

 Linux –Ubuntu 10.04 (yy-mm)

 NT 5.0 known as Windows-2000

 Microsoft Word Starter 2010

 Internal Version Numbers
 Different from product number.

 Used by developers and testers.

e.g. j2se 1.5.0

 Windows 2003 NT 5.2
 Windows Vista NT 6.0
 Windows 7 NT 6.1
 Excelling in Market

 To excel in the market major jumps are made

by vendors.

 There may not be significant changes.

 Microsoft Excess jumped from 2.0 to 7.0 to

match version number of Microsoft Word.
 Case Study[Java Compilers]
 JDK 1.0 (January 1996)
 JDK 1.1
 J2SE 1.2
 J2SE 1.3
 J2SE 1.4
 J2SE 5.0
 JAVA SE 6.0
 JAVA SE 7.0
 Case Study[Java Compilers]
 JDK 1.1
 J2SE 1.2

 J2SE replaced JDK to distinguish the base

platform from J2EE and J2ME
 Java plug-in
 Collection framework
 Sun's JVM was equipped with a JIT compiler
for the first time
 Case Study[Java Compilers]
 JDK 1.0
 JDK 1.1
 J2SE 1.2
 J2SE 1.3
 J2SE 1.4

1. Dramatic changes made in java class library.

2. Number of classes increased from a few hundred

to three thousand.
 Case Study[Java Compilers]
 J2SE 1.4
 J2SE 5.0

1. Major changes are undergone.

2. Entire new APIs introduced e.g. java swing,
java2D.
 Case Study[Java Compilers]
 J2SE 5.0
 JAVA SE 6.0

1. J2SE 5.0 entered the end of it’s life and no

longer supported by Sun as on November
3,2009.
2. JDBC4.0 support.
3. Sun replaced the name from J2SE with Java SE
and dropped .0 from the version name.
4. Internal version number being 1.6.0.
 Case Study[Java Compilers]
 JAVA SE 6.0
 JAVA SE 7.0

1. Concurrency utilities under JSR.

2. Compressed 64 bit pointers.
3. New APIs for graphics.
4. Updates for XML support.
5. Scheduled to be released in late 2010.
.

Thank You
 References
 http://www.ntg.nl/maps/05/34.pdf
 http://www.winamp.com/help/FAQ#10
 http://www.debian.org/doc/debian-
policy/ch-controlfields.html#s-f-Version
 http://java.sun.com/javase/downloads/ea/6u
10/deploymentToolkit.jsp
 http://java.sun.com/javase/6/webnotes/6u16.
html