Changes between Version 26 and Version 27 of ReleaseProcedure


Ignore:
Timestamp:
Jul 9, 2007, 11:05:12 PM (14 years ago)
Author:
Peter Johansson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v26 v27  
    170170This section describes what to do when publishing a patch release A.B.C.
    171171
    172  1. Make sure that all commits are performed into to the trunk, such
     172 1. Make sure that all commits are performed into to the branch, such
    173173    as bumping version number(s) (`configure.ac`), acknowledge
    174174    contributions (`THANKS`), update files `NEWS` and
     
    192192        - http://trac.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id
    193193}}}
     194  where `N` is given by
     195{{{
     196$ svn update
     197N-2
     198}}}
     199  and `M` should have been set at previous release.[[br]][[br]]
    194200  i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
    195201     [[br]][[br]]
     
    201207./bin/svndigest --copyright
    202208}}}
    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]]
    204210 1. Needless to say, make sure that the program is in a state to be
    205211    released; make sure that all the tests pass, test the distribution
     
    213219 1. Create a tag using a one liner like
    214220{{{
    215 svn copy http://lev.thep.lu.se/repository/svndigest/branch/A.B-stable \
     221svn copy http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
    216222    http://lev.thep.lu.se/repository/svndigest/tags/A.B.C \
    217223    -m "Tagging version A.B.C"