Erik,
Hopefully those that read what I said, know what I am talking about.
It sounded like there would be "shepherding" during this period and
all I was saying was Om, etc basically did all this off the cuff.
Kudos to them, they know we all appreciate it.
Mike
Quoting Erik de Bruin <e...@ixsoftware.nl>:
Well, while I generally agree with your sentiment, we wouldn't do
justice to Om. He's gone above and beyond with Infra and I think his
calm and political sense have made this possible. Also, I think Fred,
Dasa and Jose did their fair share making sense of the inner workings
of git in relation to this project.
That's not to say that I'm very disappointed with some of the very
vocal voters (PMC and contributors) who have been entirely absent
during the implementation:
http://markmail.org/message/ajlskznzec4wqda2
Merit works both ways, IMHO.
EdB
On Fri, Mar 22, 2013 at 4:55 PM, Michael Schmalle
<apa...@teotigraphix.com> wrote:
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
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
