Best practice today is to immediately begin migrating to a more recent generation of source control. Subversion is just an artifact of an intermediate learning stage.
My office uses Subversion. As far as my limited knowledge goes, SVN is better for more centralized commercial products. Also, I don't know if the issue-tracker JIRA has support for git.
It depends. I've never used git, but hg is a dream compared to SVN. Yeah, some of it is the plug-ins for eclipse and such just being so better, but trying to resolve conflicts is so much less awful. Committing locally-only when you hit a 'save point' is also a nice advantage, especially when you can keep adding changes to one commit as a logical unit if that's what you want since no one is commiting locally-to-you, then you only have to merge when you're done.
I prefer mercurial, personally. The thing about SVN that really gets me for mercurial is the local only "save points". I don't want to publish even to the other developers little pieces of half-working features as I muddle through repairs. It lets me be even more reckless about wiping out bad code.
9 comments
6 u/skeeto 15 Jun 2015 00:11
Best practice today is to immediately begin migrating to a more recent generation of source control. Subversion is just an artifact of an intermediate learning stage.
2 u/wigawam 15 Jun 2015 02:27
I agree. I loved SVN up until the point I started using git. No reason to look back.
1 u/watersnake 15 Jun 2015 02:30
My office uses Subversion. As far as my limited knowledge goes, SVN is better for more centralized commercial products. Also, I don't know if the issue-tracker JIRA has support for git.
0 u/sdkfj239euqo 15 Jun 2015 03:25
Jira has support for git.
https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin
0 u/Camarilla 17 Jun 2015 16:15
It depends. I've never used git, but
hgis a dream compared to SVN. Yeah, some of it is the plug-ins for eclipse and such just being so better, but trying to resolve conflicts is so much less awful. Committing locally-only when you hit a 'save point' is also a nice advantage, especially when you can keep adding changes to one commit as a logical unit if that's what you want since no one is commiting locally-to-you, then you only have to merge when you're done.0 u/Camarilla 17 Jun 2015 16:11
I prefer mercurial, personally. The thing about SVN that really gets me for mercurial is the local only "save points". I don't want to publish even to the other developers little pieces of half-working features as I muddle through repairs. It lets me be even more reckless about wiping out bad code.
0 u/VoatSimulator 14 Jun 2015 23:51
Was surprised to see that the number one tip wasn't to use git instead </flame>
What VCS(s) does everyone use for day-to-day purposes? I was under the impression that most people were using Git these days.
1 u/votes [OP] 14 Jun 2015 23:52
SourceSafe always served me well. I was sad when I had to transition to SVN.
0 u/asdghjklfghasldk 18 Jun 2015 04:20
you don't deserve the upvote but using VSS in 2015 made me laugh