Distributed VCS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benny,

Yes, you don't have many committers, but you have many integrators.  I
think that is where the power of DVCS really shines.  Now, I am not an
expert on DVCS yet, and I am still wrapping my head around its concepts.
However, its main reason for being is to support multiple lines of
development and to allow the developers to control which pieces make it
into "their" codebase.  For instance, I have made some significant
modifications to your codebase to integrate into my codebase.  I have
also submitted back changes to you.  Theoretically, a DVCS system would
make this much easier.

I know you use Trac to manage your bugs, and that is also the system I
am looking it, because it will integrate with Bazaar as well as the
default SVN.  I like Bazaar the best so far, because of its
concentration on merge and its professional level quality website.  Even
its icon is a merge sign.  I agree with the premise that merging is the
all-important activity, and branching is secondary.  Most VCS's invert
those priorities.

Anyway, I am still investigating and learning about DVCS.  I'll be
looking more closely at Mercurial, but so far Bazaar seems to be
superior to it.

Regards,
Jim Gomes


> -----Original Message-----
> From: pjsip-bounces@xxxxxxxxxxxxxxx
[mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of
> Benny Prijono
> Sent: Tuesday, 10 June, 2008 10:43 AM
> To: pjsip list
> Subject: Re: svn update error: Failed to
adddirectory'third_party\speex'
> 
> On Tue, Jun 10, 2008 at 5:35 PM, Jim Gomes <Jim.Gomes at tideworks.com>
wrote:
> > Benny,
> >
> > Have you thought about moving to git or some other DVCS program like
> > Bazaar?  Not that I am recommending you should do so, just asking if
you
> > have considered it.  We are looking into DVCS's for our project, and
> > currently Bazaar is the front runner.  Git is not an option, since
it
> > does not have Windows support.
> >
> 
> Hi Jim,
> 
> yeah I've thought of that a bit, in more than one occasions, and in
> the end always concluded that we don't DVCS yet. Mostly it's because
> we only have few people working with the source (read: having write
> access), we don't have problem with reliability (or so we thought),
> and the seamless integration of SVN with Trac is just very very nice.
> 
> One thing that I'm still not sure about is whether DVCS will make life
> easier for our users. One of the drawback of SVN (and maybe
> other/similar VC) is it makes it very difficult to manage if you
> maintain your own repository and have pjsip repository inside it, and
> if you make modifications  to pjsip. I have a hunch that the
> distributed nature of a DVCS will somewhat makes this task easier, but
> haven't investigated this further.
> 
> What makes you want a DVCS btw?
> 
> Cheers
>  Benny
> 
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
> 
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux