Okay, now that we've officially released something, we need to figure out how to handle public git branches.
The new hotness in git workflows seems to be this: http://nvie.com/posts/a-successful-git-branching-model/ In this approach, "master" is the *production* branch (only changed when you have a formal release, and "develop" is the *integration* branch (where code is integrated in). I would have called production something else ("production"?), but I can't say it's a big deal. I'm really just looking for a model that: 1. Works well 2. Is easy to understand/explain 3. Is what many other people are doing - I don't want a workflow that impedes others from participating. Any thoughts on this one? Good? Bad? Run away? --- David A. Wheeler ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
