ellisonbg.net at gmail.com
Fri Feb 8 14:00:26 EST 2008
Disclaimer: I have little experience with distributed version control
and thus am not qualified to comment on the relative strengths and
weaknesses of bsr and hg.
WIth that said, Launchpad is extremely impressive. Not only is it
ready today, it would free all of us up from having to play part time
sys-admin with trac/hg/etc (a role that I am sure Fernando would be
glad to give up). Even if we did have hg+trac fully setup today, the
feature set, usability, maintainability of launchpad+bzr is still far
As we move to a distributed model, it would still be useful to have a
place for everyone to publish their branches - launchpad makes that
easy. It would be a huge pain if everyone had to setup their own web
server to share their hg repos with everyone else.
Summary - hg would have to be _way_ better than bzr for us not to
consider using launchpad+bzr.
On Feb 8, 2008 11:09 AM, Ville M. Vainio <vivainio at gmail.com> wrote:
> There was some talk on Leo mailing list about Launchpad, https://launchpad.net/
> What do you guys think? Could Launchpad be the platform where we could
> be driving IPython forward? It would imply using bzr instead of hg,
> but I'm not sure the benefits of hg over bzr (performance comes to
> mind first) overweigh the advantages of using launchpad (one of the
> advantages being that it's ready now).
> Perhaps we should see how IPython svn can be exported to launchpad
> bzr, and see what kind of performance we can get out of it (it
> certainly can't be worse than svn). The usage patterns of hg and bzr
> are similar enough, so I don't care either way.
> It's certainly worth a thought.
> Ville M. Vainio - vivainio.googlepages.com
> blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
> IPython-dev mailing list
> IPython-dev at scipy.org
More information about the IPython-dev