Community
Participate
Working Groups
I20050217-0800 I often have a set of projects in my Synchronize view and would like to perform Team actions (e.g. Compare, Release,...) with them.
We hesitate to add the Team menu to the synchronize view since some of the actions would be confusing? For instance, what does Tag as Version tag? The visible resources that are descendants of the selection or all workspace resources. Having Release in the synchronize view doesn't really make sence either given that you should only be releasing projects that are in-sync (also, Release is a global command that can be keybound). If you have specific items you would like to see in the sync view menu then by all means log a bug to request that specific item and include a description of the workflow that includes the command in the context of the sync view.
>Having Release in the synchronize view doesn't really make sence >either given that you should only be releasing projects that are in-sync >(also, Release is a global command that can be keybound). For me it makes perfect sense: I often compare something, e.g. projects, (which is actually in sync with its branch) with some other branch or version and that ends up in the Synchronize view (at least in my Eclipse ;-). I then like to release some of those changes. I often could need this when backporting stuff to the performance branches. The actions I am missing are Compare and Release. I adapted the summary instead of creating yet another feature request.
From your description, I can see the justification for having Release in a Compare Synchronization. I still don't see the case for having a Compare in the sync view. Can you elaborate on how you would use that?
Similar to release: I don't need it when working against HEAD but lately I often had to backport fixes and tests to perf_301 and perf_30. Since the changes look quite the same I often compare what's in the Sync view (outgoing changes) with the other branch where I already applied those similar changes. To do this I had to go to the Package Explorer, find and select the projects with changes (this would be easier if enhancement 63096 would be implemented ;-) and then Team > Compare.
Sounds reasonable. Notg a high priority though.
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.
