1. Attendance
- Zach Hoffman
- Jeremy Mitchell
- Eric Holguin
- Taylor Frey
- Juliet Ngwe
- Srijeet Chatterjee
2. Since Dockerhub now uses rate limiting, we should use the GitHub
Container Registry to speed up our GHA CI
- PR #6699 shows an example
- Could potentially be a large effort
- The definitions can go in the main repo - alternatively, ATS has
a separate repo for their CI docker images
- Zach will make an issue outlining what needs to be done to
accomplish this and bring it up to the mailing list
3. Should we get notifications of wiki edits in Slack?
- We'd need to write a GHA that triggers on wiki edits, since it
won't trigger webhooks automatically
- The notifications would be added to #traffic-control-commits
- Nobody seems to have a problem with it, a couple people think it
could be useful
4. What's left for ATCv7
- APIv4 will (hopefully) be stabilized
- assuming that does happen, APIv3 will be deprecated
- endpoints being removed from the API in v4 need deprecation
notices and warning-level alerts
- The Ansible PR could use a better name
- Squashing migrations is medium effort (#6698 - added "medium
effort" label)
- The create_tables.sql script may not need to be idempotent anymore
- That needs mailing list discussion in case people rely
on the script being idempotent
- APIv2 should be removed (#6697 - added "medium effort" label)
- Removal issue needs more details
On Tue, Mar 29, 2022 at 9:21 AM Jeremy Mitchell <mitchell...@gmail.com> wrote:
>
> let's discuss what needs to be done to get ready for our Q2 release: TC
> 7.0.0
>
> On Tue, Mar 29, 2022 at 9:19 AM Zach Hoffman <zrhoff...@apache.org> wrote:
>
> > Consider discussing:
> >
> > - Since the Docker hub now uses rate limiting, we should take
> > advantage of the GitHub Container Registry to speed up our CI.
> > Example: https://github.com/apache/trafficcontrol/pull/6699
> > - Do we want to be notified of wiki edits in #traffic-control-commits?
> >
> > -Zach
> >
> > On Tue, Mar 22, 2022 at 9:28 AM ocket 8888 <ocket8...@gmail.com> wrote:
> > >
> > > If you have anything you want to discuss at next week's meeting,
> > > respond to this email and it's on the agenda.
> >
