The following changes accepted into v6 are also eligible for v5 but have
issues preventing me scheduling them.
This has conflicts I need some assistance resolving. So will not being
doing the backport myself. If you are interested please open a PR
against v5 branch for the working backport before Feb 1st.
* Bug #5090: Must(!request->pinnedConnection()) violation (#930)
squid-6-15bde30c33e47a72650ef17766719a5fc7abee4c
The following just need bugzilla IDs. If interested in getting a
backport please open the bug report with useful details (ie document the
user-visible behaviour) and then ping me.
* Properly track (and mark) truncated store entries (#909)
squid-6-ba3fe8d9bc8d35c4b04cecf30cfc7288c57e685c
* Fix reconfiguration leaking tls-cert=... memory (#911)
squid-6-b05c195415169b684b6037f306feead45ee9de4e
* Preserve configured order of intermediate CA certificate chain (#956)
squid-6-166fb918211b76a0e79eb07967f4d092f74ea18d
This is going to be a special case. Alex; I responded to you a few hrs
back in the squid-users thread "squid 5.3 frequent crash" with a plan
that I am okay with for backporting.
* Bug #5055: FATAL FwdState::noteDestinationsEnd exception: opening (#877)
squid-6-2b6b1bcb8650095c99a1916f5964305484af7ef0
and; Fix FATAL ServiceRep::putConnection exception: theBusyConns > 0 (#939)
squid-6-a8ac892bab446ac11f816edec53306256bad4de7
Cheers
Amos
_______________________________________________
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev
