@ffurano - I don't understand the opposition to breaking the ABI. In #585, I proposed making this API public in order to some sort of ABI stability for users (such as the DPM plugins) and you wrote:

I am definitely not a philosopher of ABI compatibility, and I have put those headers with the private ones exactly to have more freedom, until the interface stabilizes, which can take quite some time.

In that case, we broke the ABI for the 4.8.0 release to have more convenient access to the XrdSecEntity. So, everyone last year had to recompile their plugins to upgrade to the 4.8.0 release (just as we would have them doing here).

If we can no longer do fixes to clear oversights the API, why don't we mark it as public?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bbockelm in #879: @ffurano - I don't understand the opposition to breaking the ABI. In #585, I proposed making this API public in order to some sort of ABI stability for users (such as the DPM plugins) and you wrote:\r\n\r\n\u003e I am definitely not a philosopher of ABI compatibility, and I have put those headers with the private ones exactly to have more freedom, until the interface stabilizes, which can take quite some time.\r\n\r\nIn that case, we broke the ABI for the 4.8.0 release to have more convenient access to the `XrdSecEntity`. So, everyone last year had to recompile their plugins to upgrade to the 4.8.0 release (just as we would have them doing here).\r\n\r\nIf we can no longer do fixes to clear oversights the API, why don't we mark it as public?"}],"action":{"name":"View Pull Request","url":"https://github.com/xrootd/xrootd/pull/879#issuecomment-448200108"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/879#issuecomment-448200108", "url": "https://github.com/xrootd/xrootd/pull/879#issuecomment-448200108", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1