On Mon, Feb 8, 2016 at 12:57 PM, William A Rowe Jr <wr...@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; > > http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x > http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x > > while 2.next (3.0) with binary-breaking changes lives at the path; > http://svn.apache.org/repos/asf/httpd/httpd/trunk > > This looks like a great tool, much appreciated :) > > Bill > > > On Sun, Feb 7, 2016 at 2:32 AM, Ponomarenko Andrey < > andrewponomare...@yandex.ru> wrote: > >> Hello, >> >> 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... http://emptyhammock.com/
