On 17 Apr 2018, at 4:41 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
> And everything contributed to 2.4.33 release? All in vain. None of > that in this OS distribution, because, code freeze. I’m not following the “all in vain”. This patch in v2.4.33 was dine specifically to fix an issue in Xenial, and Ubuntu is on the case: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1750356 > We observe the "code freeze" effect (defined by three different > distributors) coupled with distributors deep distrust of our releases, > so by continuously polluting our version major.minor release with more > and more cruft, those users are denied not only the new cruft, but all > the bug fixes to the old cruft as well... there's really no other > explanation for the users of one of our most common distributions to > be locked out of several subversions worth of bugfix corrections. I’m lost - what problem are you trying to solve? Regards, Graham —
smime.p7s
Description: S/MIME cryptographic signature
