-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Daniel,
On 7/24/20 17:36, Daniel Ruggeri wrote: > Hey there, Chris; > > Fair question - and I don't think I have a handy link describing > the flow of patch -> trunk -> STATUS backport proposal -> branch > commit -> release > > Generally speaking, the code goes into trunk and is proposed for > backport into a stable branch via the STATUS file (at the root of > the branch - ex > http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=ma rkup). > > A lot of times, patches are proposed for discussion/refined and > tweaked/etc before being committed in trunk, which seems to fit > the conversation in your reference BZ item. From there, we need > three committer +1s to backport. Once all three are in place, the > proposer (or release manager) commits the change to the branch. So, > for this one, I think we're not quite ready to incorporate. Sounds reasonable to me. I'll be pushing to get this back-ported for the next 2.4.x release since I'm throwing mod_jk completely under the bus at ApacheCon this year and it's a pretty important missing-feature in mod_proxy. Thanks, - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl8bVaEACgkQHPApP6U8 pFjuIRAAnp6Ej0SvbRrS+bCgyDQzoATyycNSTPnYZt7uBKIGmuSXhZXHDgCJw6hs XdCu9j1/9mJKHK0+PibElEGogFYb6bl7Ncm21wWrV4g70RUW0EJEAKVbEEQN/xA8 1QbnhK6MFtex9eNJcw8AQCKncht6V4foO9GKNbrV4IeJ/1By/3VYPe0mfq2AsHSJ OnVL4WPvk3mQs7Ct1FMhra5/05tb+tkfA+A4wjLVd3+kR850xJrfsgoTIaBfjH+a /XoOqhgyc0/9F9dkKNlXh1NUDRfmvHQm8HvNIJWWtfAxG88ksxy3umEwfsZoUeXE PaSnCvS8GzVuAvoroQ/4vszHPCSMdL13o333H2nc4qDSnTRXuxgW3uxOFZXpRdIT 7Qq4H153AxUQpT0kLlaew8SyMCiK7V/mP0GMlx3UHdPYMl38JdjYlgRGb7YpZ5IX c4tZ4VUH6/7iLZ4BlG2/es9YdoypsSv06Hx8ZTztYfnbR7pvoYA4t2qWQKrQ+17G PUGEkGpbFL8LcWxN/nf3fYaoFy8sp3u5kSn7CyCmLetSKjZ32jxToMPJF+Fsk4c7 ULDlvehugffoVgI2Wi/zxqPe+S5XAyWyGzhcfal7MdM67J/Tsc9QDqhNT7kaHAlQ kcO7WE3HpDohON0DVqz3GcaQo293wXyEPB5b68flsJNbgO55H/A= =0hj2 -----END PGP SIGNATURE-----
