[Rubyinstaller-devel] RFC: Version Control for new Installer?

Will Green will at hotgazpacho.org
Wed Apr 23 08:01:59 EDT 2008

SVN has the lowest barrier to entry for Win32 developers (Collabnet's 
SVN installer for Windows, TortoiseSVN).

To the best of knowledge, all the other tools (bzr, git, etc) do not 
have a stable, native win32 client. That is, they all require an 
existing Cygwin or MinGW install.

The other benefit of SVN is that if folks want to use git, git-svn can 
push their changes back to the SVN repo.

Given that this is a Win32 project for Win32 developers, my vote is for SVN.

Will Green

Luis Lavena wrote:
> Hello fellow developers,
> It seems I neglected to push or decide what to do regarding the code
> being developed for what I call it 'installer3' MinGW build.
> So far, the idea was push these changes back into svn, which will
> lower the entry point for others developers wanting to contribute back
> to it.
> Since 'git' is the new cool toy, I wondered a lot of Installer3 should
> also move to it, even when Git support is not 100% what I will love to
> have.
> Or, instead, I was thinking also move the repo from my host to
> launchpad, which will raise some critics about using closed-source
> software to host an open source project (github is closed source
> anyway)...
> What do you guys think will be best? I'm open to suggestions.
> What I love of the dvcs workflow is that I can keep local branches to
> foster experimentation and try new things before I merge them back
> cherry pick stuff from them.
> Thank you for your time guys, feel free to comment.

More information about the Rubyinstaller-devel mailing list