Changeset 30602 in project


Ignore:
Timestamp:
03/25/14 12:27:26 (7 years ago)
Author:
Moritz Heidkamp
Message:

release-policy: clarify wording around tagging (tags are not pushed into branches, really)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/release-policy

    r26919 r30602  
    1212# In more or less regular intervals, the patch-level of the release
    1313number will be increased (for example "4.5.0" -> "4.5.1") and a tag
    14 identical to the release number will be pushed into "master". Once
     14identical to the release number will be made on {{master}}. Once
    1515tagged, a development snapshot is automatically generated and placed
    1616in [[http://code.call-cc.org/dev-snapshots|dev-snapshots]]. Usually,
     
    2424# If enough changes for a regular release have accumulated in the
    2525{{master}} branch, it is merged into the {{prerelease}} branch and
    26 from there into the {{release}} branch. A tag pushed into the
     26from there into the {{release}} branch. A tag made on the
    2727{{release}} branch will trigger automatic generation of a release
    2828tarball.
Note: See TracChangeset for help on using the changeset viewer.