Changes between Version 10 and Version 11 of RBuild
- Timestamp:
- Jul 23, 2008, 8:03:06 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RBuild
v10 v11 13 13 == Select version # == 14 14 15 x.yy.zz (ie 3.05.09) 16 17 WarpIN drops leading zeros, but we use them to get alpha sorts 15 Version numbers are of the form x.yy.zz, where x is the major version, yy is the minor version and zz is the CSD level. The CSD level is typically 00 and is not displayed unless it has some other value. 16 17 The separator for user visible version numbers is a period. The period may be transformed to an underscore or dash when the version number is used to derive a directory name. 18 19 The current version is 3.12.00. 20 21 WarpIN drops leading zeros, but we supply them to get alpha sorts in directory and file listings. 18 22 19 23 == Final check source code and update markings == … … 69 73 '''version #''' (major releases only) 70 74 71 Commit modified files. 72 73 Rebuild with wmake -a and verify no regressions. 75 == Commit modified files and verify == 76 77 Commit with 78 79 {{{ 80 svn commit 81 }}} 74 82 75 83 Verify everything checked in with 76 84 77 '''svn status -v |& less''' 85 {{{ 86 svn status -v |& less 87 }}} 88 89 Look for unexpected ?s in column 1. These can indicate new files that must be added to the repository. 90 91 To prevent spurious ?s, edit global-ignores in %HOME%\.subversion\config to suppress the marking for known build products. 92 93 Rebuild with 94 95 {{{ 96 wmake -a. 97 }}} 98 99 Verify no regressions. 78 100 79 101 == Apply tag == 80 102 81 svn copy -m"Tag release FM2-3_05-09" http://svn.netlabs.org/repos/fm2/trunk http://svn.netlabs.org/repos/fm2/tags/FM2-3_05-09 82 83 '''FM2-3_0x-0y''' 84 85 == Build for Release == 86 87 cd fm2_workspace\trunk (i.e. top directory of the FM/2 source) 88 103 Tags are of the form '''FM2-3_xx-yy''', where xx is the minor version and yy is the CSD level. The CSD will typically be 00. 104 105 Create the tag with a command similar to 106 107 {{{ 108 svn copy -m"Tag release FM2-3_12_00" http://svn.netlabs.org/repos/fm2/trunk 109 http://svn.netlabs.org/repos/fm2/tags/FM2-3_12_00 110 }}} 111 112 == Build for release == 113 114 If fm2_workspace\trunk is the root directory of your FM/2 source workspace, build with 115 116 {{{ 117 cd fm2_workspace\trunk 89 118 set DEBUG= 90 91 Run wmake -a or wmake all. 92 93 == Test final build == 119 set FORTIFY= 120 wmake -a 121 }}} 122 123 == Test release build == 94 124 95 125 Test the binaries. At a minimum you should run all the exes and do some basic file manipulation with each. You should, where possible, also verify that any bugs that were fixed for the release are working as expected. … … 97 127 == Lxlite binaries == 98 128 99 Run wmake lxlite to compress exe/dlls 100 101 == Retest final build== 102 103 Verify that all the exes continue to load and run after being compressed. Lxlite has no known defects, but it's better to be safe. 104 105 == Build distros == 106 107 Run wmake dist (see [wiki:WPIBuild Building FM/2 WarpIN installation files] for more information). 108 109 Zip the distribution FM2*.wpi and add the FM2utilities wpi package if desired. 110 111 We do not routine make source distributions since the source is available from Netlabs. 129 Run 130 131 {{{ 132 wmake lxlite 133 }}} 134 135 to compress exes and dlls. 136 137 == Retest final build == 138 139 Verify that all exes continue to load and run after being compressed. Lxlite has no known defects, but it's better to be safe. 140 141 == Build distro == 142 143 Run 144 145 {{{ 146 wmake dist 147 }}} 148 149 to build distribution .wpi. 150 See [wiki:WPIBuild Building FM/2 WarpIN installation files] for more information. 151 152 Zip the distribution FM2*.wpi and add the FM2utilities wpi package if desired. 153 154 We do not routinely build source distributions since the source is available from Netlabs. 112 155 113 156 == Distribute distro == … … 125 168 == Mark milestone complete == 126 169 127 Create a TRAC version for the next version .170 Create a TRAC version for the next version, if needed. 128 171 129 172 Mark the current version as the default version for new tickets. 130 173 131 Create a TRAC milestone for the next version release .132 133 M orethe new milestone as the default milestone.174 Create a TRAC milestone for the next version release, if needed. 175 176 Mark the new milestone as the default milestone. 134 177 135 178 Mark the completed milestone as complete and move any residual tickets to a future milestone. 136 179 137 TRAC can move the tickets for youwhen you mark the version milestone complete.180 TRAC can move the tickets in bulk when you mark the version milestone complete. 138 181 139 182 == Known tags == 140 {{{ 141 FM2-3.12.00 142 FM2-3.11.00 143 FM2-3.10.00 144 FM2-3.09.00 183 184 See source:tags for the full list. 185 186 Some recent tags are 187 188 {{{ 189 FM2-3.12-00 190 FM2-3.11-00 191 FM2-3.10-00 192 FM2-3.09-00 145 193 FM2-3.08 146 FM2-3.07 .00194 FM2-3.07 147 195 FM2-3.07.BETA-01 148 196 FM2-3.06.00 First OpenWatcom Build