Dev Protocol

[caycefischer]

This will go into the readme when I get around to re-writing it

cc @jhogue @grayghostvisuals

OK so we're gearing up for version 1.1.0, and we need to sort out how to organize ourselves as we write new code. I suggest what we do over at HabitRPG, which is everybody Pull Requests from a feature branch.

• Nobody should push directly to master
• Branch off of master to write a feature
• when you're ready to merge it in, do a Pull Request that you can just resolve yourself

This keeps a clean record of what we do and is more stable.

[grayghostvisuals]

I think before we get ahead of ourselves we should really think this one through. My suggestion ATM is to keep the development branch and then branch our features from development. This way when we are ready to ship new versions/updates we can push to Master for Releases. Thoughts? Maybe we can research some other methods some more. I believe github usually goes the "push everything to master" route.

[caycefischer]

That makes sense, its another insulating layer between master and new code

– Zachary Kain

Designer, Developer Writer, Educator 416-712-8895 zakkain@gmail.com ➝ http://draftingcode.com

On Sat, Apr 13, 2013 at 12:22 PM, Dennis Gaebel notifications@github.comwrote:

I think before we get ahead of ourselves we should really think this one through. My suggestion ATM is to keep the development branch and then branch our features from development. This way when we are ready to ship new versions/updates we can push to Master for Releases. Thoughts? Maybe we can research some other methods some more. I believe github usually goes the "push everything to master" route.

— Reply to this email directly or view it on GitHubhttps://github.com/typeplate/typeplate.github.com/issues/98#issuecomment-16335950 .

[grayghostvisuals]

Does that mean you like? Please say you do or else I will cry!

[caycefischer]

:ok_hand:

[grayghostvisuals]

See ya Issue! wouldn't wanna be you.