►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200210
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
good
afternoon
evening
and
probably
morning
for
some
of
you
and
welcome
to
another,
take
off
the
kubernetes
released
in
1:18
meeting.
I
am
your
host
for
this
call
and
before
we
get
started
a
new
day,
so
a
new
reminder
that
we
have
a
code
of
conduct
which
essentially
boils
down
to
please
be
nice
to
each
other,
don't
be
a
jerk
and
with
that
before
we
actually
get
started.
A
B
We
are
still
tracking
his
green
hasn't
been
much
changed
since
last
week,
but
there
was
like
one
fairly
big
change
at
all:
I'll
bring
up
so
we're
still
tracking
50
items,
but
one
item
we
dropped
tracking
last
week.
So
there's
a
kept
number
seven,
an
issue
number
785
and
it's
an
issue
for
tracking
graduation
to
beta.
It's
not
like
the
whole
issue
or
the
whole
enhancement.
It's
just
like
going
to
beta
and
they're,
not
gonna
do
that.
This
time
are
out.
There
is
a
related
change
in
another
issue
that
I
forgot
to
drop
in
here.
B
B
The
current
alpha
version
so
go
from
like
a
v1
alpha
1
to
alpha
2,
but
because
that
issue
is
not
graduating
beta,
we're
not
tracking
that
anymore,
so
that
would
have
dropped
us
to
49,
but
there
was
also
a
late-breaking
request
for
exception
last
week
and
you
can
see
that
down
there
number
issue
15
39.
It's
changed
to
a
huge
page
which
is
stable.
B
They're
gonna
make
some
changes
that
shouldn't
be
breaking
any
like
backwards,
compatibility
or
anything.
They
had
most
of
the
work
done
already.
They
just
hadn't
updated
their
Kemp.
Instead
of
making
anyone
there
updating
the
existing
one.
That's
graduated
probably
process
things
we
could
discuss
later
on.
But
because
of
that,
we
are
back
to
50
things
that
we're
tracking
we've
gone
through.
We
started
pinging
everybody
to
remind
them
of
code.
Freeze,
it
looks
like
Doc's
has
done
the
same
for
the
placeholder
PRS,
so
current
status
is
we're
tracking
50
things.
18
will
be
alpha.
A
One
quick
question:
yep
I
feel
like
I
I,
don't
remember
the
name
of
the
person
who
requested
the
inception
for
the
huge
pages,
but
I
think
I
saw
a
comment
from
he/she
day
on
the
C
police,
Channel
and
I.
Think
it
was
something
along
the
lines
of
do.
They
need
to
do
anything
else.
They
should
be
on
set
right,
yeah.
D
Yeah
around
the
enhancement
stuff,
but
I
guess
I,
don't
know
if
we
take
that
in
another
form.
Essentially,
the
confusion
for
the
huge
page
of
stuff
was
around
whether
they
do
updates
to
that
cap
or
create
a
new
one
and
I
think
that
we
should
be
fine
saying
that
if
something
is
like
moving
forward
at
least
something
is
graduated,
then
an
addition
on
top
of
it
should
be
a
new
thing.
Yeah.
B
D
C
D
F
So
we
are
ready,
but
we
were
almost
explode
during
the
night,
because
Bosco's
had
a
really
bad
day
and
our
first
little
one
to
take
care
of
it,
because
the
West
timezone
in
the
u.s.
everybody
sleeping
mode
like
live
was
cops.
I
was
a
result
itself,
so
all
jump
start
to
recover
and
that's
why
master
blocking
we
don't
have
any
failing
jobs.
F
F
There
was
one
petition
of
freaks
opened,
but
I'm
not
sure
if
that
doesn't
fix
the
job,
but
both
of
those
jobs
are
dealing
with
diversification,
so
I
hope
the
next
day
is
that
would
be
fixed.
Could
you
Malta
living
as
well?
Okay,
so
did
you
see
goes
faster
boot?
This
is
really
old,
one
entire.
We
don't
have
been
the
actually
response.
Kyle
provided
him,
I
tried
to
print
them
a
couple
of
times.
F
D
D
It
gets
the
nicest
way
to
put
it
when
cloud
provider
wouldn't
sig
GCP
rolled
under,
they
were
effectively
in
maintenance
mode
before
a
rolling
under
cloud
provider.
So
those
tests
had
no
maintainer
x'
before
and
they're
just
continuing
along
in
the
same
state.
Oh
so
so
I
don't
know
who
you're
trying
to
ping,
but
it's
probably
the
wrong
person.
D
F
Super
super
thanks
for
the
advice
I'm
going
to
ping
teams
after
the
meeting
about
this
one
super
okay,
so
the
master
cereal
is
its
failing
as
well.
So
it's
there's
like
a
wake
that
someone
assigned
Dacian
to
him,
but
there's
no
other
activity
after
this
I
I
hope
that
someone
take
a
look
at
Wiggly.
Okay,
so
a
boutique
of
master
code
entered
a
starter
failing
to
think
today,
two
days
ago,
it's
either
investigation
will
be
like
somebody's
personal
issues.
F
Could
energy
Marcel
2019
we,
this
job
is
still
in
progress.
I
have
their
comment
here.
You
can
say
they
promise
us
not
to
finish
the
job
soon
enough,
so
we
I
don't
consider
that
as
a
blood,
it's
one
and
the
same
windows,
1909
master,
it's
it's
like
failing
as
well.
We
don't
have
any
response.
I've
been
sick,
goose,
see
goodness
thing,
but
it's
quite
new
failure
as
well
in
the
release
missed
a
spot
okay.
So
we
have
this
happy
old,
33
I.
F
This
is
a
sick
release.
Job
I
said
no
as
well,
so
it
seems
that
it's
not
the
invest
case
right
now.
Teams
also
and
other
guys
have
been
notified.
Thanks
about
that,
all
right
for
1.17
blocking,
informing
those
there
are
two
tests
are
failing,
which,
like
the
same
reason
with
mastery
from
subs
as
well.
F
We
have
a
couple
of
flaky
jobs
that
we
have
opened.
The
issues
about
people
are
trying
to
take
little
converse.
Also
I
want
to
mention.
Also
that
recently
we
have
data
our
dogs,
and
we
see
excellent
team-
will
be
this
possible
so
for
their
butts,
butts
blocking
bassam,
its
commercial
brands
so
having
to
tracking
compared
to
the
debt
all
the
flakiness
of
all
the
jobs.
F
Then
we
like
really
hard,
also
I,
ever
also
to
ask
you
guys
that
if
it's
like
a
good
idea
that,
if
we
can
notify,
if
someone
would
have,
will
have
any
flakiness
in
his
PR,
so
he
can
just
make
sure
to
ping
the
shakes
in
our
team.
That
will
help
a
lot,
because
we
are
trying
to
detect
the
flakiness,
and
this
is
really
hard
and
we
can't
do
it
with
tests
great.
F
F
Let
us
note
here
that
is
the
that
was
like
a
course
that
I
was
causing
some
jobs
to
flake
and
it
seems
that
someone
is
working
or
in
ten
days
it's
likely
resolved.
So
the
next
days
we
are
hoping
to
see
less
flakes
Dobbs.
That's
good
news,
also
George
you
best
here,
but
the
most
issues
especially
website
based
also
there.
They
issue
that
were
Tim
serpent
during
the
night,
but
it's
still
open,
but
I
think
that
the
Moscow
she's
fine
now
so
we
could
just
close
it.
It
seems
that
survived
by
himself.
D
First,
one
to
all
of
the
stuff
he
said,
thank
you
for
putting
up
the
presubmit
updates
to
the
CI
signal.
Docks,
I,
sent
an
email
but
I
think
the
subject
is
flaky
tests
that
talks
about
some
of
the
stuff
and
Jordan
and
Ben
have
jumped
on
that.
So
a
lot
of
the
stuff
that
you're
you're,
seeing
flake
wise
is
actually
related
to
infrastructure
and
not
so
much
not
so
much.
The
jobs
themselves
still
keep
an
eye
on
all
the
flakes
again.
D
The
boscoe's
things
should
start
to
settle
out
the
ones
regarding
resource
contention
start
to
settle
out
as
well
yeah
the
container
D
one
that
she
mentioned
to
have
been
to
container
D
one.
That
test
is
new,
so
that's
Tim's
tweaking
that
test
he's
working
on
that
over
the
weekend,
so
that
should
settle
out
soon.
I
think
I
just
saw
a
PR
emerge
for
that,
so
I
think
that's
yeah
I
think
that's
it.
F
A
F
A
A
F
D
F
F
A
All
that's
interesting
always
been
able
to
rerun
jobs.
Let's
be
right,
I
think
that's
him
more
in
the
sick
testing
scope
and
within
this
issue,
what
we
can
do
is
everything
every
single
job
in
first
grade
and
the
like,
he
has
a
property
of
configuration
and
within
the
arguments
it
tells
you
what
and
to
and
how,
how
he
chooses
morning
to
end
jobs
to
run
a
week.
A
Do
one
or
one
of
the
things
that
we
can
do
is
if
we
go
to
the
source
code
and
find
the
actual
end-to-end
jobs
in
in
KK.
If
we
go
to,
if
we
go
to
the
source
code,
if
we,
if
we
with
the
labels
in
the
description
of
it,
we
can
know
whether
a
we
can
over
whether
it
is
actually
testing
what
a
what
it's
supposed
to
be
testing
or,
if
not
and
then
based
on
those
labels,
we
can
either
add
a
bit
of
a
label
to
another
job
2:08
also
in
create.
A
A
Also,
a
font
a
bit
the
the
issue
for
the
boss
cos
failure,
apparently
something
inside
of
Google
broke
and
I.
Don't
think
we're
gonna
get
that
much
more
information
about
it,
but
yeah
seems
to
be
fixed
other
than
that.
Anyone
has
any
comments.
Questions,
suggestions,
criticisms
for
a
foresee,
a
signal
or
relieved
to
see
a
signal.
A
A
H
Good
morning,
everyone,
my
name,
is
John
skarbek,
one
of
the
shadows
for
the
bug
triage
team.
Our
status
this
week
is
green
for
everything
that
we're
tracking
what
a
nice
downward
trend
so
I'm,
not
gonna,
repeat
all
the
numbers
are
listed,
but
for
everything
we're
on
a
nice
downward
trend
for
everything,
there's
a
a
good
minus
Delta
for
all
issues
that
we
are
currently
tracking.
H
I
Hello,
everyone,
so
our
dogs
is
right
now
working
on
tracking
the
enhancement.
So
so
far
we
have
reached
out
to
all
the
enhancements
like
me,
and
my
shadows
have
reached
out
to
all
the
enhancements
seeking
for
a
placeholder
peers
and
we
have
like
almost
like
25
to
30%
of
placeholder
peers
in
place
and
we
are
awaiting
for
the
response
for
the
rest,
yeah
placeholder
peers,
considering
February
28th
as
the
deadline
for
placeholder
peers.
Maybe
from
next
week
we
might
reach
out
to
the
enhancements
owners.
I
Personally
through
slack,
and
apart
from
that,
I
had
a
hard
time.
Syncing
up
release,
1.17
and
master
branch
is
because
the
localization
work
was
carried
out
and
released
1.17,
and
so
it
was
creating
much
conflicts.
So
Jim
from
sick
dogs
has
helped
me
so
luckily,
I
just
say:
I
did
a
hard
reset
between
master
and
released
1.17
branch.
So
we
are
good
right
now,
yeah,
that's
the
update
from
Docs.
I
I
J
Hey
guys,
hey
guys,
sorry,
sorry
trying
to
find
a
mute
button
here
me.
Yes,
okay,
cool,
so
everything
is
green.
With
us,
alpha
3
went,
went
pee
pee,
ours
were
merged
for
both
K
cig
release,
notes,
which
is
a
release,
notes,
draft
and
k,
slash,
release,
save
release,
it
gets
very
confusing,
which
is
the
website
for
low
notes,
so
both
of
those
have
been
merged.
There
were
three
open
issues
from
last
meeting.
Those
have
all
been
closed,
including
the
1.17
known
issues,
release
notes.
So,
though,
that
should
have
been
closed
on
the
117
release.
J
There
is
a
new
118
known
issues
that
needs
to
be
closed
out
once
we
do
a
118
release
as
well,
so
we'll
try
to
figure
out
a
way
to
automate
that,
but
that's
kind
of
the
process
right
now
and
we
are
update.
We
are
running
the
new
released
notes
which
changes
everything
to
kind
and
then
I
think
the
only
other
thing
that
we
have
to
worry
about
is
maybe
get
some
time
Stephen
with
my
team
to
see.
J
D
J
K
L
We
also
start
the
communication
with
the
CNC
F
block
webinar
time
slot
for
the
118
reliefs
I
think
it
will
be
somewhere
in
the
mid
of
April
and
we're
also
going
to
which
odd,
in
the
couple
of
the
next
days,
also
to
see
in
the
f2
scheduler
relief
blocks
and
the
press
embargo,
as
well
as
the
interviews,
the
analyst
pre-pre
fangs
and
the
press,
and
so
on.
So
starting
the
the
comms
working
Sun
swallowing.
D
Anyone
has
any
comments,
questions
suggestions,
so
I
made
the
suggestion
last
cycle
that
do
to
our
miscommunication
with
timelines
and
everything
that
comes
see,
see
the
release,
team
leads
and
sig
chairs
on
all
external
communications.
I,
not
sure
if
I
saw
anything
in
my
mailbox,
but
if
you
have
then
fine,
if
you
haven't
for
the
emails
over
as
well.
M
A
A
N
Okay,
hello,
good
evening,
good
morning,
my
name
is
Carlos,
helping
their
release
branchy
tomorrow,
it's
expected
to
be
cut
the
Alpha
4,
but
we
have
like
a
blocker
issue
that
is
not
fully
fix
it
right
now.
Maybe
Steven
can
give
more
details,
but
this
is
not
building
the
correct
generating
the
correct
tag
for
we
cut
the
release.
D
Yeah,
so
the
I
mean
the
TLDR,
at
least
for
now
is
the
way
that
we
bump
the
build
version.
I
mean
there
are
lots
of
different
things
that
are
intertwined
that
determine
how
we
coalesce
built
version.
If
the
build
version
that
we're
about
to
trigger
in
a
nago
is
behind
the
tag
that's
published
already,
it
will
fail
and
it's
not
happening
on
the
patch
release
branches
right
now,
but
it
is
happening
on
master.
D
D
At
one
more
comment,
Daniel
Daniel
will
be
cutting,
though
alpha
for
release.
Yeah
there
is
hey:
we've
made
him
a
release
manager
associate
as
of
last
week.
Yeah
he's
been
doing
a
lot
of
the
work
that
release
manager
associates
are
tasked
with,
and
we
realized
that
he
wasn't
one
already
so
it
since
Adam,
so
congrats
Daniel.
A
M
Thanks
George
just
ordering
batteries
for
Stevens,
that's
my
main
update
now
I've
drafted
the
mid
release.
Shadow
survey.
I
just
need
to
follow
up
with
the
leads
and
make
sure
that's
okay
to
send
out.
So
that's
to
track
how
everybody's
doing,
in
their
shadow
roles,
making
sure
that
they're
supported
so
I'll
send
that
out
in
the
next
week
or
so,
and
that's
it
for
me
thanks
George
George
thank.
A
You
good
question
last
week,
we
briefly
made
mention
of
an
existing
issue
about
retrospective
for
shadows,
which
is
a
you
know,
essentially
a
retrospective
for
how
well
the
shadowing
is
going
instead
of
how
well
they
release.
Actually,
when
have
you
taken
a
look,
do
you
have
any
comments,
say
thoughts,
I,.
M
Haven't
I
haven't
widely
discussed
it?
My
my
opinion,
is,
we
don't
need
another
meeting
if
we
can
capture
it
in
the
retro,
but
I'm
not
sure
I'm,
not
sure
that
we,
you
know,
I,
think
this
is
a
good
touch
point
for
this
release,
but
if
we
feel
we
need
another
place
to
judge
feedback
or
gauge
feedback,
I
should
say
on
the
on
the
shadows.
We
can
potentially
open
that
up,
but
I'm.
M
You
know,
given
that
we're
adding
the
shadow
survey
that
would
mid
release
I,
think
that'll
be
a
first
indication
of
whether
we
think
we're
support
the
shadows.
Well
enough
and
I
would
encourage
all
the
shadows
to
turn
up
and
voice
their
opinions
in
the
retrospective
as
well
at
this
point,
but
happy
to
discuss.
If
anybody
has
a
interest
in
that
place,
ping
me
okay
sounds.
A
October
milestones
a
alpha
for
release,
we'll
figure
it
out
at
some
point,
hopefully
so
other
than
that
a
code
freeze
a
now
a
from
now
until
they
release
a
code
freeze
every
single
time
time
I
see
any
one
of
you,
I'm
gonna,
I'm
gonna
be
reminding
you.
The
code
freeze
is
coming
at
some
point
today:
I'll
send
out
an
email
and
to
remind
the
rest
of
the
community
that
code
freeze
is
coming
because
code
freeze
is
coming
and
other
than
that
I
don't
have
any
more
updates.
A
A
It
is
detecting
I'll,
send
you
an
invite,
so
you
make
sure
that's
gonna,
be
that's
gonna,
be
part,
one
of
your
celebration
by
the
way,
some
it's
a
multi-day
party,
so
other
than
code
freeze
is
a
other
than
code
freeze.
Coming,
let's
see
what
scalability
has
for
us
and
I'm
just
gonna
read
them
because
I
haven't
seen
them
in
the
way.
So
there
were
some
training
failures
on
of
single
or
desktop
master
scale
correctness
scalability.
You
must
have
released
informing
test,
but
last
ones
are
green
master
scale.
A
Performance
is
screen,
so
it
looks
like
this
may
be
related
to
the
boscoe's
failures.
I
start
a
bunch
of
alerts
and
every
single
one
of
them
was
fading
more
on
stage
related
to
the
infrastructure
and
they
were.
They
were
also
shown
no
for
the
115
and
116
branches,
which
I
don't
think
we
have
merged
anything
super
big
into
those
branches
and
the
next
site.
And
the
next
item
is
all
smaller
scale
hundred
notes.
Tests
are
currently
still
due
to
issues
with
Bosco's.
A
A
Sweet
so
before
we
move
on
to
the
project
bar
a
like
a
drag
couple
issues
that
we
mentioned
a
last
meeting.
If
anybody
is
interested
in
any
of
these,
please
take
a
look,
a
comment.
The
first
one
is
just
handbook
of
dates.
I
tell
me:
I
got
some
notifications
and
probably
some
other
people
tell
as
well,
so
it
just
got
true
handbook
handbook
updates.
A
If
you
have
a
mob,
if
you,
if
not,
then
I
guess,
are
starting
to
do
other
than
that,
a
coronate,
the
a
kubernetes
release
appropriate
cap
and
increase
community
support
window
to
wonder
if
you
have
a.
If
you
have
time,
please
take
a
look
at
those
issues
caps
and
provide
and
give
us
some
feedback,
and
if
everyone
is
cool
with
it,
let's
go
to
the
bar
and
find
some
issues
for
everyone
to
work
on.
Let
me
start
by
sharing
screen.
H
A
Can
we
refresh
the
page
to
make
sure
I
get
the
latest
and
let's
go
with
improv?
Let's
actually
listen
up
with
review
in
progress.
We
have
a
couple
things
in
here
that
information
about
what
color
a
qualifies
for
a
milestone-
and
this
was
mentioned
by
a
bug-
triage
team
just
a
bit
ago
and
Taylor
is
going
to
be
working
with
them
and
investigator
automation
to
facilitate
tracking
spreadsheets.
A
A
So,
let's
think
that
in
progress
is
good
to
go
next
couple
dishes
track
enhancement:
sleep
across
multiple
releases
a
last
week
check
nothing
to
do
for
this
one
we
are
going
to
see
what
happens
is
released
and
then
compare
and
document
reason
for
inclusion
of
a
release
blocking
jobs
they
knew
and
I
are
working
on
this
I
also
being
sassy
a
they
say
signal
channel
to
see
if
more
people
wanted
to
jump
in
on
this,
but
this
one
is
also
still
a
work
in
progress.
So
there
is
not
much
to
say
for
that.
D
A
That
sounds
good
I
like
the
idea
and
I
guess.
That's
one
note:
let's
move
on
to
the
others
document
kubernetes
released
in
google,
hey
I
have
an
open
feel
for
this.
One
and
I'll
send
it
actually
I
just
have
to
come
for
it.
I
need
to
actually
push
it
to
make
the
beer,
but
that
one
is
hey
get
down
across
today.
A
He'll
new
projects,
I
think
lucky
Joe's
left
the
meeting
right,
but
there's
something
about
working
on
project
board
items
and
then
update,
released
him
handbooks,
yeah
I
think
that
people
are
working
on
this
and
I'll
go
to
this
and
update
him.
I
actually
saw
I
was
actually
being
on
a
couple
reviews,
so
I
think
some
of
this
might
be
done.
A
Let's
see
so
ensure
and
RT
live
handbook
includes
an
item
for
adding
release
retrospective
I
also
have
acting
for
a
novel
and
I
just
need
to
push
it.
A
117
release
retrospective
116
release
retrospective
in
kubernetes
Charlie
support
period.
That's
gonna
be
long
term
issues.
Moving
on
to
to
do
tri-split
in
release
catch
a
lot
of
release.
The
playbook
I
commented
on
this.
A
D
A
D
I
might
my
thought
there
is
that
if
they
can
find
a
way
to
if
we
have
headings
within
the
current
timeline,
that's
in
the
readme
right
they
can
link
out
to
a
exploded
version
of
that
timeline.
Right.
That
says
like
okay.
Well,
these
are
the
tasks
that
each
of
these
roles
should
be
doing
at
any
one
time
and
then
those
headings
could
then
lead
to
the
handbook.
I,
don't
know
if
that
is
too
messy,
but
that's
like
when
I
thought.
The
issue
update
that's
the
first
thing
that
came
to
mind
so.
A
C
A
Four
days
ago
and
David
mentioned
that
the
possibility
of
building
a
tool
that
will
essentially
put
together
a
bunch
of
clips
and
we
cool,
then
publish
that
with
a
in
the
seek
released
a
YouTube
playlist
if
anybody
a
especially
anybody
enough
from
the
US,
the
that's
really
that
kind
of
that
I
cannot
in
this
meaning.
If
y'all
have
any
ideas,
if
you
actually
like,
if
you
actually
like
this
proposal,
please
drop
in
here.
A
Put
an
emoji
I'll,
make
sure
to
ask
for
emojis
on
this
issue
afterwards
on
slack,
because
I
feel
like
the
people
who
are
not
able
to
actually
make
this
meeting
a
the
people
who
might
be
a
confined
whom
I
find
this
issue
more
interesting,
might
not
be
able
to
make
this
meeting
so
other
than
that.
Please
put
your
comments,
suggestions
in
in
here
and
moving
on
to
the
doc
handbook.
A
F
F
A
A
A
A
Let's
see,
create
a
shadow
in
retrospective,
like
he
just
mentioned
that,
with
the
meet
with
a
meet
released
survey,
we
might
get
enough
information
to
actually
essentially
close
this
one
out,
but
if
you're
interested
and
if
you're
interested
in
one
and
have
some
other
idea
how
to
get
feedback,
please
drop
your
comments
in
here.
Any
section
leads
a
I
want
to
say.
Please
pass
a.
Please
pass
this
issue
along
to
your
shadows,
a
they
opportunity
to
provide
to
provide
us
with
some
feedback,
handling
the
exceptions,
demo,
files.
A
A
Okay,
so
currently,
then,
has
mostly
for
police
team
crates
and
exceptions,
yellow
failed
to
capture
exceptions
for
the
current
release
cycle.
The
idea
was
to
eventually
have
a
told,
the
all
consumed
this
and
do
something
I'm
thinking
that
we
can
just
leave
it
in
the
backlog
for
now
and
yeah.
D
I
think
we
were
talking
about
leaving
oh
yeah.
Okay,
it
doesn't
know
that
long,
yeah,
I,
don't
know
what
we
want
to
do
with
that
and
I
think
that's
still
true,
which
is
why
we
moved
it
to
the
backlog.
Yeah.
A
F
I
think
this
is
the
one
actually
I
spoke
with
a
guy,
remember
his
name
alright,
so
he
was
tracking
these
tubes
open
lab.
This
is
this
right,
yeah
yeah,
so
I'm
waiting
actually
for
some
results,
and
he
updated
me
for
taste,
quality
and
told
me
that
the
job
start
passing,
but
he's
good
to
update
this
once
everything
stabilized.
F
F
A
F
Actually
able
to
update
the
issue
and
maybe
we'll
have
to
include
open,
lab
dashboards
because
there's
another
link
to
that,
so
it's
just
detect
our
pieces
of
test
code
as
well,
but
I.
Don't
think
this
is
a
good
idea
right
now,
but
I'm
going
to
have
some
kind
of
conversation
with
him.
So
I
want
to
take
the.
A
Depending
on
whatever
updates
you
get,
we
can
revisit
this
issue
later
right
now
we
were
a
since
this
issue
was
created.
We
were
just
waiting
on
an
update
to
see
if
there
was
any
more
work
to
be
done
and
I
guess
we're
still
at
that
point
and
I
guess
next
issue
create
a
shadowing
template
for
handbooks
and.
A
Again,
a
this
issue
already
linked
to
it
in
the
notes,
but
if
you're
interested
and
if
you
do
have
any
feedback,
please
got
true
increase
cover
Navy
support
window
to
wear
to
one
year.
The
next
one
is
for
me
and
my
shadows
and
the
last
one
is
as
I
don't
know,
procedure
for
jobs
entering
and
leaving
blocking,
and
we
are
putting
that
in
the
backlog
until
we
figure
out
what
to
do
with
the
CA
signals
or
project
from
seek
release.
So
first
station
create
a
shadowing
template
for
all
hand,
books.
A
Okay,
so
provision
in
this
the
meet
release
or
be
a
waiting
to
get
more
information
from
it
to
see.
There
is
anything
else
we
need
to
do
on
this
issue:
testing
for
countries.
This
is
a
mellow
another
request
for
comments.
He-
and
this
is
this-
was
part
of
the
really
a.
This
was
one
of
the
action
items
from
the
116
release
retrospective
I
believe,
if
you
are
a
funny,
buddy
is
interested
in
CI
or
testing
from
please
drop
by
they
throw
somebody
throw
some
ideas.
If
something
was
something
hasn't
been
mentioning
here
already
I.
F
Don't
think
that
it's
going
to
work
right,
I,
don't
think
that
this
infra
they
want
to
freeze
actually
the
way
how
testing
for
a
team
is
collaborative
to
their
code.
If
they
do
some
changes
that
are
like
breaking
sages,
the
they
actually
are
trying
to
deprecate
their
stuff
first
and
give
additions
of
six
month
until
the
new
course
will
be
updated.
So
I
don't
think
that
tests
infra
will
actually
break
something
ready
for
sexual.
If
it's
not
a
mistake
right.
L
D
So
yeah,
so
we
keep
going
back
and
forth
on
this
one
and
the
I
don't
know
if
it's
at
the
bottom
already,
but
I
think
essentially
what
I've
said
on
a
few
meetings
is
that
they
will
not
do
anything
until
we
tighten
this
up.
If
this
is
something
that
we
want
to
do,
we
have
to
determine
what
the
scope
of
fries
means
for
them
right.
A
So,
in
order
to
this
issue
has
been
open
for
a
while,
and
even
the
discussion
is
the
discussion
it
goes
way
back
before
they
before
I
created
this
issue,
a
for
the
sake
of
my
having
an
issue
that
is
open
for
the
TA
until
the
end
of
time.
What
would
you
all
think,
would
it
be
reasonable
to
ask
the
CIA
signal
team
to
take
all
day
to
take
a
look
at
this
and
chat
with
the
seed
release
chairs
if
there
is
anything
that
is
that
we
still
need
for
stability,
yeah.
C
E
F
D
F
F
A
Referred
to
go
to
the
cig
testing
meeting
I,
please
do
take
it.
Take
some
time.
I
know,
there's
a
clay,
there's
a
lot
wood
and
please
take
some
time
to
go
to
this
issue.
Actually,
most
of
these
called
most
of
these
comments
were
a
are
based
on
conversation.
I
had
a
last
release
with
cig
testing,
so
a
trick
converse
a
they
out
of
three
conversations
and
we
had
about
different
possibilities
for
trying
to
enhance
the
stability
of
testing
from
during
during
the
more
delicate
parts
of
their
release.
A
Anko
a
all
day,
all
the
information
that
I
thought
was
the
most
important
I
try
to
document
a
documentary
in
here.
So
take
a
look
at
it.
If
anything
sounds
interesting,
if
anything
sounds
useful,
things
have
changed
a
good
amount
since
a
since
I
brought
this,
but
yeah.
If
you
can
absolutely
absolutely
I,
will
be
good.
Okay,
thank
you
so
much
and
the
next
one
I
don't
think
there
has
been
any
comments.
I,
oh,
never
mind.
A
A
A
Will
it
be
recently
and
I
think
this
is
a
question
for
you
Stephen?
It
will
be
reasonable
for
us,
a
signal
released
him
to
us
for
CN
CF
resources
to
a
one,
more
scalability
jobs
or
she
or
should
we
just
a
world
right
now?
Well,
a
way
I
guess
more
wait
for
a
for
them
to
speed
a
to
speed
up
their
test.
D
So
one:
where
do
you
the
tests
run
right?
If
the
tests
are
running
on
Google
infrastructure,
then
you
know,
then
we're
a
little
stuck
there
right
and
they
almost
definitely
run
on
Google
infrastructure
right.
So
that's
the
first
part
of
it.
Do
we
think
we
could
get
resources
for
running
scalability
tests
on
kubernetes
infrastructure?
D
Yes,
probably
don't
quote
me
on
it,
don't
record
me
wait,
but
I
mean,
but
the
bigger
part
of
this
is
is.
Is
that
we're
on
Google
infrastructure
right
now
so
as
to
see
is
if
the
scalability
tests
were
to
move,
then
that
could
be
a
possibility,
but
I
think
in
the
meantime,
we're
stuck
the
I
mean
the
bigger
problem
is
that
we
don't
know
what
not
not
enough
resources
means
right.
D
A
So
things
that
we
could
do
to
get
on
and
get
an
answer
is
a
catch
up
with
six
scalability
to
see
if
we
can
get
some
ballpark
o
resources
and
with
the
gates
working
group
to
see
if
we,
okay,
I,
guess
gates
working
group
and
scalability
to
see
if
we
could
actually
try
an
a
moat
or
build
some
testing.
Cn
CF
infrastructure.