It would be my suggestion that we tag the individual releases, apart from the whole tree. The global revision number already gives us a global tag. What might be helpful is a tag that applies to the files affected by an individual release. One reason for this is that we vote on a release, and the tag can be used to clearly define the release. We can, of course, track releases through the global revision number, but a tag does that for us, and automatically defines which files we are including in the release.
I haven't done a lot of tagging myself, but people who roll multiple releases within one Subversion repository seem to prefer a structure like: /mapper /trunk /tags <-- tags for the mapper releases /dao /trunk /tags <-- tags for the dao releases /docs /trunk /tags <-- tags for the doc releases Subversion is flexible, and there would be other ways to do this, but the usual set of trunks and tags may speak to the principle of "least surprise". We are one project, but we are distributing multiple products with their own release cycle. The SVN structure reflects the release structure, and, to be useful, tags, and the place where we keep the tags, should follow suit. Of course, checking out something like this, especially when you only want the current stuff, and not all the branches, can be horrendous. Happily, there is a solution: --- Original Message --- From: "Martin Cooper" <[EMAIL PROTECTED]> To: Struts Developers List <dev@struts.apache.org> Cc: Sent: Sat, 15 Jan 2005 20:54:48 -0800 Subject: New 'current' pseudo-subproject > I've set up a 'current' directory for Struts that uses a cool > Subversion feature to make all of the individual subproject 'trunk' > directories available through a single checkout. So now you can do > this: > > svn co https://svn.apache.org/repos/asf/struts/current > > and get this: > > current/ > apps/ > bsf/ > core/ > el/ > faces/ > sandbox/ > taglib/ > tiles/ > > So now, if you're working on Struts as a whole, you can check out, > update and commit for all subprojects at once. > > See the section on Externals Definitions in the Subversion book for > how this works, and a couple of caveats: > > http://svnbook.red-bean.com/en/1.1/ch07s03.html > > Many thanks to Tim O'Brien for the idea. > > -- > Martin Cooper > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED]
