Continuing from #2009...
New fixes in master since previous list (@gavinandresen Are these OK to backport now as well?):
@Diapolo 6b3783a does change strings, but only the English in them, not the meaning, so the old translations are direct 1:1 mapping.
@gavinandresen If the NACKs are debatable (if not, just say so), I'd like to clarify whether the memset one is a (minor) security fix or not?
Those two are fine.
memset change is too many lines of code changes for essentially zero net security benefit (if the attacker can read your bitcoin process' memory then you're already toast).
Diff to v0.7.1: https://raw.github.com/gist/4090863/715fbe48576dbce157071333f86a138ba34f022b/stdin.txt
#2022 looks like a good idea to throw into this too.
@luke-jr 6b3783a Is fine with me then, your explanation did it's job ;). Just wondering, if the legacy translations will still be used then? I have new translation files ready in another pull now btw.
@Diapolo Gavin NACK'd 6b3783a anyway, so it won't be in 0.7.2. Maybe 0.7.3 :) I've pulled in translations of strings that were missing for 0.7.1, if that's what you mean by the second part.
Revised diff with 0.7.1: https://raw.github.com/gist/4094412/a0a1ca844b60a7e54387c7c637791915238cde70/stdin.txt
Should we wait for #1927?
@luke-jr I would vote no, as this is just a small glitch but not really a heavy UX problem IMHO. I would much more love to see #2024 get in 0.7.2.
Agreed with Diapolo. #2024 is a fix for a boost issue which makes boost::path unsafe to use in global constuctors on windows. This can cause a crash at shutdown. #1927 is 'nice to have' category but no need to wait for it.
Backported #2024, added release notes (+ bumped versions), and tagged v0.7.2rc1.
ACK on the diff between v0.7.1 and 0dba651 (v0.7.2rc1). I can't build myself right now, unfortunately.
I didn't look at the changed translations closely.
v0.7.1..v0.7.2rc1 diff: https://raw.github.com/gist/4133508/fd3d389097d24040d929bebd0435fcd21eb7f185/stdin.txt
v0.7.2rc2 is tagged, if anyone else can contribute gitian builds...
tagged at gitorious?
It is confusing and error-prone to be using github for issues and major releases, but gitorious for a seemingly random collection of stuff.