Changes between Version 3 and Version 4 of MonotoneLimitations

Timestamp:

Dec 20, 2006, 10:24:55 PM (17 years ago)

Author:

elb

Comment:

--

MonotoneLimitations

@@ -5 +5 @@
  * '''No workspace merge''' - The inability to perform logical fixups at merge-time (only conflict fixups) introduces a glitch into our traditional "Pidgin should always compile" philosophy.  While we recognize that a DVCS may require some workflow changes, this isn't one we're ready to give up on, yet.
  * '''{{{annotate}}} and {{{log <file>}}} speed''' - Particularly while we are validating the svn import, these are noticable limitations.  Work is underway upstream to mitigate these, in the form of "heights".  See [Monotone:RevisionNumbering] for some details; one of those heights proposals has been accepted, and a faster {{{log <file>}}} will be in the 0.32 release.  {{{annotate}}} remains in a branch.
- * '''Partial Pull''' - Complete (initial) pulls of Gaim are ~1h on a fast connection.  This is too long to expect any casual developer to invest.  There are several possible mitigations for this (and monotone is working on both complete pull improvements, and partial pull):
+ * '''Partial Pull''' - Complete (initial) pulls of Gaim are ~35 minutes on a fast connection.  This is too long to expect any casual developer to invest.  There are several possible mitigations for this (and monotone is working on both complete pull improvements, and partial pull):
   * Provide a monotone-to-svn (or similar) gateway for "casual" development.  Obviously the severe limitations of svn will make this painful for serious development, and we would not provide a svn-to-monotone gateway; however, for one-off patches from parties with limited interest, it would probably suffice.
   * Provide a monotone database (or database dump) for download; this bootstraps the process, and while it requires a large download, it is much less CPU-intensive and quite a bit faster than a proper pull.  It looks like a bzipped database dump is about 80MB at this point.