Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

software release methodology

Stephen Adler wrote:
> Guys,
> For those of you who are actively involved in software projects, I was 
> wondering how you go about giving your software project a version 
> number. Specifically, how do you tag the version string in your code so 
> that when you do something like
>   myexecutable --version

In my java/ant/cvs environment, we use a hacky but effective solution. 
During the build, an ant target reads the version tag out of a nearby 
CVS/Tag file and generates a Java properties file encapsulating the 
version name.


> then prints out the version number of the software. Are there methods 
> within code repository tools like subversion or cvs which will fill in a 
> string or something with a version number or tag string so that when you 
> do a checkout, it automatically replaces the string? Or do you have to 
> manually change a string constant within your code and then commit the 
> change to the released version of the code?
> Cheers. Steve.

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /