The import of the CVS repository created several tags and a branch with names reasonable for CVS, but somewhat strange otherwise. Rename them to something useful.
I've changed all tags for all parts of the repository. Old, existing tags have only been altered slightly (e.g., something like ropp_io_v_0_1 under cvs was changed to ropp_io-0.1). For the future, I would suggest the following convention for tag names under the tags subdirectories in the Subversion repository:
n.n or n.n.n
for sources, test folder and web site. I have dropped most of the lengthy cvs-style tag names for simplicity, in line with the intended use of the Subversion repository structure. This allows the export of a given version (say 0.7) into a local subdirectory (say ropp) by a command like (for the ropp sources)
This is different for the documents, as I would expect that different documents will be versioned independently from each other. Thus, each document should have it's own tag name like
<doc_abbrev>-n.n
where <doc_abbrev> is one of tld or ug (or whatever else comes up). This would mean, however, that we are tagging the documents individually rather than all at once; which is slightly inconsistent with the way we work with the source code.
I've changed all tags for all parts of the repository. Old, existing tags have only been altered slightly (e.g., something like ropp_io_v_0_1 under cvs was changed to ropp_io-0.1). For the future, I would suggest the following convention for tag names under the tags subdirectories in the Subversion repository:
for sources, test folder and web site. I have dropped most of the lengthy cvs-style tag names for simplicity, in line with the intended use of the Subversion repository structure. This allows the export of a given version (say 0.7) into a local subdirectory (say ropp) by a command like (for the ropp sources)
This is different for the documents, as I would expect that different documents will be versioned independently from each other. Thus, each document should have it's own tag name like
where <doc_abbrev> is one of tld or ug (or whatever else comes up). This would mean, however, that we are tagging the documents individually rather than all at once; which is slightly inconsistent with the way we work with the source code.