126 | | svn copy http://dev.thep.lu.se/svndigest/svn/branches/A.B-stable \ |
127 | | http://dev.thep.lu.se/svndigest/svn/tags/A.B \ |
128 | | -m "tagging version A.B" |
129 | | }}} |
130 | | 1. Prepare the minor branch for the first patch release [[br]][[br]] |
131 | | i. Update version number in `version.m4`. Locate and change the |
132 | | below line |
133 | | {{{ |
134 | | m4_define([PATCH_VERSION], [1]) |
135 | | m4_define([SVNDIGEST_DEV_BUILD], [true]) |
136 | | }}} |
137 | | i. Add an entry in `NEWS` |
138 | | {{{ |
139 | | version A.B.1 (released NOT YET) |
140 | | }}} |
141 | | The date is set when version A.B.1 is released. [[br]][[br]] |
142 | | i. Commit changes to the repository, |
143 | | `svn ci -m "Bumping version"` [[br]][[br]] |
| 126 | svn copy ^/branches/A.B-stable ^/tags/A.B -m "tagging version A.B" |
| 127 | }}} |
201 | | svn commit -m "Merged release A.B to the trunk. Delta A.B - A.B@fork_revision" |
202 | | }}} |
| 184 | svn commit -m "Merged release A.B to the trunk." |
| 185 | }}} |
| 186 | 1. Prepare the minor branch for the first patch release [[br]][[br]] |
| 187 | i. Update version number in `version.m4`. Locate and change the |
| 188 | below line |
| 189 | {{{ |
| 190 | m4_define([PATCH_VERSION], [1]) |
| 191 | m4_define([SVNDIGEST_DEV_BUILD], [true]) |
| 192 | }}} |
| 193 | i. Add an entry in `NEWS` |
| 194 | {{{ |
| 195 | version A.B.1 (released NOT YET) |
| 196 | }}} |
| 197 | The date is set when version A.B.1 is released. [[br]][[br]] |
| 198 | i. Commit changes to the repository, |
| 199 | `svn ci -m "Bumping version"` [[br]][[br]] |
248 | | svn copy http://dev.thep.lu.se/svndigest/svn/branches/A.B-stable \ |
249 | | http://dev.thep.lu.se/svndigest/svn/tags/A.B.C \ |
250 | | -m "tagging version A.B.C" |
251 | | }}} |
252 | | 1. Prepare the minor branch for the next patch release [[br]][[br]] |
253 | | i. Update version number in `configure.ac`. Locate and change the |
254 | | below line |
255 | | {{{ |
256 | | m4_define([PATCH_VERSION], [C+1]) |
257 | | m4_define([SVNDIGEST_DEV_BUILD], [true]) |
258 | | }}} |
259 | | i. Add an entry in `NEWS` |
260 | | {{{ |
261 | | version A.B.[C+1] (released DATE) |
262 | | }}} |
263 | | The date is set when version A.B.[C+1] is released. [[br]][[br]] |
264 | | i. Commit changes to the repository, |
265 | | `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]] |
| 245 | svn copy ^/branches/A.B-stable ^/tags/A.B.C -m "tagging version A.B.C" |
| 246 | }}} |
| 295 | 1. Prepare the minor branch for the next patch release [[br]][[br]] |
| 296 | i. Update version number in `m4/version.m4`. Locate and change the |
| 297 | below line |
| 298 | {{{ |
| 299 | m4_define([PATCH_VERSION], [C+1]) |
| 300 | m4_define([SVNDIGEST_DEV_BUILD], [true]) |
| 301 | }}} |
| 302 | i. Add an entry in `NEWS` |
| 303 | {{{ |
| 304 | version A.B.[C+1] (released DATE) |
| 305 | }}} |
| 306 | The date is set when version A.B.[C+1] is released. [[br]][[br]] |
| 307 | i. Commit changes to the repository, |
| 308 | `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]] |