Changes between Version 26 and Version 27 of ReleaseProcedure
- Timestamp:
- Jul 9, 2007, 11:05:12 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseProcedure
v26 v27 170 170 This section describes what to do when publishing a patch release A.B.C. 171 171 172 1. Make sure that all commits are performed into to the trunk, such172 1. Make sure that all commits are performed into to the branch, such 173 173 as bumping version number(s) (`configure.ac`), acknowledge 174 174 contributions (`THANKS`), update files `NEWS` and … … 192 192 - http://trac.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id 193 193 }}} 194 where `N` is given by 195 {{{ 196 $ svn update 197 N-2 198 }}} 199 and `M` should have been set at previous release.[[br]][[br]] 194 200 i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"` 195 201 [[br]][[br]] … … 201 207 ./bin/svndigest --copyright 202 208 }}} 203 Examine the updates and commit changes with `svn ci -m "updating copyright statements"` [[br]][[br]]209 Examine the updates and commit changes with `svn ci -m "updating copyright statements"`.[[br]][[br]] 204 210 1. Needless to say, make sure that the program is in a state to be 205 211 released; make sure that all the tests pass, test the distribution … … 213 219 1. Create a tag using a one liner like 214 220 {{{ 215 svn copy http://lev.thep.lu.se/repository/svndigest/branch /A.B-stable \221 svn copy http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \ 216 222 http://lev.thep.lu.se/repository/svndigest/tags/A.B.C \ 217 223 -m "Tagging version A.B.C"