[Openroad-users] OR versioning

[Adrian Williamson]

Hi Garret,

The 'versioning' capability that lies within OpenROAD has always been
considered a little flaky.

The 'Save Private' functionality doesn't help much either, it's too easy to
forget you are working on something that is saved private, and check it back
in (as part of the save frequently mentallity). Don't even get me started on
the mess the client cache can get in when dealing with this. You quite often
have to shut OpenROAD down, just to be able to view the component it its
up-to-date state after a another developer does check it in.

Doesn't matter if you are doing application or component versioning, both
ended up in a mess. The fact that they were missing the ability to record
reasons for change etc made it more unattractive.

Also as everything is stored in one set of application catalogues,
performance will eventually become an issue. SO you have to be canny with
the sysmods.

The OpenRoad 4.0 catalogue style didn't help much either, the versions were
just mixed up in amongst everything else.

It was a bit easier with Version 3 and below as it opened the versions in a
separate window.

As for our latest 'GUI', it hadn't even occurred to me to try it.

I routinely support applications with 15,000+ components in them, and we
tend to use complete database copies to implement Application level
versions.

If you are using Ingres as your source repository (you really should it's
much easier) then creating database copies is very easy.

It's also easy to dump the catalogues as well, so they could even go into a
source code control system of some description.

I'll be happy to go into this in more detail if you want, just drop me a
note.

Regards,

Adrian


-----Original Message-----
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Garret Taylor
Sent: 08 February 2007 16:40
To: openroad-users at peerlessit.com
Subject: [Openroad-users] OR versioning

Hi
Is anyone out there using the OpenROAD versioning successfully on an ongoing
basis for a large code base ?
Can you let me know how and to what end you use it and have you any
practices/procedure around using it ?
And - what are the gotchas ?
Thanks
Garret


_______________________________________________
Openroad-users mailing list  Openroad-users at peerlessit.com

To unsubscribe please click on this link
mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe

To subscribe please click on this link
mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe