Versioned software release branching for large teams with less frequent releases, Modelling the versioned software approach
It adds significant process overhead that may not be worth it for teams with frequent releases or simple projects.
Teams needing frequent releases where the release branch model adds overhead and merge conflicts
Reviews from businesses like yours — matched by size and type. Available once you create a profile.
Complete profileRelated Tools
Community Reviews
Reviews from Reddit, Product Hunt, Hacker News & AlignAI members
In [one] case, after finding an exploit to edit files for which it lacked permissions, the model made further interventions to make sure that any changes it made this way would not appear in the change history on git.
Hacker News • HackerNews • Use case: Version control and change history tracking
git for source code and bug tracking... it's all a mess, when you can use something like fossil.
Hacker News • HackerNews • Use case: source code and bug tracking
The issue is 100% Git... ooh look it runs Git, so can we apply the ol’ fsmonitor chestnut there?
Hacker News • HackerNews • Use case: Version control, specifically its fsmonitor feature
My experience has exposed me to a wide range of technologies, tools, and methodologies, and has allowed me to collaborate with professionals from diverse backgrounds.
Hacker News • HackerNews • Use case: Version control and collaboration
Not that that works well with git of course, I just can manage to actually design stuff.
Hacker News • HackerNews • Use case: Version control for CAD files
GitFlow seemed to be better aligned with modelling the versioned software approach... but Git Flow's release branching model added overhead - people might forget to merge back to develop, deal with conflicts or semantic brokenness.
Hacker News • HackerNews • Use case: Versioned software release branching model for a large team with less frequent releases
Have You Used This Tool?
Sign in to share your experience with this tool.
Sign in