Changes between Version 44 and Version 45 of ReleaseProcedure


Ignore:
Timestamp:
Feb 9, 2009, 1:00:41 AM (12 years ago)
Author:
Peter
Comment:

moved version.m4 to m4/ in r1785

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v44 v45  
    5050}}}
    5151 1. Prepare the trunk for the next minor release [[br]][[br]]
    52   i. Update version number in `build_support/version.m4`. Locate and change the
     52  i. Update version number in `m4/version.m4`. Locate and change the
    5353     below line
    5454{{{
     
    7979    files `NEWS` and `ChangeLog`.
    8080    [[br]][[br]]
    81   i. Update version number in `build_support/version.m4`. Locate and change the
     81  i. Update version number in `m4/version.m4`. Locate and change the
    8282     below line
    8383{{{
    8484m4_define([DEV_BUILD], [false])
    8585}}}
    86   i. Update the interface version number in `build_support/version.m4`. Locate and set the version in the
     86  i. Update the interface version number in `m4/version.m4`. Locate and set the version in the
    8787     below line
    8888{{{
     
    9191m4_define([YAT_LT_AGE], [a])
    9292}}}
    93      appropriately. Refer to the interface version list in `build_support/version.m4` to figure out the settings of c, r, and a. c should increase with 1 if the interface has changed. If the interface is changed, r should be set to zero and a should be set to reflect backward compatibility level of this version. If interface was not changed just increase r with 1. See `build_support/version.m4` and the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
     93     appropriately. Refer to the interface version list in `m4/version.m4` to figure out the settings of c, r, and a. c should increase with 1 if the interface has changed. If the interface is changed, r should be set to zero and a should be set to reflect backward compatibility level of this version. If interface was not changed just increase r with 1. See `m4/version.m4` and the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
    9494  i. Update `THANKS`. Remember, ego and vanity is the currency of open
    9595     source projects. Well, there are other reasons for open source
     
    138138}}}
    139139 1. Prepare the minor branch for the first patch release [[br]][[br]]
    140   i. Update version number in `build_support/version.m4`. Locate and change the
     140  i. Update version number in `m4/version.m4`. Locate and change the
    141141     below lines
    142142{{{
     
    209209  i. Resolve all conflicts. Run tests and perform all other
    210210     appropriate tests to make sure that the merge does not create
    211      havoc. Typically changes in `build_support/version.m4` are problematic
     211     havoc. Typically changes in `m4/version.m4` are problematic
    212212     so check this file extra carefully.[[br]][[br]]
    213213  i. Commit changes to the trunk branch.
     
    226226    contributions (`THANKS`), update files `NEWS` and
    227227    `ChangeLog`. [[br]][[br]]
    228   i. Update the release version number in `build_support/version.m4`. Locate and change the
     228  i. Update the release version number in `m4/version.m4`. Locate and change the
    229229     below line
    230230{{{
     
    278278}}}
    279279 1. Prepare the minor branch for the next patch release [[br]][[br]]
    280   i. Update version number in `build_support/version.m4`. Locate and change the
     280  i. Update version number in `m4/version.m4`. Locate and change the
    281281     below lines
    282282{{{
     
    284284m4_define([DEV_BUILD], [true])
    285285}}}
    286   i. Update the interface version number in `build_support/version.m4`. Locate and change the
     286  i. Update the interface version number in `m4/version.m4`. Locate and change the
    287287     below line
    288288{{{
     
    350350  i. Resolve all conflicts. Run tests and perform all other
    351351     appropriate tests to make sure that the merge does not create
    352      havoc. Typically changes in `build_support/version.m4` are problematic
     352     havoc. Typically changes in `m4/version.m4` are problematic
    353353     so check this file extra carefully.[[br]][[br]]
    354354  i. Commit changes to the trunk branch.