From my understanding of Subversion i would say we do both. We start a "release branch" for incorporating fixes based on the code of a specific release and we "tag" every build number. In Subversion the tags and branches are basically just copies of a specific revision [1]. Usually a repository layout like the one of ccnet is recommended (/trunk, /branches, /tags) but you're not bound to that. You do both tags and branches using the copy command on the commandline.
regards, Daniel [1] http://svnbook.red-bean.com/en/1.5/svn.branchmerge.html On Tue, 27 Jan 2009 20:10:48 +0100 Ruben Willems <[email protected]> wrote: > Hi > > I do not use svn, so the meaning of 'tag' is not known to me for know. > but I think it is comparable with a label in other source controls. > > And yes, I only create a branch with when i release a certain build, > all the other builds can be retrieved via that label, but do not > require a separate branch. > > > with kind regards > Ruben Willems > > > On Tue, Jan 27, 2009 at 8:05 PM, Scott Vickery > <[email protected]>wrote: > > > Right, so here is where I am at: > > > > - I am generating a build number using a hard coded major and minor > > version. The 3 number is the date, the last number is the > > subversion revision number, that is <major>.<minor>.<date>.<svn > > revision> > > > > - The build is being labelled with this number > > > > - I am passing that to msbuild and generating AssemblyInfo.cs with > > the same version which the dll's are picking up. > > > > Are you then creating SVN tags with the build number so that it is > > easy to find a build and create a branch when the time comes? > > > > Thanks for the tip on the modification publisher. I will look at > > that. > > > > Scott > > > > > > On Tue, Jan 27, 2009 at 1:58 PM, Ruben Willems > > <[email protected]>wrote: > > > >> Hi > >> > >> i find it easier to pull code via a version number, than via a > >> revision number. > >> If you also use the modifican publisher, you can easily see what > >> functionality was added when, > >> and you have the version number of that build by hand. And if you > >> also update the version number > >> of your dll's with the same number, it's also easy to link with > >> programs that are deployed. > >> > >> when using the revision number it's harder to achieve the same > >> functionality > >> > >> > >> my 2 cents > >> > >> with kind regards > >> Ruben Willems > >> > >> > >> > >> On Tue, Jan 27, 2009 at 4:41 PM, Scott Vickery > >> <[email protected]>wrote: > >> > >>> Non technical question here. And probably not really a CC.Net > >>> issue. But, one that I think is of interest to this group. > >>> > >>> What is a reasonable tagging methodology for subversion? It > >>> looks like the CC.Net code is tagged for every build. I have > >>> done it this way in the past with CVS, but, is this a good > >>> strategy with subversion as well? It seems to me that you can > >>> create a tag and/or branch at any time given a subversion > >>> revision number. If so, what is the point of the tags? Why not > >>> just create a branch after a version is released when and if a > >>> fix is needed for that release? > >>> > >>> Thanks, > >>> Scott > >>> > >>> > >> > >
