Changes between Version 25 and Version 26 of ReleaseProcedure


Ignore:
Timestamp:
Mar 25, 2008, 9:02:09 AM (14 years ago)
Author:
Nicklas Nordborg
Comment:

Updating release procedure

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v25 v26  
    232232  i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
    233233     [[br]][[br]]
    234  1. Update copyright statements with the below command. Make sure that you do not break file
    235     encodings such as UTF-8 and what not. One example, do not use non-US characters for developer
    236     names in the source:trunk/.svndigest/config file.
    237 {{{
    238 svndigest --copyright --no-report
    239 }}}
    240     Examine the updates and commit changes with `svn ci -m "updating copyright statements"`. For
    241     this step [http://trac.thep.lu.se/trac/svndigest svndigest] is obviously needed. [[br]][[br]]
    242234 1. Needless to say, make sure that the program is in a state to be
    243235    released; make sure that all the tests pass, test the distribution
     
    292284  i. Add a new entry to the ''Base A.B'' subsection in the '''All packaged BASE releases'''
    293285     section. [[br]][[br]]
     286 1. Close the milestone associated with the release and replace `head` with appropriate
     287    revision in log link. Add a new milestone as needed (with an associated log link like
     288    ''Revision Log: log:branches/A.B-stable@3001:head'' in the description field). [[br]][[br]]
     289 1. [mailto:basedb-users@lists.sourceforge.net,basedb-devel@lists.sourceforge.net,basedb-announce@lists.sourceforge.net Announce]
     290    the new release in the mailing list.[[br]][[br]]
    294291 1. Merge the patch release into the trunk. To avoid confusion and
    295292    minimize the risk of loosing fixes, this step is only performed by
     
    314311svn commit -m "Merged patch release A.B.1 to the trunk. Delta A.B.1 - A.B"
    315312}}}
    316  1. ''Performing this step is to acknowledge that the merge has been performed.'' [[br]]
    317     Close the milestone associated with the release and replace `head` with appropriate
    318     revision in log link. Add a new milestone as needed (with an associated log link like
    319     ''Revision Log: log:branches/webservices@3001:head'' in the description field). [[br]][[br]]
    320  1. [mailto:basedb-users@lists.sourceforge.net,basedb-devel@lists.sourceforge.net,basedb-announce@lists.sourceforge.net Announce] the new release in the mailing list.