monotone Mtn Source Tree


2This document gives a rough overview of features and changes planned
3for the future of monotone development. It does not spontaneously
4include bug fixes. We endeavour to fix bugs when possible, throughout
5the development cycle. When a specific class of bugs is targeted for
6focus in the roadmap, it is noted here.
8The roadmap does *not* include release points, because it is our
9intention (though at times not our demonstrated behavior) to stick as
10close as possible to time-based releases, once per month. Even if we
11happen to hold up a release for some unforseen reason -- usually lack
12of available effort -- the *plan* is to operate in a time-based
15Note also that the roadmap is (broadly) conservative. The goal with
16monotone is to produce a stable tool which works fast, reliably,
17predictably, and helps users manage their ever-growing collections of
18diverging data.
24- tidy up major buid/use-breaking bugs in win32, BSD, OSX versions
25- improve netsync error reporting code
26 - one part: many 'I's should be 'require's.
27- overhaul command-line option processing, perhaps use argp
28- move output formatting to lua hooks
29- integrate net.venge.monotone.ssh branch
30- modify database code to use sqlite3 pre-parsed queries, blobs
31- change netsync to globbing branches, not using collections
32- implement improved ACL/permission system for default trust rules
33- implement "merge into working copy" approach to merging
34- emacs integration
36 ( probably call it "1.0" or "stable" around here )
38- work on GUIs and web UIs
39- "merge before commit" (CVS-style online commit-coordination)
40- bidirectional mirroring between monotone and CVS/SVN/arch
41- (possible) try using botan instead of cryptopp
42- an "agent" for storing decrypted private key in memory
43- "hash-migration" technology for scenarios where SHA1 falls

Archive Download this file



Quick Links:    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status