Tags and uncommited resources...

[James Depaul]

Two questions for the group:

1) We have three separate projects that together make up the deployment assets: Commons, Web, and Testing. First question is: can I TAG all three of the projects with the same TAG to mark the same mile-stone in all three of them?! Guessing that it's not a problem but wanted to confirm.

2) Need to TAG the projects while having some uncommited resources locally - is this a problem? I seem to recall from the docs that the TAG command only affects the repository, so any uncommited changes locally should not be included. Not sure if cvs will insist that they be checked in first?! Ideally, whatever is in repository at the time the TAG command is issued for each project should be tagged, and all local changes should be excluded/ignored. Here is the command I plan on using (after navigating to each project dir):

cvs -q tag Release-2007_07_27_001

Any comments would be welcome before we do it.

Thanks,
James