Community
Participate
Working Groups
I have unreleased resources in my project. I want to tag what is released in HEAD as a revision. So, I select Team->Tag, and get the following message: "...These changes are not in the repository and will not be included in the version you are creating." I interpret this to mean that the *changes* will not be in the repository, but the released files (without changes) will be in the version. I have no idea what actually got tagged, but I am certain it was not the contents of HEAD stream. We ended up with compiler errors in the build, but HEAD compiles cleanly. If I use the CVS Repositories view to TAG the HEAD stream, I get what I really wanted to happen. I'm suggesting that the prompt be changed to reflect whatever it is that actually happened (and not what isn't going to happen:-)
What got tagged was the base of whatever you had loaded in your workspace (i.e. the lineup in HEAD the last time you checked out or updated your project). It would not include files that have been released by others since your last update and would not include outgoing changes. We could give the option in the prompt to show the sync state between the local and remote so that the user could see what local resources and what remote resources will be excluded from the tag operation. This should be fairly easy once we merge the latest sync work with HEAD.
Is that even useful? Why not just suggest that the user tag what is in the repository stream, since that is more likely to be in a working state some unknown state based on when you last synced up.
There are actually times when you want to tag the lineup in your local workspace. Branching is one such example. I think presenting the user with the comparison between the local and remote states will let them make an informed decision as to how to proceed. We could even give them the option in the wizard of tagging the remote state directly, saving them from cancelling and then going to the repo view.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
