<link href="https://cdnjs.cloudflare.com/ajax/libs/gitgraph.js/1.11.4/gitgraph.css" rel="stylesheet">

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no, minimal-ui">

<p style="margin: 20px"></p>

<canvas id="gitGraph" style="padding: 20px"></canvas>

<script src="https://cdnjs.cloudflare.com/ajax/libs/gitgraph.js/1.11.4/gitgraph.js"></script>

<script src="gitFlowDevModel.js"></script>

<p style="page-break-before: always">

<h2> Notes</h2>

<li>Feature branches branch off of

<b><i>develop</i></b>

& merge back into

<b><i>develop</i></b>

</li>

<li>Release branches branch off of

<b><i>develop</i></b>

& merge back into

<b><i>develop</i></b> and

<b><i>master</i></b>

</li>

<li>Hotfix branches off of

<b><i>master</i></b>

& after critical bug fixes merge back into

<b><i>develop</i></b> and

<b><i>master</i></b>

</li>

<h2> Pros</h2>

<li>Git flow model used by open source projects and other firms.</li>

<li>Has been trending well last few years.</li>

<li>origin/master would be the main branch where the source code of HEAD always reflects a production-ready state.</li>

<li>origin/develop would be the main branch where source code of HEAD always reflects a state with latest delivered development changes for next release. aka “integration branch” or "nightly build branch"</li>

<h2> Cons</h2>

<li>Requires more effort since it involves maintaining more branches and merges may not be smooth.</li>

<li>Might be overkill if code base does not change often or less available resources.</li>

<li>Might be problematic if release cycles are long and same mature code base is changed/refactored extensively between releases along with personnel turnover.</li>

<button onclick="myFunction()">Print</button>

function myFunction() {

window.print();