Changes between Version 49 and Version 50 of ReleaseProcedure
- Timestamp:
- Nov 15, 2009, 10:55:23 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseProcedure
v49 v50 42 42 m4_define([YAT_LT_VERSION_INFO], [c:r:a]) 43 43 }}} 44 1. Add a line in NEWS 45 {{{ 46 See the end for copyrights and conditions. 47 48 +yat A.B.x series from http://dev.thep.lu.se/yat/svn/branches/A.B-stable 49 + 50 Version A.B (released NOT YET) 51 }}} 52 commit the changes with `svn ci -m "preparing branch A.B-stable"`[[br]][[br]] 44 53 1. Update copyright statements with command: 45 54 {{{ 46 55 svndigest --copyright --no-report -v 47 56 }}} 48 (The `--no-report` option works with svndigest 0.7 and later, for earlier version omit the option.) Examine the updates and commit changes with `svn ci -m "updating copyright statements"`. 49 For this step [http://dev.thep.lu.se/svndigest svndigest] is obviously needed.[[br]][[br]] 57 (The `--no-report` option works with svndigest 0.7 and later, for 58 earlier version omit the option.) Examine the updates and commit 59 changes with `svn ci -m "updating copyright statements"`. For this 60 step [http://dev.thep.lu.se/svndigest svndigest] is obviously 61 needed.[[br]][[br]] 62 1. Make a copy of trunk WC including svndigest cache 63 {{{ 64 cp /path/to/yat-trunk /path/to/yat-A.B.x 65 }}} 50 66 1. Create a new minor branch using a one liner like 51 67 {{{ … … 54 70 -m "New minor version A.B branch" 55 71 }}} 72 1. Switch the new WC to follow new branch 73 {{{ 74 cd /path/to/yat-A.B.x/ 75 svn switch http://dev.thep.lu.se/yat/svn/branches/A.B-stable 76 cd /path/to/yat-trunk/ 77 }}} 56 78 1. Prepare the trunk for the next minor release [[br]][[br]] 57 79 i. Update version number in `m4/version.m4`. Locate and change the … … 63 85 i. Add an entry in `NEWS` 64 86 {{{ 65 version A.[B+1] (released DATE)87 version A.[B+1] (released NOT YET) 66 88 }}} 67 89 The date is set when version A.[B+1] is released. [[br]][[br]] 68 90 i. Commit changes to the repository, 69 `svn ci -m " Changes for future releaseA.[B+1]"` [[br]][[br]]91 `svn ci -m "Bumping VERSION to A.[B+1]"` [[br]][[br]] 70 92 1. When someone with access to documentation site has time available, 71 93 they will upgrade to the new branch. This person is usually not the … … 89 111 m4_define([YAT_LT_VERSION_INFO], [c:r:a]) 90 112 }}} 91 appropriately. Refer to the interface version list in `m4/version.m4` to figure out the settings of c, r, and a. c should increase with 1 if the interface has changed. If the interface is changed, r should be set to zero and a should be set to reflect backward compatibility level of this version. If interface was not changed just increase r with 1. See `m4/version.m4` and the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]] 113 appropriately. Refer to the interface version list in 114 `m4/version.m4` to figure out the settings of c, r, and a. c 115 should increase with 1 if the interface has changed. If the 116 interface is changed, r should be set to zero and a should be set 117 to reflect backward compatibility level of this version. If 118 interface was not changed just increase r with 1. See 119 `m4/version.m4` and the 120 [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning 121 libtool manual] for details.[[br]][[br]] 92 122 i. Update `THANKS`. Remember, ego and vanity is the currency of open 93 123 source projects. Well, there are other reasons for open source … … 113 143 Run 114 144 {{{ 145 make all 115 146 make release 116 147 }}} 117 If everything is OK, attach the new package to the DownloadPage, else start over.[[br]][[br]]118 1. C reate a tag, but first check that you are synchronized with repository148 Fix potential problems.[[br]][[br]] 149 1. Check that you are synchronized with repository 119 150 {{{ 120 151 svn status -q -u … … 135 166 i. Add an entry in `NEWS` 136 167 {{{ 137 version A.B.1 (released DATE)168 version A.B.1 (released NOT YET) 138 169 }}} 139 170 The date is set when version A.B.1 is released. [[br]][[br]] 140 171 i. Commit changes to the repository, 141 `svn ci -m "Changes for future release A.B.1"` [[br]][[br]] 172 `svn ci -m "Bumping VERSION to A.B.1"` [[br]][[br]] 173 1. Upload `yat-A.B.tar.gz` and md5 file to Downloadpage [[br]][[br]] 142 174 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]] 143 175 i. Update the section '''Latest stable release''' to reflect the new … … 174 206 minimize the risk of loosing fixes, this step is only performed by 175 207 the ''Merge Master''. [[br]][[br]] 176 i. Switch to the trunk or checkout a pristine version of the trunk. 177 {{{ 178 svn switch http://dev.thep.lu.se/yat/svn/trunk 179 180 }}} 181 or 182 {{{ 183 svn checkout http://dev.thep.lu.se/yat/svn/trunk trunk_merge 184 cd trunk_merge 208 i. Go to a pristine trunk WC 209 {{{ 210 cd /path/to/yat-trunk/ 211 svn update 212 svn status -q 185 213 }}} 186 214 i. Merge changes into trunk. In this example the difference between a … … 197 225 i. Commit changes to the trunk branch. 198 226 {{{ 199 svn commit -m "Merged patch release A.B to the trunk. Delta A.B - A.B@fork_revision" 200 }}} 201 Remove `trunk_merge` if it was created. [[br]][[br]] 227 svn commit -m "Merged release A.B to the trunk. Delta A.B - A.B@fork_revision" 228 }}} 202 229 203 230 … … 236 263 Run 237 264 {{{ 265 make all 238 266 make release 239 267 }}} 240 If everything is OK, attach the new package to the DownloadPage, else start over.[[br]][[br]]268 Fix potential problems.[[br]][[br]] 241 269 1. Create a tag, but first check that you are synchronized with repository 242 270 {{{ … … 261 289 m4_define([YAT_LT_VERSION_INFO], [c:r+1:a]) 262 290 }}} 263 i.e., only raise the revision number since the interface will not change. See the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]] 291 i.e., only raise the revision number since the interface will not 292 change. See the 293 [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning 294 libtool manual] for details.[[br]][[br]] 264 295 i. Add an entry in `NEWS` 265 296 {{{ … … 268 299 The date is set when version A.B.[C+1] is released. [[br]][[br]] 269 300 i. Commit changes to the repository, 270 `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]] 301 `svn ci -m "Bumping VERSION to A.B.[C+1]"` [[br]][[br]] 302 1. Upload `yat-A.B.C.tar.gz` and md5 file to DownloadPage [[br]][[br]] 271 303 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]] 272 304 i. Update the section '''Latest stable release''' to reflect the new … … 298 330 minimize the risk of loosing fixes, this step is only performed by 299 331 the ''Merge Master''. [[br]][[br]] 300 i. Switch to the trunk or checkout a pristine version of the trunk. 301 {{{ 302 svn switch http://dev.thep.lu.se/yat/svn/trunk 303 }}} 304 or 305 {{{ 306 svn checkout http://dev.thep.lu.se/yat/svn/trunk trunk_merge 307 cd trunk_merge 332 i. cd to a pristine trunk WC 333 {{{ 334 cd /path/to/yat-trunk/ 335 svn update 336 svn status -q 308 337 }}} 309 338 i. Merge changes into trunk. In this example the diffence between a … … 322 351 svn commit -m "Merged patch release A.B.1 to the trunk. Delta A.B.1 - A.B" 323 352 }}} 324 Remove `trunk_merge` if it was created. [[br]][[br]] 353