branching_policy - jibedoubleve/lanceur-bis GitHub Wiki

Branching Policy

This project follows a structured branching strategy to organise development and releases clearly and efficiently.

  1. Development Branch: master

    The master branch reflects the current state of ongoing development. It includes the latest changes being prepared for future releases.

    Example: If development for version 1.3.0 is underway, the corresponding work is done directly in the master branch.

  2. Release Tagging

    The latest stable production release is identified using Git tags in the format x.x.x. These tags represent the exact code that is running in production.

    Example: After releasing version 1.2.0 to production, a 1.2.0 tag is applied to the commit corresponding to that version.

  3. Pre-Release Coordination Branch: develop

    When development is split between a nearly finished version and a future one, a develop branch is created to isolate final work on the upcoming release. This branch is tagged with the version to be released and used by GitVersion to manage versioning appropriately.

    Example: While version 1.3.0 is being worked on in master, the develop branch may hold the final adjustments for version 1.2.0, tagged as 1.2.0.

Would you like this formatted as a markdown file or documentation snippet?