Has anyone counted the number of commits between 0.4.6 and 0.4.7 that this would have applied to, in order to gauge the amount and feasibility of the additional work?
By feasibility, I mean, if the commits come after the transition to C++11, or some other significant refactoring, then adding them to the release branch is not as simple as a cherry pick.
I don't know that we agreed on a scope of issues to even try counting. The very limited scope that I was envisioning was something that I would expect to be in the small handful range. I don't think we should have any blanket commitment for bugfixes, and could just consider them as they come up, with respect to severity of bug and if the fix can be cherry picked or easily adapted.
And at this point I don't think there is any point talking about a bug-fix release for 0.4.6; either 0.4.7 can fill that need or they can do without. (Though perhaps you simply mention that to illustrate how such bug fixes might be a major headache?)