Re: [mantisbt-dev] Moving from SVN to Git

[Victor B. <vb...@gm...>]

Hi all,

I would like to thank everyone who has contributed to this discussion,
it has been very useful to us and has helped us to drill further to
make the decision.  It also helped us understand the concerns of the
community and make sure we address them in our new platform.  Based on
that, following is the summary of our decision:

1. Based on this discussion we have re-considered git, hg and bazaar.
hg / git were the stronger candidates.  However, we decided on git for
the following reasons:
a. We have already built integration plugin between Mantis and git.
b. The current devs have already been experimenting with git for a while.
c. Native git works fine on Windows (msysgit) and fixes have been
merged back in main code base.

2. For users, we will provide a way for them to download nightly
builds without having to use any source control tool.

3. For contributors not familiar with git, they can provide diffs
against nightly builds.

4. For translators, they will use a translation infrastructure.
Siebrand is currently co-ordinating this via some translation wiki
infrastructure which seems to be effective in keeping our translation
updated and adding new languages.

5. There will be follow up email threads relating to our revised work
flows based on the fact that we will be using a DVCS which allows us
to enhance our process.

6. As of now, there is a commit freeze to SVN since we are in the
process of migration to git.

On Thu, Oct 30, 2008 at 11:55 AM, Victor Boctor <vb...@gm...> wrote:
> Just adding some more notes:
>
> 1. It seems that as a development team, we would want to move to *any*
> DVCS.  Is there a value in keeping the Sourceforge SVN repository up
> to date?  i.e. on commit push the data to Sourceforge?  Would patches
> submitted by contributors based on SVN or our new DVCS both work when
> applying the changes to DVCS? (assuming no code conflicts of course).
>
> This model may apply contributors to continue to use SVN or a nightly build.
>
> 2. For the Windows environment, I had the following experience:
> a. The Windows port of git works fine against a native git repository.
> b. The git-svn is only available for cygwin and is hard to setup right
> / potentially broken.
> c. Virtual Machine option is a nice to have, it is not a requirements.
>
> 3. Some Windows/DVCS related questions:
> 1. Did any one use any of the DVCS products under Windows?  Specially
> in combination with TortoiseXX interface?
> 2. If so which ones and what is your experience?
> 3. Is it possible to run this DVCS with SVN as the backend?  i.e. same
> way we did with Git.
>
> I think it may be feasible to test one of the other options with
> Windows / Linux and compare with Git.  However, I don't think it is
> efficient to test everyone out there.
>
> On Thu, Oct 30, 2008 at 12:28 PM, John Reese <jr...@le...> wrote:
>> The discussion is likely not getting anywhere, so I will just sum up
>> what I was trying to accomplish:
>>
>> 1. Discuss why we as the development team want to move away from SVN to
>> a DVCS tool, so that we can implement certain development practices more
>> easily than we can using SVN, or similarly, SVN hosted by SourceForge.
>>
>> 2. Discuss why we wanted to move to Git as opposed to other DVCS tools
>> like Mercurial or Bazaar.  This is more of a personal preference choice,
>> as most of us were trying to establish that most DVCS tools can
>> accomplish the same tasks; it's merely a choice of preference as to
>> which you choose.  Our (or rather, Victor, Giallu, my) preference is
>> currently on Git.
>>
>>
>> Unfortunately, like the venerable Emacs/Vim topic, DVCS choices tend to
>> result in 'holy wars' type of discussions, in which each side feels that
>> their choice is the best choice, and unfortunately, neither side is
>> likely to ever be capable of changing their preference.
>>
>> I don't think there are really any 'facts' that would really have any
>> bearing on which DVCS we choose, because all the major DVCS tools have
>> the same overall feature sets, and anyone can easily pick up any DVCS
>> tool and start using it, assuming the person in question is willing to
>> learn and read documentation; if not, all hope is lost anyways.
>>
>> The distinguishing factors are therefore the implementation details and
>> which of the tools implement the details in a manner favorable to the
>> developers.
>>
>> Disagree?
>>
>> --
>> John Reese
>> LeetCode.net
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> mantisbt-dev mailing list
>> man...@li...
>> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>