Well...
Being down right blunt, this model was voted on by PMC members that
don't even contribute to the project anymore (if ever).
All the people that voted for GIT int he first place have hardly show
there face once, now that it has happened.
I think this calls for an ability to revise what was voted on since us
commiters (PMC members) that are actually doing work with this stuff
right now have problems with it.
Gordon, I agree, for Falcon repo development that model is huge over kill.
The vote happened when I was away for 8 months.
Mike
Quoting Gordon Smith <gosm...@adobe.com>:
I plan to do my Falcon development work on the 'develop' branch. The
full nvie model is complete overkill for what I am doing and I don't
need umpteen feature branches. Has everyone forgotten about KISS?
- Gordon
Sent from my iPad
On Mar 22, 2013, at 3:37 AM, "Justin Mclean"
<jus...@classsoftware.com> wrote:
Hi,
Also anyone want to explain why this doesn't mention pull -rebase anywhere?
http://nvie.com/posts/a-successful-git-branching-model/
Also on the bug fix issue to branch or not branch (from the author
of gitflow):
"A rule of thumb would be that if you need more than one commit for
a change, you should do it on a feature branch, otherwise commit it
directly on develop."
https://github.com/nvie/gitflow/issues/24
Thanks
Justin
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
