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 2022/01/11 16:43:00 UTC

2022-01-18 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-01-18 TC Working Group Agenda and Meeting Notes

Posted by ocket 8888 <oc...@gmail.com>.
1. Attendance
    - Zach Hoffman
    - Srijeet Chatterjee
    - Justin Howard
    - Juliet Ngwe
    - Jeremy Mitchell
    - Taylor Frey
    - Stephen Hamrick
2. Status of 6.1
    - 6.1.0 RC0 set to be open for voting today
    - Should we add everything that will be in 6.1 to the 6.1.0 milestone?
        - No that's what the CHANGELOG is for
            - Should we group CHANGELOG entries by component and/or
alphabetized?
                - That might not be helpful unless we have more rules
around a CHANGELOG entry's format
                - Components affected should be included in CHANGELOG
entries that affect more than one
                - Traditionally the release notes are grouped by
component, but the CHANGELOG isn't
                - We can add a sample entry to the PR template to
encourage people to do it without making it a real rule
3. Adding impact and effort level labels to technical debt issues
    - #6512 Asked @rawlinp what he thinks are good effort level/impact labels
    - #6504 Add "low effort" and "low impact" labels
    - #6502 Add "low effort" and "low impact" labels
    - #6501 Add "low effort" and "low impact" labels
    - #6500 Add "low effort" and "low impact" labels
    - #6499 Add "low effort" and "low impact" labels
    - #6498 Add "low effort" and "low impact" labels
    - #6497 Add "low effort" and "low impact" labels
    - #6496 Add "low effort" and "low impact" labels
    - #6495 Add "low effort" and "low impact" labels
    - #6494 Add "low effort" and "low impact" labels
    - #6493 Add "low effort" and "low impact" labels
    - #6492 Add "low effort" and "low impact" labels
    - #6491 Add "low effort" and "low impact" labels
    - #6490 Add "low effort" and "low impact" labels
    - #6489 Add "low effort" and "low impact" labels
    - #6488 Add "low effort" and "low impact" labels
    - #6487 Add "low effort" and "low impact" labels
    - #6486 Add "low effort" and "low impact" labels
    - #6485 Add "low effort" and "low impact" labels
    - #6484 Add "low effort" and "low impact" labels
    - #6483 Add "low effort" and "low impact" labels
    - #6482 Add "low effort" and "low impact" labels
    - #6481 Add "low effort" and "low impact" labels
    - #6480 Add "low effort" and "low impact" labels
    - #6479 Add "low effort" and "low impact" labels
    - #6478 Add "low effort" and "low impact" labels
    - #6477 Add "low effort" and "low impact" labels
    - #6476 Add "low effort" and "low impact" labels
    - #6475 Add "low effort" and "low impact" labels
    - #6474 Add "low effort" and "low impact" labels
    - #6473 Add "low effort" and "low impact" labels
    - #6472 Add "low effort" and "low impact" labels
    - #6471 Add "low effort" and "low impact" labels
    - #6470 Add "low effort" and "low impact" labels
    - #6469 Add "low effort" and "low impact" labels
    - #6468 Add "low effort" and "low impact" labels
    - #6467 Add "low effort" and "low impact" labels
    - #6466 Add "low effort" and "low impact" labels
    - #6465 Add "low effort" and "low impact" labels
    - #6464 Add "low effort" and "low impact" labels
    - #6463 Add "low effort" and "low impact" labels
    - #6462 Add "low effort" and "low impact" labels
    - #4047 Add "high effort" and "low impact" labels
    - #3924 Add "low effort" and "high impact" labels
    - #3868 Add "medium effort" and "high impact" labels
    - #3710 Asked @rob05c if t3c does any clean-up on DS deletion, and
what he thinks would be appropriate impact/effort level labels
    - #3515 Asked @rob05c if he can rename the issue and clean up the
description since its meaning has changed drastically since being
written
    - #3352 Asked @rob05c whether the issue refers to Traffic Router
or Traffic Monitor, as the description conflicts - Add "medium impact"
label
    - #3351 Add "medium impact" label

On Tue, Jan 18, 2022 at 9:20 AM Zach Hoffman <zr...@apache.org> wrote:
>
> - 6.1.0 RC0 to be open for voting today
>
> active mailing list threads:
> - Layered Profiles Blueprint
> <https://lists.apache.org/thread/5lwbxhnfppdg3x5crrz61mp0k4v73klv>
>
> -Zach
>
> On Tue, Jan 18, 2022 at 9:15 AM Jeremy Mitchell <mi...@gmail.com> wrote:
> >
> > Maybe we can put some impact and effort labels on the following tech debt
> > items:
> >
> > https://github.com/apache/trafficcontrol/issues?q=is%3Aopen+is%3Aissue+label%3A%22tech+debt%22++-label%3A%22high+impact%22+-label%3A%22medium+impact%22+-label%3A%22low+impact%22
> >
> > On Tue, Jan 18, 2022 at 9:14 AM Jeremy Mitchell <mi...@gmail.com>
> > wrote:
> >
> > > Status of 6.1
> > >
> > > On Tue, Jan 11, 2022 at 9:43 AM ocket 8888 <oc...@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.
> > >>
> > >

Re: 2022-01-18 TC Working Group Agenda and Meeting Notes

Posted by Zach Hoffman <zr...@apache.org>.
- 6.1.0 RC0 to be open for voting today

active mailing list threads:
- Layered Profiles Blueprint
<https://lists.apache.org/thread/5lwbxhnfppdg3x5crrz61mp0k4v73klv>

-Zach

On Tue, Jan 18, 2022 at 9:15 AM Jeremy Mitchell <mi...@gmail.com> wrote:
>
> Maybe we can put some impact and effort labels on the following tech debt
> items:
>
> https://github.com/apache/trafficcontrol/issues?q=is%3Aopen+is%3Aissue+label%3A%22tech+debt%22++-label%3A%22high+impact%22+-label%3A%22medium+impact%22+-label%3A%22low+impact%22
>
> On Tue, Jan 18, 2022 at 9:14 AM Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
> > Status of 6.1
> >
> > On Tue, Jan 11, 2022 at 9:43 AM ocket 8888 <oc...@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.
> >>
> >

Re: 2022-01-18 TC Working Group Agenda and Meeting Notes

Posted by Jeremy Mitchell <mi...@gmail.com>.
Maybe we can put some impact and effort labels on the following tech debt
items:

https://github.com/apache/trafficcontrol/issues?q=is%3Aopen+is%3Aissue+label%3A%22tech+debt%22++-label%3A%22high+impact%22+-label%3A%22medium+impact%22+-label%3A%22low+impact%22

On Tue, Jan 18, 2022 at 9:14 AM Jeremy Mitchell <mi...@gmail.com>
wrote:

> Status of 6.1
>
> On Tue, Jan 11, 2022 at 9:43 AM ocket 8888 <oc...@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.
>>
>

Re: 2022-01-18 TC Working Group Agenda and Meeting Notes

Posted by Jeremy Mitchell <mi...@gmail.com>.
Status of 6.1

On Tue, Jan 11, 2022 at 9:43 AM ocket 8888 <oc...@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.
>