On Mon, Feb 8, 2016 at 12:57 PM, William A Rowe Jr <wrowe@rowe-clan.net> wrote:
This is excellent, thanks for the effort!

You should note that there was no binary compatibility between 2.2.x final
and 2.4.x.  And there will be no binary compatibility between 2.next (3.0?)
and 2.4.x.  The interesting branches to compare for 2.2.next and 2.4.next
to anticipate any binary breakage before we release would be in subversion 
under the paths;

while 2.next (3.0) with binary-breaking changes lives at the path;

This looks like a great tool, much appreciated :)


On Sun, Feb 7, 2016 at 2:32 AM, Ponomarenko Andrey <andrewponomarenko@yandex.ru> wrote:

I've started to maintain binary compatibility report for the recent versions of the httpd: http://abi-laboratory.pro/tracker/timeline/httpd/

The report is updated every other day. The report for the latest version from git is also there. Hope this helps Linux maintainers to be aware of ABI changes and added/removed symbols.

Thank you.

Perhaps there could be a way to configure a message related to the intended breakage between 2.2.last and 2.4.first, since that is interesting from an API migration standpoint.  (Link to https://httpd.apache.org/docs/2.4/developer/new_api_2_4.html)

Born in Roswell... married an alien...