[squid-dev] Squid-5 status update and RFI

[Alex Rousskov]

On 12/30/19 4:46 AM, Amos Jeffries wrote:
> 
> The v5 branch will be bumped to master HEAD
> commit in a few hours then the documentation update PRs for stage 2 will
> proceed.

I would wait for all pending v5 changes to be committed to master before
pointing v5 to master's HEAD. There is no pressure to commit to master
anything that should not be in v5 right now.

Alex.


> On 5/09/19 10:37 pm, Amos Jeffries wrote:
>> Hi all,
>>
>> A request today for backporting large changes to v4 has prompted me to
>> take a look at where Squid-5 is in terms of being ready for branching.
>>
>> As of a few weeks ago it passed the criteria for feature count.
>>
>> There are 3 new major or higher bugs right now, 23 new ones in total
>> already known. Which is small enough to accept as a starting point.
>>
>>
> <https://bugs.squid-cache.org/buglist.cgi?bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&columnlist=bug_severity%2Cversion%2Cop_sys%2Cshort_desc&list_id=7331&order=version%20DESC%2Cbug_severity%2Cbug_id&product=Squid&query_format=advanced&version=5>
>>
>>
>>
>> So as a tentative plan, lets say 2 weeks away:
>>
>>     27 Sep 2019
>>
>> For the branching Squid-5 and a v5.0.1 Beta release shortly after.
>>
>> Note: PR under review by the branching date will be ported should they
>> complete that review and be merged during the v5 beta series.
>>
>>
>> To get a late-PR exemption from the "no new features" or "no UI changes"
>> policy please reply to this message with a brief (one-liner) description
>> of the project and an ETA for PR review submission.
>>
>>
> 
> 
> On 12/09/19, 2:59 pm, Alex Rousskov wrote:
>>
>> FWIW, below is a list of Factory projects that should be submitted for
>> the official review soon. It is difficult to give a reliable ETA for
>> individual project submission because it depends, in part, on the
>> activity surrounding already submitted PRs, which is largely outside our
>> control. Said that,
>>
>> * The projects closer to the top of the list have completed primary
>> development and testing cycles; they are being massaged for the official
>> submission. 10-15 days?
>>
>> * The projects in the middle of the list may need another internal
>> polishing round or two, but no major rewrites are expected.
>>
>> * The projects at the very end of the list still need serious
>> development work which may take 3-5 weeks or longer.
>>
> 
> After eliding the PRs already submitted and/or merged we currently have
> this list of Factory projects without any PR submitted:
> 
>>
>> SQUID-392: Maintain cache metadata when updating headers
>> SQUID-291: Support slow cache_peer_access ACLs
>> SQUID-448: Critical collapsed forwarding regressions
>> SQUID-216: log the number of request sending attempts
>> SQUID-340: Detail TLS client handshake errors
>> SQUID-357: Detail TLS server handshake errors
>> SQUID-425: Bug 4906: src ACL mismatches when access logging TCP probes
>> SQUID-464: %>connection_id logformat code
>>
> 
> Of these only 216, 291 and 464 appear to relate the Squid API. But not
> in a way that would prevent the beta series starting.
> 
> I will try to keep an eye out for these in the backports, but they still
> have to be submitted and approved just like anything else.
> 
> 
> The PRs already submitted have been marked to distinguish which will get
> my attention during v5 beta cycle with the plan being to backport unless
> there is a major blocker found that prevents it being merged.
> 
> 
> Amos
> _______________________________________________
> squid-dev mailing list
> squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev
>