Re: [EXTERNAL] Slack Invite request to take part in GSOC Varnish Cache support in Apache Traffic Control (2023)

[Holguin, Eric]

Invite sent

From: Rohith Raju 
Date: Thursday, March 9, 2023 at 12:39 AM
To: dev@trafficcontrol.apache.org , 
fri...@trafficcontrol.apache.org 
Subject: [EXTERNAL] Slack Invite request to take part in GSOC Varnish Cache 
support in Apache Traffic Control (2023)
Hello Team,
Will someone please invite me to the ASF Slack so I can join the 
#traffic-control channel?

Re: 2023-02-22 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

I heard that all of the gorilla libraries have been archived, how does it 
affect us?

From: ocket  
Date: Wednesday, February 8, 2023 at 10:32 AM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] 2023-02-22 TC Working Group Agenda and Meeting Notes
If you have anything you want to discuss at the next meeting, reply to this
email and it's on the agenda.

Re: 2023-01-11 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

Continue discussing the parts of the project that are not in use or code 
duplication that could be removed.
From: ocket  
Date: Wednesday, January 4, 2023 at 10:41 AM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] 2023-01-11 TC Working Group Agenda and Meeting Notes
If you have anything you want to discuss at next week's meeting, respond
to this email and it's on the agenda.

Re: [EXTERNAL] 2023-01-04 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

Consider discussing:

Are there parts of the project that are not in use or code duplication that 
could be removed? In the interest of reducing the amount of code we maintain.


From: ocket  
Date: Tuesday, January 3, 2023 at 4:09 PM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] 2023-01-04 TC Working Group Agenda and Meeting Notes
If you have anything you want to discuss at next week's meeting, respond to
this email and it's on the agenda.

Re: [EXTERNAL] Re: 2022-11-08 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

> How exactly does it not work? It seems to run ok for me on an arm64 (Apple 
> M1).

This is an issue when using nerdctl that happens outside of arm64 and is not 
limited to Traffic Router, more investigation is needed to get nerdctl working 
for all TC components.

From: Rawlin Peters 
Date: Wednesday, November 9, 2022 at 2:36 PM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] Re: 2022-11-08 TC Working Group Agenda and Meeting Notes
> Traffic Router seemingly doesn't work on arm64, despite being
not tied to an architecture

How exactly does it not work? It seems to run ok for me on an arm64 (Apple M1).

On Tue, Nov 8, 2022 at 10:40 AM ocket   wrote:
>
> 1. Attendance
> - Srijeet Chatterjee
> - Zach Hoffman
> 2. arm64 suport updates
> - builder images now support arm64
> - PR #7176 makes the build system support arm64
> - Traffic Router seemingly doesn't work on arm64, despite being
> not tied to an architecture
> - podman and rancher don't work either - but also not directly
> using containerd
> 3. Issue Grooming
> - #6161 - left a comment noting that the issue still exists, added
> "low impact" and "low difficulty" labels
> - #7045 - Needs rebase, needs outstanding review feedback addressed
> - #6454 - No action
> - #6871 - Change title to be more accurate/appropriate
> - #3537 - Add comment asking if an issue should be opened to track
> the effort to move from parent.config to strategies.yaml
> - #3086 - Added "bug" label
> - #4023 - left comment asking if the system_stats ATS plugin
> solves the issue
> - #957 - Added "Needs more Info" label
> - #1131 - Left a comment asking if the newer spec file in the
> cache-config tests directory should replace the older one under the
> top-level traffic_server directory
> - #2293 - Added "high difficulty" label
>
> On Tue, Nov 8, 2022 at 9:21 AM Zach Hoffman  wrote:
> >
> > Consider discussing:
> > - aarch suport updates:
> > * The builder images now support arm64
> > * PR to make the build system support aarch64 <
> > https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/pull/7176__;!!CQl3mcHX2A!BZEzPLzhL1uPXAVyD-tErjrAvX0qfZEk04XWRB8qaHwWOkQKc5OoD3r6h0iw1gSYYmB6syA7ALbwUtbyLUE$
> >   >
> >
> > On Tue, Nov 1, 2022 at 10:17 AM ocket   wrote:
> >
> > > If you have anything you want to discuss at next week's meeting
> > > respond to this email and it's on the agenda.
> > >

Re: [EXTERNAL] Re: 2022-10-25 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

  1.  Attendance

  *   Zach Hoffman
  *   Joshua Zenn
  *   Amy Wilson
  *   Kurtis Michie
  *   Srijeet Chatterjee


  1.  What would be the benefits and drawbacks from splitting T3C out into its
own repo?

  *   Most people using the trafficcontrol repo have benefitted from the mono 
