Changes between Version 5 and Version 6 of StartModWorkflow


Ignore:
Timestamp:
Dec 10, 2013, 2:45:35 PM (9 years ago)
Author:
Beman Dawes
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • StartModWorkflow

    v5 v6  
    1 = Modular Boost Library Workflow Overview =
     1=  * [wiki:StartModWorkflow Modular Boost Library Workflow Overview]
     2 =
    23[[PageOutline]]
    34
    45Workflow is the term used to describe the steps a Boost library developer follows to create and maintain a library.
    56 
    6 The workflow model Boost recommends is nowadays called '''Git Flow'''. It was introduced as a simple [http://nvie.com/posts/a-successful-git-branching-model/ blog posting] by Vincent Driessen on January 5th, 2010, that went viral and has become a de facto standard software engineering practice.
     7The workflow model Boost recommends is nowadays called '''Git Flow'''. It was introduced as a simple [http://nvie.com/posts/a-successful-git-branching-model/ blog posting] by Vincent Driessen on January 5th, 2010, that went viral and has become a widely used software engineering practice.
    78
    8 This workflow has arguably become so successful because it scales really well, and that's one of the reasons it is recommended for Boost libraries.
     9This workflow has arguably become so successful because it scales well from very small to very large projects, and that's one of the reasons it is recommended (but not required) for Boost libraries.
    910
    1011 * An unusually simple, single developer library would have only the permanent **develop** and **master** branches that are required for all Boost libraries.
    … …  
    1819== Aside: Deleting merged branches ==
    1920
    20 The usual culture with Git is to delete feature branch references as soon as
     21The usual culture with Git is to delete feature branches as soon as
    2122they are merged to some other branch.
    2223This approach is also recommended for Boost developers.