Changes between Version 74 and Version 75 of ReleaseProcedure
- Timestamp:
- Oct 22, 2011, 7:12:53 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseProcedure
v74 v75 83 83 you can create checksum files, i.e., you need `openssl` and `md5`/`md5sum`. 84 84 85 1. Create a new milestone for next patch release A.B.1. 85 86 1. Make sure that all commits are performed into to the trunk, such 86 87 as bumping version number(s) ([source:trunk/m4/version.m4 version.m4]), … … 168 169 1. Close the [http://dev.thep.lu.se/svndigest/roadmap milestone] 169 170 associated with the release and replace `head` with appropriate 170 revision. Add a new milestone as needed (with log link).[[br]][[br]]171 revision.[[br]][[br]] 171 172 1. Merge the release into the trunk. To avoid confusion and 172 173 minimize the risk of loosing fixes, this step is only performed by … … 217 218 you can create checksum files, i.e., you need `openssl` and `md5`/`md5sum`. 218 219 220 1. Create a new milestone for next patch release A.B.C+1 219 221 1. Make sure that all commits are performed into to the branch, such 220 222 as bumping version number(s) (`version.m4`), acknowledge … … 284 286 and links `[source:tags/A.B.C/NEWS NEWS]`.[[br]][[br]] 285 287 1. Close the milestone associated with the release and replace 286 `head` with appropriate revision in log link. Add a new milestone 287 as needed (with a log link). 288 `head` with appropriate revision in log link. 288 289 1. Update the version list in Trac using the 289 290 [http://dev.thep.lu.se/svndigest/admin/ticket/versions trac-admin tool].