4.4.10 branch

going into pre-release freeze without being able to use a branch to continue on turned out to be incredibly costly. I was trying to get stuck into fixing bugs in 4.4 & master that relied on other fixes (particularly to tests) and queuing them up as separate PRs I couldn't keep them clean and also get the tests to pass. 

Since I don't have the option of branching 4.4 on the CiviCRM core repo when it goes into pre-release freeze my plan is to continue the 'trunk' of 4.4 in my own repo  during pre-release freeze (pushing & testing) & hit merge as soon as it is over