Our dev process includes edge/snapshot code being kept in the develop branch until release time. I like this process because it allows us to keep master clean and stable. So imagine that we have a major bug fix. To get this to users we could do a release but this can’t happen soon enough if a user has discovered it and already needs the fix. We could point to a commit in develop but that branch is a little wild until release time.
I’d like to propose we allow some commits to master, to fix critical bugs, and tag these with the Jira # describing the bug. The fix would also go in develop so at merge time there would be nothing to merge. At present we have a source only release so this would work fairly well, even with a binary release it would be safer and easier to document than suggesting a build of the develop branch. Opinions? If no one objects there was a critical bug fixed recently and I’ll do the above to get the fix in master.
