Re: Need To "Lock" Many Files Within Multiple Folders

Tim Hill suggested using the "Authorization" mechanism rather than the
"Locking" mechanism to accomplish our objective. After consideration, our
team has opted to use his suggestion.

Although the strategy requires logging onto the repository server and
hand-editing the applicable file, it benefits the project by sustaining
read/write access for a targetted group (of Promotion Managers) while
prohibiting "lock stealing" by developers.

Thank you Tim!

_Marvin

On Dec 7, 2006, at 9:27 AM, Marvin Toll wrote:

* Objective Statement * We have folders of (.class / .xml / .txt etc. etc.)
artifacts matured over many days. Once they are certified for promotion to
our Integration environment, we would like to prohibit any further changes
to the artifacts. Thus we can be assured they are viewable, but not
alterable, before future promotions to our Quality Assurance and (later)
Production environments.
Received on Tue Dec 12 21:31:42 2006