You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by ocket 8888 <oc...@gmail.com> on 2021/10/19 15:31:25 UTC
2021-10-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.
Rolling over from last week:
- is it time to make the unstable API (4.0) stable?
- what is our next version and when? 6.0.1? 6.1? 7.0?
- We should start thinking about Google Summer of Code 2022
Mailing list thread updates since last week:
- Federations rework blueprint
Also, follow-up on:
- Asked Jonathan Amsterdam about our options to make newer versions
show up on https://github.com/apache/trafficcontrol/issues/4380
Re: 2021-10-26 TC Working Group Agenda and Meeting Notes
Posted by Dave Neuman <ne...@apache.org>.
Thanks Brennan.
On Wed, Oct 27, 2021 at 12:42 PM ocket 8888 <oc...@gmail.com> wrote:
> Because I was taking notes on my laptop, so when I lost internet yesterday
> I had no way to send _any_ meeting notes. I saved them to a text file and
> forgot about it until right this very minute:
>
> 1. Attendance
> - Taylor Frey
> - Justin Howard
> - Amy Wilson
> - Srijeet Chatterjee
> - Jeremy Mitchell
> - Stephen Hamrick
> - Zach Hoffman
> 2. Should API 4.0 be stable
> - Not yet, ask again next week - hopefully Rawlin will be here
> 3. Should the next release be 6.0.1, 6.1.0, or 7.0.0?
> - Zach is looking at cutting 6.0.1 RC0 soon
> - Maybe we should use "time-boxed" releases, which will enforce scope
> - proposed schedule would be either a new minor or micro version every
> month
> - When an API version is removed the version update must be major, so if
> APIv4 becomes stable - and therefore API 2.0 is removed - we need to move
> to 7.0.0
> - Jeremy will follow up with a proper mailing list proposal
> 4. Google summer of code 2022
> - The sooner we get a proposal in, the better
> - We'll discuss further in a mailing list thread
> 5. Federations Rework blueprint
> - read it! Or don't, it's not a priority for the PR's author
> 6. Update on Go Module versioning difficulties
> 7. Should we support ARM?
> - Maybe, once a contributor has a processor to test on.
> - Zach will open an Issue making note of places where a specific
> architecture is assumed/alluded to.
>
> On Wed, Oct 27, 2021 at 9:40 AM Dave Neuman <ne...@apache.org> wrote:
>
> > If we talked about releases - as indicated in the releases ML discussion
> -
> > why is it not in the notes?
> >
> > On Tue, Oct 26, 2021 at 9:07 AM Zach Hoffman <zr...@apache.org>
> wrote:
> >
> > > Consider discussing:
> > > - Apple M1 processors are fast and power-saving, and in the future,
> > > they or other ARM processors might even be less expensive than
> > > amd64/x86_64. How much effort would it take to support ATC targeting
> > > aarch64/arm64?
> > >
> > > Following up from last week:
> > > - The go.mod file was removed from the `v6.0.0` tag (but not the
> > > `RELEASE-6.0.0` tag) and now
> > > https://pkg.go.dev/github.com/apache/trafficcontrol shows
> > > v6.0.0+incompatible content.
> > > <https://github.com/apache/trafficcontrol/pull/6305>
> > >
> > > Active mailing list threads within the past week:
> > > - Maing use of GitHub Triage role
> > > <
> > >
> >
> https://lists.apache.org/thread.html/r72a8c0fe0bd7fd753bae4c924e4b08edd96e8fc30b26ee54fb2c7ca5%40%3Cdev.trafficcontrol.apache.org%3E
> > > >
> > >
> >
>
Re: 2021-10-26 TC Working Group Agenda and Meeting Notes
Posted by ocket 8888 <oc...@gmail.com>.
Because I was taking notes on my laptop, so when I lost internet yesterday
I had no way to send _any_ meeting notes. I saved them to a text file and
forgot about it until right this very minute:
1. Attendance
- Taylor Frey
- Justin Howard
- Amy Wilson
- Srijeet Chatterjee
- Jeremy Mitchell
- Stephen Hamrick
- Zach Hoffman
2. Should API 4.0 be stable
- Not yet, ask again next week - hopefully Rawlin will be here
3. Should the next release be 6.0.1, 6.1.0, or 7.0.0?
- Zach is looking at cutting 6.0.1 RC0 soon
- Maybe we should use "time-boxed" releases, which will enforce scope
- proposed schedule would be either a new minor or micro version every
month
- When an API version is removed the version update must be major, so if
APIv4 becomes stable - and therefore API 2.0 is removed - we need to move
to 7.0.0
- Jeremy will follow up with a proper mailing list proposal
4. Google summer of code 2022
- The sooner we get a proposal in, the better
- We'll discuss further in a mailing list thread
5. Federations Rework blueprint
- read it! Or don't, it's not a priority for the PR's author
6. Update on Go Module versioning difficulties
7. Should we support ARM?
- Maybe, once a contributor has a processor to test on.
- Zach will open an Issue making note of places where a specific
architecture is assumed/alluded to.
On Wed, Oct 27, 2021 at 9:40 AM Dave Neuman <ne...@apache.org> wrote:
> If we talked about releases - as indicated in the releases ML discussion -
> why is it not in the notes?
>
> On Tue, Oct 26, 2021 at 9:07 AM Zach Hoffman <zr...@apache.org> wrote:
>
> > Consider discussing:
> > - Apple M1 processors are fast and power-saving, and in the future,
> > they or other ARM processors might even be less expensive than
> > amd64/x86_64. How much effort would it take to support ATC targeting
> > aarch64/arm64?
> >
> > Following up from last week:
> > - The go.mod file was removed from the `v6.0.0` tag (but not the
> > `RELEASE-6.0.0` tag) and now
> > https://pkg.go.dev/github.com/apache/trafficcontrol shows
> > v6.0.0+incompatible content.
> > <https://github.com/apache/trafficcontrol/pull/6305>
> >
> > Active mailing list threads within the past week:
> > - Maing use of GitHub Triage role
> > <
> >
> https://lists.apache.org/thread.html/r72a8c0fe0bd7fd753bae4c924e4b08edd96e8fc30b26ee54fb2c7ca5%40%3Cdev.trafficcontrol.apache.org%3E
> > >
> >
>
Re: 2021-10-26 TC Working Group Agenda and Meeting Notes
Posted by Dave Neuman <ne...@apache.org>.
If we talked about releases - as indicated in the releases ML discussion -
why is it not in the notes?
On Tue, Oct 26, 2021 at 9:07 AM Zach Hoffman <zr...@apache.org> wrote:
> Consider discussing:
> - Apple M1 processors are fast and power-saving, and in the future,
> they or other ARM processors might even be less expensive than
> amd64/x86_64. How much effort would it take to support ATC targeting
> aarch64/arm64?
>
> Following up from last week:
> - The go.mod file was removed from the `v6.0.0` tag (but not the
> `RELEASE-6.0.0` tag) and now
> https://pkg.go.dev/github.com/apache/trafficcontrol shows
> v6.0.0+incompatible content.
> <https://github.com/apache/trafficcontrol/pull/6305>
>
> Active mailing list threads within the past week:
> - Maing use of GitHub Triage role
> <
> https://lists.apache.org/thread.html/r72a8c0fe0bd7fd753bae4c924e4b08edd96e8fc30b26ee54fb2c7ca5%40%3Cdev.trafficcontrol.apache.org%3E
> >
>
Re: 2021-10-26 TC Working Group Agenda and Meeting Notes
Posted by Zach Hoffman <zr...@apache.org>.
Consider discussing:
- Apple M1 processors are fast and power-saving, and in the future,
they or other ARM processors might even be less expensive than
amd64/x86_64. How much effort would it take to support ATC targeting
aarch64/arm64?
Following up from last week:
- The go.mod file was removed from the `v6.0.0` tag (but not the
`RELEASE-6.0.0` tag) and now
https://pkg.go.dev/github.com/apache/trafficcontrol shows
v6.0.0+incompatible content.
<https://github.com/apache/trafficcontrol/pull/6305>
Active mailing list threads within the past week:
- Maing use of GitHub Triage role
<https://lists.apache.org/thread.html/r72a8c0fe0bd7fd753bae4c924e4b08edd96e8fc30b26ee54fb2c7ca5%40%3Cdev.trafficcontrol.apache.org%3E>