ClearCase-like reserved checkout capability

In ClearCase, the reserved checkout alerts users on a shared stream that a file is being modified by another user, and appropriate triggers can prevent multiple checkouts if necessary.

This is especially useful for versioned binary files that cannot be merged.

Is there any mechanism in RTC to help users avoid simultaneous modification of binary files in their local workspaces?

Hi

in RTC 2.0 - a file that is locked on your stream is marked as locked in the relevant views (such as the Package View). It also tells you who has locked the file.

It looks like the process permissions will let you control how people can manage that lock - but I have not tried this yet.

anthony

With Jazz SCM, you can create a "lock" on a file in a stream, and the
GUI does show you via an icon that there is a lock on the file, but you
are not prevented from modifying or checking in a new version of the
file ... you are only prevented from delivering a new version of the
file to the stream.

There is a work item (77416) requesting that multiple checkouts be
prevented on a locked file. There is another work item (82195)
requesting that these locks be automatically created on a selected set
of file types, when that file is modified.

Please feel free to add your comments/support to those work items.

Cheers,
Geoff

jim.islandtraining.com wrote:

In ClearCase, the reserved checkout alerts users on a shared stream
that a file is being modified by another user, and appropriate
triggers can prevent multiple checkouts if necessary.

This is especially useful for versioned binary files that cannot be
merged.

Is there any mechanism in RTC to help users avoid simultaneous
modification of binary files in their local workspaces?

Hi Geoff,

Is there any progress with defining\implementing this requirement?
Is there a best practice\workaround for developers to avoid multiple editing on a same element?

Best Regards,
Amit.

With Jazz SCM, you can create a "lock" on a file in a stream, and the
GUI does show you via an icon that there is a lock on the file, but you
are not prevented from modifying or checking in a new version of the
file ... you are only prevented from delivering a new version of the
file to the stream.

There is a work item (77416) requesting that multiple checkouts be
prevented on a locked file. There is another work item (82195)
requesting that these locks be automatically created on a selected set
of file types, when that file is modified.

Please feel free to add your comments/support to those work items.

Cheers,
Geoff

The work item was not part of the 4.0 plan ... add your comments to the
work item to help get it prioritized for 5.0 (attending the VoiCE
sessions at Innovate in June is a very good way of getting the priority
bumped for your favorite enhancements).

Until then, you would need to use the "lock" mechanism, described below.

Cheers,
Geoff

On 3/15/2012 12:12 PM, amitkar wrote:

Hi Geoff,

Is there any progress with defining\implementing this requirement?
Is there a best practice\workaround for developers to avoid multiple
editing on a same element?

Best Regards,
Amit.

gmclemmwrote:
With Jazz SCM, you can create a "lock" on a file in a
stream, and the
GUI does show you via an icon that there is a lock on the file, but
you
are not prevented from modifying or checking in a new version of the

file ... you are only prevented from delivering a new version of the

file to the stream.

There is a work item (77416) requesting that multiple checkouts be
prevented on a locked file. There is another work item (82195)
requesting that these locks be automatically created on a selected
set
of file types, when that file is modified.

Please feel free to add your comments/support to those work items.

Cheers,
Geoff