2 of 2 people found this helpful
We have been using Subversion for several years and it works great for us. We use TortoiseSVN to check in the whole design directory. We check in everything at once including the mechanical, software, specifications and electrical files. The revision control features have saved us more times than I can count. We try to keep our specs in text documents intially so its easy to track changes using the diff feature.
Thank you for your reply, that is what I am planning on doing right now since there does not seem to be built-in support for SVN.
We too use SVN Subversion. We use DXDesigner in which we have a central library used by as many as 4 peaple. Do you see any potential problem in this system.
I would like to know if your library system is shared by multiple users or is your library tied to each design?
We put both the project directories and the shared central library under revision control. The users checks out a copy of the central library and any projects they are working on to a local drive. If they make changes to the central library by editing a part on there local drive, they must check the new or modified part back into the central library. The user will comment the reason for the change in the version log at the time of check in. The only flaw with the system is that the user must remember to do the check in. Its easy to see in file manager that a check in is required so its not been a problem for us. Some sort of script that reminds the user to do the check in on a daily basis if required would help with this.
Thanks Ben.. It looks like we will be taking the same approach.
Would anyone using subversion be willing to detail out how they are using it and how their environment is setup?
I have experienced this issue using SVN and DxD.
If you do a check in of a design, complete directory, then check it back out to a working copy - then attempt to do a job management wizard copy - the job mgt wizard cannot create the next version project as it stops when trying to copy the .svn files that are included in each directory when you commit to svn.
Anyone have the same issue?
We can run the archived versions just fine, however for archival purposes and creating next versions - seems to be a block.
We are going to try zipping the entire project, then submitting for corruption archival purposes.
You may be interested in this posting on the DxDesigner Ideas Site