On di, 2009-01-06 at 04:53 -0500, Behdad Esfahbod wrote: > Ali Sabil wrote: > > > Concerning the asserted flaws in John's proposal, the only valid point, > > is that it will need testing as the implementation is not very mature > > yet, > > And that's a HUGE issue, mind you.
Here's another problem I'd like to see pointed out. While the hybrid solution might work fine within the GNOME infrastructure, what happens if an outside contributor clones a repository, hacks on and publishes his code on his own server. Remember, we are talking about DVCSes, this *will* happen, it should happen. What if this user publishes his branch using bzr (which works fine with the GNOME servers). How will I merge this branch, if I'm using git? It looks to me that with the git+bzr proposal, we're being forced to learn both systems anyway. We can control what's going on on our own servers, but not what happens outside. So don't tell us it's equivalent. It's not. And let's not forget the broad confusion that will arise from the fact that part of the developers advice you to use git and other parts advice you to use bzr. I am exceedingly less convinced that the advantages of supporting both outweigh the disadvantages (looking at the usage patterns, not the technical merits). R -- Ruben Vermeersch (rubenv) http://www.savanne.be _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
