Changes between Version 11 and Version 12 of SuperProjectWorkflow


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

Michael Cox suggested creating a maintenance branch.

Legend:

Unmodified
Added
Removed
Modified

  • SuperProjectWorkflow

    v11 v12  
    5656* Would release management and regression testing scripts be simpler if the name of the release development branch was fixed (e.g. "release") rather than varying (e.g. "release/1.56.0")?
    5757* Are new libraries that might not be ready for release added to both "develop" and "latest", or just to "latest"?
    58 
     58* Should we create a maintenance branch after releasing? Or just do everything on the super-project's "master" (simpler but limits making changes once the next release is in progress).
    5959
    6060== Naming rationale ==