Changes between Version 2 and Version 3 of StartModWorkflow


Ignore:
Timestamp:
Dec 10, 2012, 4:18:33 PM (10 years ago)
Author:
Beman Dawes
Comment:

Add git-flow tools mention

Legend:

Unmodified
Added
Removed
Modified
  • StartModWorkflow

    v2 v3  
    22
    33Workflow is the term used to describe the steps a Boost library developer follows to create and maintain a library.
     4 
     5The 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 quickly become a de facto standard software engineering practice.
    46
    5 The workflow model Boost recommends is nowadays called !GitFlow. 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 quickly become a de facto standard software engineering practice.
    6 
    7 This workflow has probably become so successful because it scales so well, and that's one of the reasons it is recommended for Boost libraries.
     7This workflow has arguably become so successful because it scales really well, and that's one of the reasons it is recommended for Boost libraries.
    88
    99 * An unusually simple, single developer library would have only the permanent **develop** and **master** branches that are required for all Boost libraries.
    10  * A more typical library would occasionally add temporary feature branches, either private or public.
     10 * A more typical library would occasionally add temporary feature branches, either private or public. Feature branch names follow the {{{feature/x}}} model, where {{{x}}} names the specific feature being developed.
    1111 * A larger library, particularly if it has multiple developers, would always have some active public feature branches, and at least occasionally employ release staging branches and hotfix branches. Individual developers would often use private branches.
    1212
    13 The !GitFlow model diagram is available as a [http://github.com/downloads/nvie/gitflow/Git-branching-model.pdf PDF file] - print it out and hang it on your wall! 
     13The Git Flow model diagram is available as a [http://github.com/downloads/nvie/gitflow/Git-branching-model.pdf PDF file] - print it out and hang it on your wall!
     14
     15For those who use Git from the command line, [https://github.com/nvie/gitflow git-flow command line tools] are available to automate common operations. See [https://github.com/nvie/gitflow/wiki git-flow wiki] for more information.