Yep, that's what I did with Catch. you change the default branch in github to develop and people will be put on the develop branch when they clone.

On Wed, Jun 8, 2011 at 21:56, Brian Leathem <bleathem@gmail.com> wrote:
I had a question regarding the default branch that people clone.  If we map "release" to "master" as one of the articles recommends, and create a 2nd branch called "develop" then we want to make sure people fork off of develop when they want to add a feature.

I think you said the default branch was a configurable option in github.  Is that how you approached this with Catch? 

I'm really hoping Faces will end up with many contributors, so this has to be easy for them to pick up.

Brian Leathem


On 06/06/2011 05:30 PM, Jason Porter wrote:
Who has questions about Git Flow? Aside from sending out the same links I've sent out in the past, I want to answer your questions about it before we officially adopt the workflow for all seam modules.

--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
_______________________________________________ seam-dev mailing list


_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev




--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu