@dallo
It was a nice diagram, but poor workflow even in 2010. The gitworkflows(7) man page was first written in 2008 and had clear rationale. I made this figure in that era to show the parallelism exposed by the workflow. As CI has become more robust, many projects moved away from having a 'next' as a throw-away integration branch, but it is a useful strategy especially if you want user feedback on experimental features before you commit to including them by merging to 'main' (formerly 'master').
https://git-scm.com/docs/gitworkflows
@dazfuller

@dazfuller
And this is the figure from the 2010 blog post that their machine plagiarized (badly).
https://nvie.com/posts/a-successful-git-branching-model/

RE: https://mastodon.social/@jwz/116078186911677336

Every week another "AI" booster rushes out: "I started taking amphetamines three times a day and now I'm the next Paul Erdős!"

And invariably within days or weeks, we find them walking dazed across traffic, car doors open in the middle of the intersection with a baby inside, to scratch a proof on a lightpole. The proof is always wrong.