Difference between revisions of "Switching from SourceSafe to Subversion"
From MohidWiki
| Line 1: | Line 1: | ||
==FAQ== | ==FAQ== | ||
| − | ''Are we really going to change from source-safe to subversion?'' | + | *''Are we really going to change from source-safe to subversion?'' |
| + | *Yes, after a lot of propositions and debating with the main developers at Maretec and Hidromod, we opted to make the switch from source-safe to subversion. | ||
| − | + | *''Why?'' | |
| + | *Because source-safe has some limitations that prevent a better development and maintenance of the MOHID code. | ||
| − | '' | + | *''What are the implications?'' |
| + | *The users of source-safe will have to install a subversion client in their computers and configure it in order to access the new subversion repository of the MOHID code. So, basically, it's a new interface to get the latest version of the code. | ||
| − | + | *''What are the other implications?'' | |
| − | + | *Developers will have to use the subversion client to perform standard source-safe actions like check-out, check-in, diff, merge, roll-back and branching. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''What are the other implications?'' | ||
| − | |||
| − | Developers will have to use the subversion client to perform standard source-safe actions like check-out, check-in, diff, merge, roll-back and branching. | ||
Revision as of 15:16, 31 March 2009
FAQ
- Are we really going to change from source-safe to subversion?
- Yes, after a lot of propositions and debating with the main developers at Maretec and Hidromod, we opted to make the switch from source-safe to subversion.
- Why?
- Because source-safe has some limitations that prevent a better development and maintenance of the MOHID code.
- What are the implications?
- The users of source-safe will have to install a subversion client in their computers and configure it in order to access the new subversion repository of the MOHID code. So, basically, it's a new interface to get the latest version of the code.
- What are the other implications?
- Developers will have to use the subversion client to perform standard source-safe actions like check-out, check-in, diff, merge, roll-back and branching.
