unread
While wondering what was the reasoning behind this commit, I came to
the conclusion that we should not do such thing in stable branches and
we should respect something we decided long time ago, to stop to add
bad options which can break PHP ABI or BC in one way or another. It isor maybe at least queue it up in a branch for "BC breaking review", or in
a branch where the ABI has already changed? I.e. if at some point you
must break the API/ABI, you can then shuttle in the rest of the changes
that you would have wanted but had deferred for this reason.
Right, and we have a clear way to do it, increase the middle version
number (4.3 > 4.4, 5.2 > 5.3, etc.).
Cheers,
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org