[squid-users] Git tag strategy in Squids GitHub repo

Vacheslav m_zouhairy at skno.by
Wed Aug 22 14:55:19 UTC 2018

-----Original Message-----
From: squid-users <squid-users-bounces at lists.squid-cache.org> On Behalf Of Alex Rousskov
Sent: Wednesday, August 22, 2018 5:51 PM
To: squid-users at lists.squid-cache.org
Subject: Re: [squid-users] Git tag strategy in Squids GitHub repo

On 08/21/2018 09:05 PM, Amos Jeffries wrote:
> On 21/08/18 11:22 PM, Simon Staeheli wrote:
>> It would be awesome if there is tag pointing to every official Squid release. 

> our auto-commit bot the QA team came up with does not do tagging.

>Very true. It also does not water plants.

> And tags from third-party repositories (ie my release staging
> one) are not imported by the github PR process.

>True again and still irrelevant. GitHub does not import lightweight tags when merging PRs because those tags are not a part of a PR branch and are not supposed to be imported by git design.

>GitHub certainly supports release tagging. The PR merging bot is not (and probably should not be) responsible for releases, including release tagging.

>FWIW, in March 2018 email to Amos, I have already tried to explain the design approach behind git tagging and offered a specific short-term tagging solution. I did not get a response.


I get this all the time it's never me, it's everybody else who is out to get me :)
Like it wasn't the driver, the port on the switch was blocking, i.e I'm the innocent good guy!
squid-users mailing list
squid-users at lists.squid-cache.org

More information about the squid-users mailing list