What does the date look like in the Revision? YYMMDD wouldn't fit. I think this is a example of a date like value (minus the year and some weird start digit) in the Build portion http://weblogs.asp.net/bradleyb/archive/2005/12/02/432150.aspx
On Fri, Feb 5, 2010 at 4:22 PM, Michael Minutillo <michael.minuti...@gmail.com> wrote: > If D is the Revision (or Changeset for TFS) number then you can normally > grab the date from that. > > On Fri, Feb 5, 2010 at 1:17 PM, Bec Carter <bec.usern...@gmail.com> wrote: >> >> I've seen attempts at jamming dates in the C part (Build) before, is >> there any benefit or standard for this? >> >> On Fri, Feb 5, 2010 at 3:21 PM, David Richards >> <ausdot...@davidsuniverse.com> wrote: >> > I think it doesn't really matter as long as you are consistent. We >> > have two conventions. Mainly because our marketing people forced us >> > to have the second one. >> > >> > We have the four A.B.C.D so firstly (for customer products): >> > >> > A - Feature/interface change, not necessarily backwards compatible. >> > B - Feature/interface change but IS backward compatible >> > C - No feature or interface change. eg bug fix. >> > D - Controlled by build server. >> > >> > Second (for our core libraries): >> > A - Family version used in marketing >> > B - Same as A above >> > C - Same as B above >> > D - Same as D above >> > >> > >> > David >> > >> > "If we can hit that bullseye, the rest of the dominoes >> > will fall like a house of cards... checkmate!" >> > -Zapp Brannigan, Futurama >> > >> > >> > >> > >> > On Fri, Feb 5, 2010 at 13:33, Bec Carter <bec.usern...@gmail.com> wrote: >> >> TGIF! >> >> >> >> What assembly versioning convention do people here follow? I assume >> >> theres a Microsoft standard that I havent found yet. >> >> >> >> Cheers >> >> Bec >> >> >> > > > > > -- > Michael M. Minutillo > Indiscriminate Information Sponge > Blog: http://wolfbyte-net.blogspot.com >
