freebsd stable - Sep 2017 - ABI changes within stable branch

Now that we are on a faster upgrade policy for minor branches, it is expected
that we'll upgrade from 11.0 to 11.1 to 11.2 much faster than in the old
days. I can cope with that, but it appears that functional changes are also
being made within the stable branch as seen here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221672

A new fdatasync()  method is available in 11.1 but not in 11.0 which means that
I now need to maintain separate ports trees for each minor update. I've
never done this before, assuming (correctly for me until now) that all ports
build on the latest minor release within the stable branch would work on older
releases until I was ready to upgrade them.

Is this instance a mistake or am I misunderstanding the new policy?

If I need to treat each release within the stable branch as a whole new platform
for ports, that means a bunch of extra testing and maintenance work for me.

Cheers
Ari


-- 
-------------------------->
Aristedes Maniatis
CEO, ish
https://www.ish.com.au
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Hi!
> Now that we are on a faster upgrade policy for minor branches, it is
expected that we'll upgrade from 11.0 to 11.1 to 11.2 much faster than in
the old days. I can cope with that, but it appears that functional changes are
also being made within the stable branch as seen here:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221672
> 
> A new fdatasync()  method is available in 11.1 but not in 11.0 which means
that I now need to maintain separate ports trees for each minor update. I've
never done this before, assuming (correctly for me until now) that all ports
build on the latest minor release within the stable branch would work on older
releases until I was ready to upgrade them.
I think it was the other way around: All ports build on the .0 of
a RELEASE work on all later .x of that RELEASE. Which makes it a bit
difficult, if a .0 is no longer supported/patched by the secteam.

A pointer to the official policy would be nice 8-}

-- 
pi at opsec.eu            +49 171 3101372                         3 years to go
!