2 ms·
Does anyone have any references / recommendations along the vein of "guide to branch strategies" for certain development methodologies? For example: working in
by neogodless 8y ago
Does anyone have any references / recommendations along the vein of "guide to branch strategies" for certain development methodologies? For example: working in sprints / AGILE, branches for testing/QA/user-acceptance environments, etc?
(While I would hope the answers to this question would be widely useful, I mostly work on C# applications, with less focus on JavaScript-based applications. Maybe that's relevant for deciding on strategy - hopefully not!)
- alkonaut 8y agoI'd argue that language is less important than product/deployment type. The difference between releasing e.g. a desktop product on a yearly schedule with maintenance fixes going both to the 2018 and earlier main releases, versus building a web service with a single deployed version deployed perhaps several times per day is rather big when it comes to a branching strategy.
- WorldMaker 8y agoThe most commonly referenced references to read can be found by searching for GitFlow (heavier) and GitHubFlow (lighter). Personally, I recommend the GitHubFlow and CI/CD for "agile", and never branching per-environment but there are almost as many opinions as there are developers.