i would suggest using version task's revisiontype=increment for the daily build and revisiontype=automatic when you are going to test. Major and minor or done manually to the .version file that is maintained by the version task. I think that would follow your scheme
----Original Message Follows----
From: "Bonnett, Evan A" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: "'Gert Driesen'" <[EMAIL PROTECTED]>
Subject: [Nant-users] More Questions on Versioning...
Date: Thu, 22 Apr 2004 11:00:11 -0400
Ok, last question on versioning... I think.
Gert and others,
You say that when using the asminfo task, you should just use the # of days
since a certain date (I forget which date but I think it's the date VS was
released?)
Currently, I use the major.minor.build.revision model now, and my
application is at 2.1.0.5. The revision is my daily build. The build is my
weekly load build to the testers. The minor is used for releases to the
public that are not the majors, and the final #, well you can figure that
one out.
So, when generating a new asminfo during the daily, weekly, or release
build, would I check out the AssemblyInfo.cs file from VSS, generate a new
one, and check it back in?
Which # (major, minor, build or revision) is incremented with the # of days
since that certain date? the revision?
Thanks all,
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
