Publish a new release

[jerryzj]

Hi there,
It seems that we have more than 20 commits after the 0.31 release.
Would you mind drafting a new one?
Thanks.

[sevaa]

I was rather hoping #530 would land soon. Also, I'm having doubts if #525 was correct - see #594.

[eliben]

@sevaa do you want to just take over #530? It's not been responsive for quite a while now

[sevaa]

Oof. Let me see if I can pull this off. Never did a PR on top of another PR.

[sevaa]

So that one landed. I'll see what can be done about #594, and if I can land any of the pending PRs on the cheap.

[sevaa]

@eliben

Is there anything else on the agenda you'd prefer to see done before a release? #528 is fairly easy. #589 is held back by the GNU readelf, but they had a release in the meantime and I could try and integrate that, but new readelf usually comes with a bunch of unrelated format discrepancies in unexpected places. As for #540, I don't like their approach.

Also #564 will a pain in the neck to do, for what seems to be a somewhat marginal use case (.o files).

There is another issue I'm still chasing, a KeyError on DIE tree enumeration, which somehow only happens on PowerPC binaries (I don't have any). But I have no repro and no good idea about the root cause.

[eliben]

@sevaa Nothing specific from me. Happy to prepare a release. Do you want to get something else in?

[sevaa]

If I don't get a lead on the PowerPC crash in the next 2-3 days, let's go ahead and release. My monkeypatch file is getting embarrassingly long.

[eliben]

No problem, just ping me on this issue

[sevaa]

I got nothing. Release away.

[eliben]

v0.32 released