   version control
  i''m planning to implement a version-ing system for my framework and it''s plugins. so i''m just wondering, what kind of it is mot used and which is "the best". i was thinking somethin like:MAJOR.MINOR.BUILD like 1.2.23 etc...pros&cons? 
  Who gives a shit about how you format your version numbers??? Just pick a style and get on with your life.  I guess next you will be asking which is faster :if(){ofif(){ ;quote:Original post by Anonymous Poster  Who gives a shit about how you format your version numbers??? Just pick a style and get on with your life.  I guess next you will be asking which is faster :if(){ofif(){   no, i know that second one is faster... ;quote:Original post by Anonymous Poster  Who gives a shit about how you format your version numbers??? Just pick a style and get on with your life.  I guess next you will be asking which is faster :if(){ofif(){   Can''t wait until the new forusm when you can flag topic for review and get people like you IP banned. ;  this how I do it0.5.3 - 0 means not finished, 5 sounds good, 3 third small changereally it doesn''t mean anything, except the next one will be higher then the current one   ;  my version number is like this X.Y.Z well they are just numbers.. I have a small program I created that works something like thisVersionUpdate Main.h MYVERSIONit search the Main.h file for a #DEFINE MYVERSION x.y.z and then it increases the version number to x.y.z+1 as long as z is below 100 if z == 100 then it will put z to 0 and y will be y+1, and the same for x and y.I have put it in my Post-build section ( using VC++ 6 ) so it updates my version every build. well not exactly if the date of the Main.h file is the same as the date of the day that the VersionUpdate file runs, then it won''t update the version, so in other words I can build it 1000 times on one day but the version number only updates once that day.planning to change that some day.. maybe I change it so Z will be number of builds the last day and Y will be number of days I have been working on the project, and X will be something else.. maybe 0 = not finished and X>0 finished and what major version it is. ;  major.minor.branch.buildnomajor  : radical changesminor  : major enhancements and feature, but not a core rewritebranch  : (if any) or milestone in which this version is being developpedbuildno  : increment by one on each successful build (+successful ''smoke'' tests). Could use the day-of-the-year number if built once a day. ;  As stated above, version numbers are useless unless you want to track in which version bugs/enhancements/features/changes were introduced. You would typically use this version number to ''timestamp'' your sources and other game assets in VSS, CVS, PerForce or other similar changement management system. ;  well, my basic need for version control is to have "control" over my framework modules, ie: an app would require above 1.2 video module version to run properly. ;  I tend to use a 6 digit code for each release, defined by the date I make the release. Todays release would be 031219 (YYMMDD).If I can define some mayor milestones for the program those are included via a Letter postfix. Reason? Well, increasing Version numbers suggest that higher versions include all features of and are generally better than prior versions. Sometimes I have to disable certain unneccesary older features in order to test newer features. Is that a higher Version? I don''t think so.   ---------------------------I may be getting older, but I refuse to grow up 