On Thu, Feb 12, 2009 at 6:39 AM, Ben Wheeler <[email protected]> wrote: > On Wed, Feb 11, 2009 at 12:59:21PM -0800, Albert Santoni wrote: >> There also seems to be agreement that version controls systems in >> general attract fanboy crowds and flamewars that border on zealotry. >> We're need to cut through the crap and make sure we look at things >> objectively, and especially pay attention to our unique constraints >> (mainly cross-platform development). > > The only DVCS I have much experience of is darcs. I like it a lot. > It's *very* easy to use, especially if you have CVS or SVN experience. > It seemed to be the best of the bunch for cherry-picking patches > (with automatic dependency solving) and sending them around between repos. > > Really it's absolutely perfect as far as I'm concerned, except for two things: > > 1. You need to come up with a system for patch naming. Patches don't > have any kind of automatic unique name, but they really need a unique > name in order to be easily cherry-pickable, so it's up to developers > to come up with a naming system and be religious about following it. > This is no big deal as far as I'm concerned, and if you forget, it's > usually possible to undo the mistake. > > 2. It has a design flaw that can, in rare circumstances, cause a > conflicted merge to implode, take infinite time, and/or break the repo > in a way that is very hard to undo. I still haven't really worked out > how rare these rare circumstances are, or what the consequences would be, > so if anyone knows more about it please chip in. > > Despite these, I would recommend anyone interested in DVCS look at darcs. > But it may be that for this project, bzr is the natural choice because > of the Launchpad integration. Certainly my experience trying to > integrate Launchpad with other VCSs has not been a happy one... >
I don't have any experience with bzr beyond the last few days. The reason I'm eyeing it is to streamline this project by reduce the number of websites we're spread across. But another point for bzr: if you install bzr-svn you can work on svn and bzr at the same time, which will let us keep pushing to sourceforge while we get used to it. So it seems like everyone is in agreement about bzr? At least, no one is screaming against it. I'm asking about the best way to transition from SF: https://answers.edge.launchpad.net/launchpad-bazaar/+question/60675, once I'm sure I understand that I'll get the initial import done and point lp:mixxx at it. -Nick ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
