Changes between Version 60 and Version 61 of ReleaseProcedure


Ignore:
Timestamp:
Oct 31, 2011, 5:27:43 AM (10 years ago)
Author:
Peter
Comment:

don;t mention THANKS in RP as we have no such file (yet)

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v60 v61  
    9393
    9494 1. Make sure that all commits are performed into the minor branch, such
    95     as bumping version number(s) (`version.m4`),
    96     acknowledge contributions (`THANKS`), update
    97     `NEWS`.
     95    as bumping version number(s) (`version.m4`), update `NEWS`.
    9896    [[br]][[br]]
    9997  i. Update version number in `m4/version.m4`. Locate and change the
     
    115113     `m4/version.m4` and the
    116114     [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
    117   i. Update `THANKS`. Remember, ego and vanity is the currency of open
    118      source projects. Well, there are other reasons for open source
    119      projects but `THANKS` is for boosting people's ego. [[br]][[br]]
    120115  i. Set the date for the new release in `NEWS`.
    121116{{{
     
    222217
    223218 1. Make sure that all commits are performed into to the branch, such
    224     as bumping version number(s) (`configure.ac`), acknowledge
    225     contributions (`THANKS`), update `NEWS`. [[br]][[br]]
     219    as bumping version number(s) (`configure.ac`), update `NEWS`. [[br]][[br]]
    226220  i. Update the release version number in `m4/version.m4`. Locate and change the
    227221     below line
     
    230224}}}
    231225     Confirm `YAT_LT_VERSION_INFO` and add an entry in list of versions.[[br]][[br]]
    232   i. Update `THANKS`. [[br]][[br]]
    233226  i. Set the date for the new release in `NEWS`
    234227{{{