Or... I could just leave the branch there... Can you imagine trying to track the history of bugfixes for a release product if you're deleting the branch each time and just going off merges into master. Holy mary mother of god that sounds scary.
The tag tracks that history. Trust me, it's no problem at all.
BTW, I feel like you're resorting to "I'm no worse than GitFlow", but I've never used GitFlow so that's not compelling for me :/
I can just say, "Lucky you" :). I like to think my workflow is superior to GitFlow in every way - I'm not sure how I implied I'm merely no worse, that wasn't my intention.
dev ---> dev ------> merge --> dev ---------->
\-- 1.0 ---> {tag} --/ /
\---- 1.1 ---> {tag} --/ /
\ /
\---------> 1.2 ---> {tag} --- /
vs.
dev ---> dev ------> merge --> dev --------------------->
\-- 1.0 ------ / --- commit -- / -- commit bugfix -- /
i think what he means is the second one, having a linear branch is far easier to understand and use than having tags and re-creating branches etc.
if i can chime in, if you are developing an application (like an ios application etc) and need to bump version everytime it completely make sense, tags are like snapshots you cant change it, and when you release your software, you cant update without releasing a new version.
on the other hand, if you are building applications on the server side or (maybe web frontend), and deploy a dozen of times everyday, its a nightmare to tag and rebranch.
Sorry, I have no idea what that second drawing means.
If you are deploying several times a day, I would imagine you do it straight from the mainline, and you don't bother with tagging your releases. If that's true, then you also for sure don't bother with separate branches for each release, so I'm not sure what you're arguing here.
And I don't know what you mean by "rebranching". Like I said, you only have one eternal branch in your repo with this workflow. There's no "rebranching".
0
u/[deleted] Jun 19 '15
[deleted]