Any thoughts on branches in terms of development? All for proper feature branching/merging. In the past, I’ve kept master in sync with .org’s SVN to avoid confusion for folks that stumble across the project for google, etc., and did most of the work in a `develop` branch, but up for others’ expertise. Thoughts?
Post Forking 
Daniel Bachhuber 11:13 am on October 1, 2012 Permalink
I used to follow the master/develop approach but then decided it wasn’t offering much value, was a pain to maintain, and made things painful when users wanted to submit pull requests
Benjamin J. Balter 11:19 am on October 1, 2012 Permalink
Makes sense. I can add a note to the documentation, and we should treat SVN as stable and master as develop?
Daniel Bachhuber 11:22 am on October 1, 2012 Permalink
Sure, that works for me.