Source Control Strategy

[jnapier]

Hi, I am wondering what the best strategy is for placing packages under source control.  Should you source control the lowest nested package or source control root namespace packages?

I am using SQL Server for my repository and it is extremely slow when working with source control, so source controlling the root namespace packages takes forever to check-in and check-out.  I tried checking in nested packages but if I share the packages with another project, the full namespace hierarchy does not show up in the project that is using the shared resource.

I am just hoping to get some feedback on how other users are using this feature.  

[«Midnight»]

I cannot say for sure which direction (top-down or bottom-up) will work best for you. There has been some lively discussion in the Sparx forum (probably several sections, but mostly this one). You'll have to try several searches to find them all. I think it would be worth your time, since several posters have described their experiences.

Now, about performance and SQL Server. I know there were some issues with SQL Server performance a while back, and I'm pretty sure they were evident when using source control. Some of these addressed in EA builds released since the beginning of 2006. Do you have a recent build? And, if you are not using 789 (which is current now) have you checked the release notes since your build? [You can do so in the Latest News forum section.]

If you are up to the current build, please let us know if you get better performance with another back end (even Access if you don't have anything else handy). If SQL Server is noticably slow compared to something else, it is probably worth issuing a bug report. Use the on-line bug report or connect from EA via Help / On-line Resources / Bug Report Page. If you can somehow limit the problem or determine if it is worse under some circumstances it would probably help Sparx.

David

[jnapier]

I have tried searching for threads regarding this matter and have had no luck finding anything of great value. I have serached for Version Contol, Source Control, and Share Packages over the last 700 days.  I guess my keywords are wrong, could you help point me in the right direction?

For the SQL performance, I have the most recent build.  I will issue a bug report.

[«Midnight»]

A bit of a long shot; try CVS. Often it gets mentioned somewhere in a thread even if it is not what the original writer uses for SC.

Let me know.

[jnapier]

Not much luck finding any "lively discussions" regarding this topic. It would be nice to hear what others are doing.  I'm finding it very cumbersome to implement a bottom-up solution, but top-down packages are way to large.  I was hoping this would be a little easier.

[wsargent]

I'd like to know how best to use source control in EA as well.  Right now I'm assuming that I only want to capture information that I can't reverse engineer.  But I don't know what drawbacks may be involved.

If I'm saving an XMI file into Subversion, and it saves only UML 1.3 reliably roundtrip, does this mean that I can't use UML 2.0 and source control in the same project?