Which Version Control System are you using?

[Cjkjvfnby]

Which Version Control System are you using?
[list type=decimal]
[*]SVN
[*]Git
[*]Mercurial
[*]other
[*]I know about Version Control System but don`t use any
[*]I don`t know about Version Control System
[/list]
And why?

Version control system is tool what all moders MUST HAVE. especially if working in teams.

If you work in team: where you store project?
[list type=decimal]
[*]Enternet service for version control systems (SourceForge, github, ...)
[*]Personal server
[*]File share service (Dropbox, ...)
[*]Sending source to each other by email. (Dropbox, ...)
[*]Other
[/list]

I use git for my projects. (Because I use it at my employment. It is better for storing code when SVN)
To share code between my computers, I use www.github.com to public scripts and Dropbox for personal. (git hub doesn't have free private repositories.)
Storing repo on dropbox folder is more preferable for modding because where is many not text files in mod.

 

[xenoargh]

5; as a one-man show I just keep backups of everything in multiple places, including online. 

If I was working with a team, I'd likely continue that, as past experience with repos indicates that non-coders using repos frequently find it complicated to manage and waste more time than it's worth. 

It's easier to just explain things like naming conventions to artists and then expect complete uploads that meet the business case.

If it was a really large project with very competent technical artists, well, that's something else, but at that point, you're not making a mod, you're making a AAA demo.

 

[Vincenzo]

Subversion for all code.
Dropbox for all resources.

Works perfect for my team.

 

[Cjkjvfnby]

5; as a one-man show I just keep backups of everything in multiple places, including online. 

If I was working with a team, I'd likely continue that, as past experience with repos indicates that non-coders using repos frequently find it complicated to manage and waste more time than it's worth.

It's easier to just explain things like naming conventions to artists and then expect complete uploads that meet the business case.

If it was a really large project with very competent technical artists, well, that's something else, but at that point, you're not making a mod, you're making a AAA demo.

I allways forget about artists . It is good idea to split code repo and artists repo.  VCS it good for text files. 

 

[Kazzan]

I've only used dropbox for a short time when working with another guy when I wasn't the coder-guy of the mod.
I also use pastebin for code and idea handling.

 

[MadocComadrin]

SVN or manual back-ups--depends on the project.

 

[Caba`drin]

The Floris team uses Dropbox for everything (code, resources, etc), though the only thing that currently is really collaboratively edited is the code.

Dropbox ensures we all have the same copy of the files, and since we all edit with Notepad++, any changes get automatically notified and updated while we are working. It holds backups/conflicted files etc and seems to do a decent job with that.

True, it doesn't keep any line-by-line histories for us, but its hands-off ease-of-use makes it more than enough.

 

[Azrooh]

Subversion.

 

[Vornne]

I use git, which dramatically changes the way code development can happen: I'd be rather lost without it. Just myself at this stage, with backups on private ISP webspace; but eventually the full module system will be released to the public via some sort of git hosting - not sure what would be both free of cost and compatible with whatever the distribution terms of the module system are (haven't asked yet).

 

[Swyter]

For Star Wars Conquest we use private SVN repositories hosted in Assembla, without branching. A single rolling release.
Works great, and with the help of the new revisions of the Subversion protocol now is much faster. Although I keep an eye in Git.

 

[cmpxchg8b]

SVN for cRPG.
Mercurial for WSE and "WSE2" (similar concept to Git, but I find HG to be cleaner/more elegant. Also it has a very good UI for Windows, while the Git ones are sub-par).

 

[Llew2]

The TLD team uses SVN.

 

[Ikaguia]

Dropbox

 

[Mammoet]

Mercurial/Hg + Tortoise

 

[Specialist]

Dropbox. Though for some of the simpler stuff (my dropbox is full) I just use mediafire and send the link through steam. Lol

 

[Computica]

Version control system is tool what all modders MUST HAVE. especially if working in teams.

I don't use an SVN since I'm the only person doing code work, anytime I add a new feature I back up the files externally.

 

[Mammoet]

Version control system is tool what all modders MUST HAVE. especially if working in teams.

I don't use an SVN since I'm the only person doing code work, anytime I add a new feature I back up the files externally.

It's a bit harder if you want to check the difference and/or recover only parts of it though. Plus you'd have to name everything accordingly etc. In my opinion its much easier to use a version control system, even if you work alone. But well... whatever works for you

 

[sairtar]

Our team once used SVN, but it was complicated and time consuming as mentioned earlier.  Now version control is done by having the team lead organize who uses the code at one time, aggregates resources, and redistributes using mediafire pro.  I had heard reports of Dropbox corrupting data, so switched tot he paid for media fire, which has a great dropbox and direct linking capability.

Cheers.

 

[Cjkjvfnby]

I had heard reports of Dropbox corrupting data, so switched tot he paid for media fire, which has a great dropbox and direct linking capability.

Dropbox not corrupting files. But if two person write same group of files in one time they can be merged in random.

 

[Caba`drin]

I had heard reports of Dropbox corrupting data, so switched tot he paid for media fire, which has a great dropbox and direct linking capability.

Dropbox not corrupting files. But if two person write same group of files in one time they can be merged in random.

and it will put a "conflict file" with the name of the alternative file in your folder to notify of this.