This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
What version naming policy do you follow in your organizations for variou spurposes? Like, we use for word documents the starting version from 0.90, then every update makes it 0.91,0.92 etc. For our softwares/solutions, we use 1.0 and then 1.1, 1.2 etc. for our source codes, we use CVS which itself gives a version. I would particularly like to know the versioning policy for the followings--- (1) Internal (Word) Documents (2) External (Word) Documents (3) Web Site versions (4) Software versions (5) Source code versions Any ready made docs are most welcome.
Ashik Uzzaman Senior Member of Technical Staff, Salesforce.com, San Francisco, CA, USA.
donno if this is any useful, but one of my freind told me that they are sticking to some standard for documentation, with some standardizing authority, and tht same authority have provided them with pre-defined templets and guidelines for every artifact of software documentation, in which they just have to fill relevent field etc. I guess i 'll ask him the name of the standard first before commenting further.......
Gagan (/^_^\) SCJP2 SCWCD IBM486 <br />Die-hard JavaMonk -- little Java a day, keeps you going.<br /><a href="http://www.objectfirst.com/blog" target="_blank" rel="nofollow">My Blog</a>