On 03/09/2018 10:15 AM, Florian Weimer wrote:
On 03/07/2018 06:11 PM, Carlos O'Donell wrote:
> Would we create an upstream Fedora branch that is based on the
> glibc release, and then layer the ABI baselines there?
Yes, we could have an abi/ directory tree with those files there.
Any ABI change would also have to update the baseline files. That
may not work so well for rawhide, though.
What would not work well?
What are the "baseline" files?
If we went with upstream branches I would assume they would look like this:
master (glibc) -> master (rawhide)
Here master (rawhide) has an abi/ directory, but it isn't verified against.
When master (glibc) freezes we start doing ABI verification on rawhide spec
files.
When we branch to f29, what do we do?
* Branch from release/2.28/master to create f29.
* Merge master (rawhide) changes into f29 branch.
* Update final abi/* files.
Then I assume we need not modify master (rawhide) abi/ files as f29 beings
to deviate if we add GLIBC_PRIVATE symbols. The branch from which the
git-bundle is created need to be changed.
Cheers,
Carlos.