Re: ABI Compliance Checker GSoC Project

"David E. Wheeler" <david@justatheory.com> writes:
> How bout we keep it a simple as possible to start with: make it either the last tag in the branch or else the first
commitin the branch (the branch commit). Except for master, in which case perhaps since the last time a branch was
created?

I do not think we either need or want ABI checking on master.
I'm not even convinced we want it on a currently-beta branch;
having to update the reference point after each ABI-breaking
commit seems like mostly make-work until we approach RC stage.
I like the idea of an in-tree file partly because the decision
about when to create it in a branch could be made dynamically.

If we do want to drive this off tags, I'd suggest a rule like
"Use the most recent tag of the form REL_m_n or REL_m_RCn;
if there is none in this branch, don't perform ABI checking".
But I still wonder how expensive it'll be to determine that.

            regards, tom lane