v1.20150222 doesn't seem to include recent changes

[msimerson]

v1.20150222 doesn't seem to include recent changes

[msimerson]

Hmm, I'm aware that change is not in that release, because I didn't merge it until after the release. The fact that it snuck into Changes is slightly surprising to me, but I expect some human error is to blame.

[msimerson]

PS: I'll roll another release soon, I don't think this change is in that release either "missing scope in SPF auth results," and there's another one that's not quite a PR yet.

[rjbs]

Weird. You say you didn't merge it until after the release, but the "v1.20150222" commit is on 38ad62d, which is the great-grandchild of 13a119c, which includes the merge. The intervening commit is the one that updates the changelog. I have nothing more than "weird," I guess. I look forward to the next release!

[msimerson]

Well, I do believe they were committed on the same day, but not necessarily on the same computer, so while the changes were time-linear, the order replayed in the public repo isn't necessarily.