Great Tom! I understand and thanks for investigating.
I am now sure that this information was never there nor lost when I moved around the releases. How to consider the "releases" in comparison to the "tags" and "branches" depends on what they are used for. The script that creates the new release in the "releases" directory can easily be changed to create it either in the "tags" or in the "branches" directory instead. I just think it is convenient that the "releases" are separate. It makes it easier to monitor the active branches and tags and easier to explain the commit rules and monitor them. On the other hand, the script doesn't have any knowledge about Subversion or what parts of the repository that are the project roots in our Eclipse setup. It works on the whole repository. See http://argoumlinstaller.tigris.org/source/browse/argoumlinstaller/trunk/ build-release.sh?annotate=123#id111. If we were to add a function that appends information to the subversion:tags property, is it enough to do it on /trunk i.e. the root of the branch or tag or does our Eclipse setup require it to be on /trunk/src_new, /trunk/lib, /trunk/src/model, /trunk/src/model-mdr, /trunk/tests, /trunk/tools, /trunk/documentation, /trunk/modules/dev, and /trunk/www. /Linus > -----Original Message----- > From: Tom Morris [mailto:[EMAIL PROTECTED] > Sent: den 14 december 2006 18:35 > To: [email protected] > Subject: RE: [argouml-dev] Where did all the SVN tags go? > > > I don't think Subversion has the concept of tags so I am very > > confused by this. > > That's true at an abstract level since the SVN folks like to claim > "everything is just a file" but both tools and people which use SVN have a > very strong concept of what tags are. > > http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html > > > What is the Subclipse SVN Resource History Tags column > > supposed to contain and how is it generated? > > It looks like it uses information in the subclipse:tags property. > http://subclipse.tigris.org/branch_tag.html > > I'm not sure if this got broken when the Tags directory was removed or if > something else broke it. I'll see if recommitting the property fixes > things. I'm guessing it will. > > Does the concept of "release," which is a little bit of a "tag" and a > little > bit of a "branch," have enough extra value to justify the overhead of > defining and maintaining it or could we make do with the concepts that > everyone already knows? All of the Eclipse Team subsystem functionality > (for both CVS & SVN) is based on branches and tags. > > Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
