Changes between Version 9 and Version 10 of SuperProjectWorkflow


Ignore:
Timestamp:
Jan 18, 2014, 4:38:45 PM (9 years ago)
Author:
Daniel James
Comment:

Some notes on things that need to be done to prepare the release branch.

Legend:

Unmodified
Added
Removed
Modified

  • SuperProjectWorkflow

    v9 v10  
    2828=== Release preparation ===
    2929
    30 The release preparation branch follows the Git Flow model. It is branched from "develop" and merged with "release" once complete.
     30The release preparation branch follows the Git Flow model. It is branched from "develop" and merged with "release" once complete. If a module isn't considered ready for release (such as a new library that hasn't been fully approved) it may be reverted to an earlier version. The appropriate files are updated for the release, such as 'index.html'. It might also be necessary to update `<boost/version.hpp>` in Boost.Config.
    3131
    3232When a submodule does a release, the super-project's "develop" for the submodule is updated to the new version, and merged (without committing) to the release branch. Release management scripts then run local tests.