I think just using the branching scheme? For most people it would just boil
down to that themain branch is called develop and that pull requests are
made against that one, right? And if we do manage to do official releases we
would know how to handle that in terms of branches.
From: PythonDotNe
I have found git-flow to be a good starting point for building a workflow.
Cases it doesn't cover or parts of it that cause problems for the
contributors of this project may be discovered, at which point
deviation/modification should be considered.
Are you suggesting using the gitflow project [
ht
Oh yes, this would really only be feasible once things are on github, still
thought we might start talking about it now and get people's opinion on how
they would want things to be.
I think the brunt of the migration to github is done (fingers crossed) and
it is more about a decision at this point