3 ms·
> In my experience, git tags are far more effective at managing releases than git branches. I'm sorry to say that your experience doesn't seem to be with produ
by rewmie 3y ago
> In my experience, git tags are far more effective at managing releases than git branches.
I'm sorry to say that your experience doesn't seem to be with production software with a significant release cadence. Tags fail very basic requirements of any release process. A release requires release-specific changes such as bumping version numbers, toggling configurations and feature flags, update changelogs and documentation, and more importantly accommodate bugfixes without having to merge in unrelated work on features actively under development that are not intended to ship.
Tags are only good to point to specific commits. Unless you're working on a pet project or you're the single developer working on software no one uses, a release is way more than pointing to a random commit in the development branch.
- WorldMaker 3y agoYou don't know my experience and making assertions about what you don't know here verges on an ad hominem attack. Please rethink your approach. I never said tags come only from a single development branch, I said that release branches are best when short-lived and that tags are a better long-term representation of released versions than long-running release branches. If you want to discuss the complexities of the differences in workflow that entails, feel free to ask questions without assuming you have any idea what my experience level is.