Those who don't have the links: http://nvie.com/posts/a-successful-git-branching-model/ - Explanation of the workflow http://nvie.com/posts/a-git-flow-screencast/ - Screencast showing it in action http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ - Usage of the workflow in blog post form https://github.com/nvie/gitflow - Repo of the git flow extension, also contains wiki pages about it. On Mon, Jun 6, 2011 at 18:30, Jason Porter <lightguard.jp(a)gmail.com&gt; 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 -- 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Hello, I have four questions: 1) Are we following the default naming standard ?

2) When are we going to adopt it ?

3) Which projects will be using it in first place ?

4) How do I install it on Windows ? :) Regards, George Gastaldi 2011/6/6 Jason Porter <lightguard.jp(a)gmail.com&gt;: > Those who don't have the links: > > http://nvie.com/posts/a-successful-git-branching-model/ - Explanation of the > workflow > http://nvie.com/posts/a-git-flow-screencast/ - Screencast showing it in > action > http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ - Usage of > the workflow in blog post form > https://github.com/nvie/gitflow - Repo of the git flow extension, also > contains wiki pages about it. > > On Mon, Jun 6, 2011 at 18:30, Jason Porter <lightguard.jp(a)gmail.com&gt; 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 > > > > -- > 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > >

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 <http://keyserver.net>;, pgp.mit.edu <http://pgp.mit.edu> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

------------------------------------------------------------------------ Jason Porter <mailto:lightguard.jp@gmail.com> Thursday, June 09, 2011 6:14 AM 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. -- 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 <http://keyserver.net>;, pgp.mit.edu <http://pgp.mit.edu> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev ------------------------------------------------------------------------ Brian Leathem <mailto:bleathem@gmail.com> Thursday, June 09, 2011 5:56 AM 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 _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev ------------------------------------------------------------------------ Jason Porter <mailto:lightguard.jp@gmail.com> Tuesday, June 07, 2011 2:30 AM 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 <http://keyserver.net>;, pgp.mit.edu <http://pgp.mit.edu> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev