[pkg-squid-devel] Whats next for Squid in Buster?

[Amos Jeffries]

On 29/06/17 01:46, Amos Jeffries wrote:
> Hi guys,
> 
>   Time for buster. (Yay!)
> 
> 
> Item A)
> 
> So, as far as I am aware from back when jesse happened we are now 
> waiting on someone to branch master and upstream/sid at the point where 
> squid-3.5.23-6 happened to branches the security team can work with for 
> the stretch packaging.
> 
>   Who does that? can it please be taken care of ASAP :-)
> 
> 
> Item B)
> 
> During freeze we also briefly discussed some shuffling of the 
> repositories and source package names around.
> 
> 1) repository 'squid' rename to 'squid2'
> 
> 2) repository squid3 rename to 'squid'
> 
> 3) source package name squid3 rename to squid.
> 
> 
> Do we actually have agreement on doing it that way?
>   if not, what alternative(s) should happen?
>   and who does the change when agreed?
> 
> 
> Item C)
> 
> The Squid-4 package I have been assembling for upload to experimental.
> 
> Upstream I have reached the situation where there are only 3 bugs 
> blocking the stabilization process, and two of those have fixes already 
> in the pipeline. So I tentatively estimate, maybe, just perhapse, about 
> 2 months before Squid-4 achieves the criteria for a 'stable' release.
> 
> Is anyone interested enough to sponsor an upload to experimental?
>   or shall I wait on the 4.1 release, and re-target it directly at sid?
> 

Updates on the Squid-4 situation;


Now down to just one blocker bug, and things are looking very quiet 
since the 4.0.21 beta. So I am quite hopeful that Squid-4 stable will be 
not long after that get fixed.


Additionally upstream have moved to git from bzr this month. So there is 
now a github repository that can be linked to.
  <https://github.com/squid-cache/squid>
The release series branches should be obvious from the vN.N numbered 
names. Release tagging though still uses the SQUID_X_Y_Z numbering from 
BZR and CVS.


I have looked into what would be required to link the pkg-squid3 
repository with the upstream remote. According to DEP-14 it should be 
tracked as upstream/* .

But we already have some branches under there and I am new enough with 
git not to know whether it is safe to mix legacy content and a remote 
repository in that namespace. Anyone know better?

     upstream/4
     upstream/jessie
     upstream/sid
     upstream/wheezy

Amos