repo strategy
  *   Already other traffic control repos out there (trafficcontrol-website, 
trafficcontrol-trafficops-types)
  *   Not optimal - might require most PRs to update master branch – example 
Apache Camel
  *   Reason to split out could be holding t3c devs back


  1.  What would it take to update Traffic Router (and the Java TO client) to
OpenJDK 13?

  *   Few library differences between 11 and 13 (nothing as drastic as LTS 8 
and LTS 11)
  *   No love for OpenJDK 13 in Centos repos – doesn’t look like an option
  *   OpenJDK 17 possible option – might have to provide the rpm (like we do 
for tomcat)
  *   We’d be responsible to figure out where it comes from if we do upgrade
  *   Wait for Centos 7 EOL (1 year 8 months)



  1.  Would a different TC working group time get better participation?

  *   Overlap in meetings – there should be a suggestion made to the mailing 
list for a different time/day that works for people


  1.  Closing milestones?

  *   Closed 6.1.0 and 6.0.3
  *   Closing 7.0.0 should be determined by the release manager
  *   Adding to milestone 7.1.0 or retracting from it should be determined by 
the release manager


From: Zach Hoffman 
Date: Tuesday, October 25, 2022 at 9:22 AM
To:
Cc: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] Re: 2022-10-25 TC Working Group Agenda and Meeting Notes
- Would a different TC working group time get better participation?

On Tue, Oct 25, 2022 at 9:20 AM Zach Hoffman  wrote:

> If you have anything you want to discuss at next week's meeting respond
> to this email and it's on the agenda.
>
> Consider discussing:
>
> - What would be the benefits and drawbacks from splitting T3C out into its
> own repo?
> - What would it take to update Traffic Router (and the Java TO client) to
> OpenJDK 13?
>
> -Zach
>

Re: [EXTERNAL] 2022-07-26 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

Discuss adding codecov to the project  https://about.codecov.io/for/open-source/

From: ocket  
Date: Tuesday, July 19, 2022 at 10:22 AM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] 2022-07-26 TC Working Group Agenda and Meeting Notes
If you have anything you want to discuss at next week's meeting
respond to this email and it's on the agenda.

RE: 2022-04-05 TC Working Group Agenda and Meeting Notes

[Holguin, Eric]

Are there any plans or thoughts on API v5? Something that comes to mind is the 
removal of the repetitive delivery service server routes.

On 2022/03/29 16:01:11 ocket  wrote:
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: [EXTERNAL] [VOTE] Release Apache Traffic Control 6.1.0-RC2

[Holguin, Eric]

+1

From: Zach Hoffman 
Date: Monday, January 31, 2022 at 2:51 PM
To: dev@trafficcontrol.apache.org 
Subject: [EXTERNAL] [VOTE] Release Apache Traffic Control 6.1.0-RC2
I've prepared a release for 6.1.0-RC2. Changes since RELEASE-6.0.2:


https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC2__;!!CQl3mcHX2A!S43JnvEYF9q2cLSEu61lYQmhvAwCtfS8lwIv2H4GFzQckamsuKHnqJKUiQho-nn1lug$

https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC2/CHANGELOG.md__;!!CQl3mcHX2A!S43JnvEYF9q2cLSEu61lYQmhvAwCtfS8lwIv2H4GFzQckamsuKHnqJKUiQhoUgkQmcE$

The artifacts are available for download at:


https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC2/__;!!CQl3mcHX2A!S43JnvEYF9q2cLSEu61lYQmhvAwCtfS8lwIv2H4GFzQckamsuKHnqJKUiQhofLGkbK4$

BLAKE2 checksum:
35b73bea81f6550aeecb8e5a0e8776089b557fea135ffdd1c6bc022d3625e34941c834d55114cf7de594578ba4bbe1103d17ae9d3efc3b92ed52279d2c5b14e7
  apache-trafficcontrol-6.1.0.tar.gz

SHA512 checksum:
be4cb2d99462cd92bb771705853381b8c6fd466d97ebbf273cc401e26629a56019838ba4a9993504780f5994f5005ae5f04d27587664ea3fe5113f816d6e1424
  apache-trafficcontrol-6.1.0.tar.gz

This corresponds to git refs:

Hash: f8041b3b5d616003b32d7c0dc160f5f9621e5366
Tag: RELEASE-6.1.0-RC2

Which can be verified with the following command:

$ git tag -v RELEASE-6.1.0-RC2

All code signing keys are available here:


https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS__;!!CQl3mcHX2A!S43JnvEYF9q2cLSEu61lYQmhvAwCtfS8lwIv2H4GFzQckamsuKHnqJKUiQhovacEZtE$

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 22:00 UTC on Thursday, February 3 and passes if a 
majority of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach