Description / Mention of Longer lived branch workflow

[brntbeer]

I've taught a few people a version of the GitHub flow that uses longer lived branches, wondering if there's a place in the workflow section of Advanced for us to describe this?

This is also the workflow that we'll be using for this repo moving forward i believe.

[matthewmccullough]

Some of the largest teams and firms moving to GitHub will want to make a horizontal transition to keep their long lived branch processes in place, but give them a slight GitHub flavor. Hopefully, over time, we can convince them to shorten those cycles. But this is great bridge between their world and the GitHub world and serves a real need. Do you think this might tee up for after bolstering the Subversion migration sections of the curriculum though?

[brntbeer]

i think this could be helpful for SVN people, but i don't think they are mutually exclusive

[matthewmccullough]

Do you think this might tee up for after bolstering the Subversion migration sections of the curriculum though?

i think this could be helpful for SVN people, but i don't think they are mutually exclusive

Agreed. 😄 Just wondering based on JavaOne feedback, which one might be more impactful to take on first, vs. second. 👍

[crichID]

@brntbeer this issue is super stale. I have added this to the backlog in the training repo and will close this out. If you would like it re-opened, please feel free to do so!