monotone

monotone Mtn Source Tree

Root/NEWS

1monotone (0.45-1) unstable; urgency=low
2
3 * The fix for bug #542287 changes the default run-levels in which
4 the monotone server is started, and may overwrite local customizations
5 to those run-levels in some cases. If you use the monotone-server
6 package and you changed the /etc/rc*.d links for it, check after
7 upgrade to make sure they are the way you want them.
8
9 * Upstream made major changes to key handling: certs now refer to
10 the key that signed them by hash, not name. This permits some
11 significant security and usability improvements: for instance, it
12 is now possible to retire an old key without changing to a new
13 email address. See NEWS and UPGRADE for full details.
14
15 There is no "flag day" for this: you do not have to upgrade at the
16 same time as everyone else in your projects. However, if you have
17 more than one public key in your database with the same name,
18 older clients will not be able to process all of the certs signed
19 with those keys.
20
21 The database format did change. You need to do the following on
22 each of your databases after taking a backup of them (except for
23 the server database handled by the monotone-server package, for
24 which it is done automatically):
25
26 mtn db migrate
27
28 -- Zack Weinberg <zackw@panix.com> Sat, 14 Nov 2009 12:38:19 -0800
29
30monotone (0.40-1) unstable; urgency=low
31
32 * The database format has changed for efficiency. You need to do the
33 following on each of your databases after taking a backup of them
34 (except for the server database handled by the monotone-server
35 package, for which it is done automatically):
36
37 mtn db migrate
38
39 -- Richard Levitte <richard@levitte.org> Thu, 03 Apr 2008 16:55:36 +0200
40
41monotone (0.31-90.2) unstable; urgency=low
42
43 * "mtn serve" doesn't take any mandatory arguments any more. Instead
44 of specifying branches to serve (or to exclude) on the command line,
45 mtn now entirely trusts the netsync permission hooks called
46 get_netsync_read_permitted and get_netsync_write_permitted.
47
48 If you have any "mtn serve" still running with branches given on the
49 command line, you will need to remove those and work on the hooks.
50 If you just have the argument "*", it can safely be removed. Not
51 doing so will cause your server to stop working.
52
53 -- Richard Levitte <richard@levitte.org> Sat, 18 Nov 2006 22:35:15 +0100
54
55monotone (0.31-90.1) unstable; urgency=low
56
57 * Another efficiency change. You need to do the following on each
58 of your databases (except for the server database handled by the
59 monotone-server package, for which this is done automatically):
60
61 mtn db migrate
62 # ... possibly other commands, depending on how old your previous
63 # mtn version was
64 mtn db regenerate_caches
65
66 This does NOT affect remote participants of your projects, the
67 changes are only local.
68
69 -- Richard Levitte <richard@levitte.org> Mon, 13 Nov 2006 22:56:10 +0100
70
71monotone (0.30-0.1) unstable; urgency=low
72
73 * Efficiency changes have been implemented, which changes the rosters
74 (and internal file description structure). It means that you will
75 have to do the following on each of your databases (except for the
76 server database handled by the monotone-server package, for which
77 this is done automatically):
78
79 mtn db migrate
80 # ... possibly other commands, depending on how old your previous
81 # mtn version was
82 mtn db regenerate_rosters
83
84 This does NOT affect remote participants of your projects, the
85 changes are only local.
86
87 -- Richard Levitte <richard@levitte.org> Thu, 7 Sep 2006 05:15:43 +0200
88
89monotone (0.30-0.1) unstable; urgency=low
90
91 * [this is copied from the normal monotone NEWS file]
92
93 In this release, there is a minor change to the format of the
94 data stored in the bookkeeping directory "_MTN". You must run
95 the command "mtn migrate_workspace" in all your existing
96 workspaces before you can use them with this version of
97 monotone; once you have done this, you will not be able to use
98 those workspaces with older versions of monotone. Nothing
99 terrible will happen if you try to use an old workspace
100 without migrating it; you'll just get an error message.
101
102 This change makes it possible for a workspace to have more
103 than one parent revision, which will enable a number of
104 long-wanted features. Those features are not yet complete,
105 but we do not expect to have to change formats again to
106 support them.
107
108 -- Richard Levitte <richard@levitte.org> Tue, 5 Sep 2006 08:18:34 +0200

Archive Download this file

Branches

Tags

Quick Links:     www.monotone.ca    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status