new-freebsd-version

You can use a FreeBSD-inspired branching policy to manage release branches by enforcing hyphenated naming conventions, which avoids invalid characters for Docker and DNS environments while structuring stable, releng, and tag workflows.

The FreeBSD branching model defines a structured workflow using main, stable-X, releng-X-Y, and MFH branches to separate feature development, stabilization, and release preparation, ensuring predictable versioning and tagging across the project lifecycle.

To create a stable release, follow a multi-step workflow from the main branch: create the stable-X branch, update the version in composer.json, apply MFH flow rules, and complete a final confirmation step before pushing the tag.

Yes, the branching policy includes optional instructions for version handling within composer.json, allowing you to automate or guide version bumps during the stable, releng, and tagging steps of the release workflow.

Branch names must avoid dots and slashes because spawn, DNS, and Docker environments treat these characters as path separators or domain delimiters, which breaks deployment resolution and requires hyphenated naming conventions instead.

The workflow requires strict adherence to its specific branch naming conventions and multi-step release sequences, meaning projects with existing flexible branching strategies may need significant adjustment to enforce the stable, releng, and MFH patterns.