Thank you for sharing. Even thou I have a lot fewer projects and majority of my work happens on the projects of clients - I managed to take away some useful ideas and tips. Specifically using "issue" as a place where everything gets tied together and combining all aspects of a feature into a single main-branch commit is something I will try to do more from now on.
Since your workflow is so GitHub centered, one place that IMO could use more structuring is GitHub issue labels   . Defaults are quite ad-hoc, with color not really representing anything. And setting up new default labels for new projects can be automated with command line scripts.Reply
Hey Simon, as you mentioned Github and I regard you as one of the biggest SQLite hackers on the interwebz, I was wondering if you've tried Fossil?
Might be nice to hack around with, especially combined with its CGI extension feature.Reply
I was hoping this would discuss how he chooses which features to build. Unfortunately, that is not what this is.
It is a description of a pretty rigorous development workflow, but I think it will mostly only be useful to people who want to contribute code to Simon's projects.Reply