Test `next` branch - from stable v0.1.0

[powerlevel9k]

Test `next` branch - from stable v0.1.0

[natemccurdy]

Sounds like a plan. I'll start using the next branch and checking for bugs.

[bhilburn]

Thanks so much, @natemccurdy! I really appreciate it =)

[dritter]

@bhilburn I'm in! :)

Btw. do you work with git flow?

[bhilburn]

@dritter - Great! Are you talking about the branching model?

https://datasift.github.io/gitflow/IntroducingGitFlow.html

[dritter]

@bhilburn Right. What you described sounded much like it.. So maybe switching directly to it may benefit us..

[bhilburn]

@dritter - Yup, I'm familiar with it. The master + maint + next model is effectively the same thing, but was around before git flow, and so has different names. It's used by a number of other FOSS projects I'm involved in, and so I just naturally started using it here. The only real difference is that the release branch for the latest release is called maint, and develop is called next.

Otherwise, we are already basically doing it. Once we tag our next release and I merge & re-set the next branch, I'll rename them to adhere to this model. You're right, it's more widely known that the naming scheme I used above =)

I'm not sure we need 'release branches', just yet. I don't know that our current level of complexity warrants it. If we decide we need it, I'll create it at the next tag.

Great idea, @dritter!