[Subversion] Rational Rhapsody files, lock unlock philosophy

[Keller Eric <Ek...@hamilton-medical.ch>]

Hi everybody,

We are finally switching from PVCS to subversion, and I would like to get more input from you other user concerning the lock/modify/unlock philosophy!

Subversion as PVCS allow the use of locks. The description in your reference book: http://svnbook.red-bean.com/en/1.0/ch02s02.html also presents the Copy modify merge solution, which is more commonly used. Yet our manager people are not convienced that this method is better than a lock unlock modify solution.

For giving you a short overview the project files revision in subversion are Rhapsody models, these files data structure is ASN.1(Abstract Syntax Notation One) It is not binary.

Are there other user using subversion associated with Rhapsody files who are using the copy-modify-merge solution?

Thank you in advance for your answers, I am looking forward for a constructive communication!

Best Regards
--
Eric Keller



Eric Keller
_________________________________________
Software Engineer

HAMILTON Medical AG
Via Crusch 8
7402 Bonaduz
Switzerland

Phone:+41 81 660 65 16
Fax:+41 81 660 60 20

eMail:Ekeller@hamilton-medical.ch
Web:www.hamilton-medical.ch

RE: [Subversion] Rational Rhapsody files, lock unlock philosophy

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: Keller Eric [mailto:Ekeller@hamilton-medical.ch]
> Sent: woensdag 10 augustus 2011 17:22
> To: users@subversion.apache.org
> Cc: Hug Martin
> Subject: [Subversion] Rational Rhapsody files, lock unlock philosophy
> 
> Hi everybody,
> 
> We are finally switching from PVCS to subversion, and I would like to get
> more input from you other user concerning the lock/modify/unlock
> philosophy!
> 
> Subversion as PVCS allow the use of locks. The description in your
reference
> book: http://svnbook.red-bean.com/en/1.0/ch02s02.html also presents the

I see a /1.0/ there.

> Copy modify merge solution, which is more commonly used. Yet our
> manager people are not convienced that this method is better than a lock
> unlock modify solution.

Please (also) check the more recent versions of the book on the same site.
The version you are looking at was written for Subversion 1.0 and a lot has
changed since then.

 (I think svn lock wasn't introduced until 1.1 or 1.2)

	Bert