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