@zach for addons that break with these upgrades there are two obvious ways to deal with that,
1. have a branch per version and possibly a tag for each release or
2. use preprocessor guards, eg.
#if (OF_VERSION_MAJOR == 0) && (OF_VERSION_MINOR < 9)Any thought on best practices here?
I can see benefits with both. Eg. it is easier to just work in one branch and be able to ignore other oF versions, but at the same time, I often need to work in different oF versions and keep developing addons to be used with both. I feel using option 1 runs the risk of branches becoming an addon graveyard where old addons receive no love. Often that is ok as you probably wont need / expect new features from an addon in an old project, but bug fixes and updates due to say xcode changes risk getting lost.
Also master and develop branch names don't really communicate dependencies for oF version very well.
