►
From YouTube: k8s 1.16 - Week 9 - Release Team Meeting 20190828
Description
Release details: http://bit.ly/k8s116
A
In
recording
hello
and
welcome
to
week,
9
burn
down
on
Wednesday
August
28th.
This
is
the
1/16
release.
Welcome
everybody,
it's
lovely
to
see
everybody's
faces
and
people
are
still
rolling
in
while
they
are
doing
that.
Please
take
a
moment
to
add
your
name
to
the
attendees
list.
If
you
are
here
with
your
Associated
role
and
if
anyone
would
love
to
volunteer
to
be
note-taker,
I
would
be
very
appreciative.
Thank
you
very
much
lazy
agenda
link,
Thank
You
Gwen.
That's
the
old
agenda.
A
We
will
get
it
fixed
up
and
live
live
commentary
here
there
we
go
so
this
meeting
is
being
recorded.
It
will
be
posted
to
YouTube
after
this
so
reminder
that
all
these
conversations
fall
under
the
kubernetes
code
of
conduct,
which
states
that
you
must
be
excellent
to
each
other,
and
we
all
adhere
to
that
and
appreciate
your
adherence.
Today
we
have
a
packed
agenda.
It
looks
like
there
is
a
lot
of
good
news
in
the
agenda
as
I
was
reading
through
it.
A
So
I'm
excited
to
get
through
all
the
updates
and
hear
where
people
are
in
all
their
associative
roles
and
we
are
like
20,
maybe
17,
18
hours
out
from
burn
down
sorry
code.
Freeze
tomorrow's
exciting
times
in
the
release,
so
to
kick
it
off.
I
will
pass
it
to
enhancements
for
an
update
with
Kendrick.
A
A
B
Well
did
everything
for
the
last
stuff
he
just
basically
competent
on
all
the
issues
or
sorry,
PRS
and
stuff.
It
was
issues
to
get
them
into
enhancements
for
the
KK
like
PRS
and
such
so
he
did
that
and
that's
really
all
I
know
right
now.
Okay,.
A
B
A
What
percentage
is
still
open
today
and
then
I
will
touch
base
with
everybody
in
the
morning?
So
if
you
can
have
Kendrick
throw
update
or
if
you
get,
the
information
fill
three
to
three
I
just
want
to
look
objectively
at
what
percentage
were
actually
looking
at
that
opposed
a
day
and
a
half
out
from
code
freeze,
because
also
you
know,
we
need
to
monitor
the
exception
process
as
well.
There
may
be
some
exceptions
coming
in
yeah.
C
B
A
B
D
E
I,
don't
but
I
have
a
lot
of
cool
stuff
to
share
with
y'all
there's
also
a
ton
of
boards
on,
but
I
guess,
I'm
gonna
try
to
get
you
all
through
this
as
fast
and
nicely
as
possible.
So
first
off
see
a
signal
report.
Please
check
it
out.
It
was
written
by
nickel
a
by
Nicolas
my
Nicholas,
this
time.
If
you
want
to
get
caught
up
on
everything,
that's
been
going
on
on
the
kubernetes
on
the
cover
native
side,
especially
the
things
are
broke.
E
E
Then
1:16
in
the
1:16
informing
dashboard
does
not
look
the
same
as
the
as
the
current
master
informing
dashboard,
especially
we
have
a
couple
cubed
me
a
cube
admin
kind
of
jobs
that
we
need,
that
we
need
to
port
and
they
cube
the
cube
at
mean
my
dinners
have.
It
seems
that
we
have
an
open.
They
have
an
open
PR
on
kinder
to
watch
it
to
actually
get
the
ball
to
get.
The
ball
rolling,
see
a
signal,
a
signal,
wise
we're,
gonna
work
closely
with
them
and
see.
E
E
We
need
to
you
know
we
need
to
start
arguing
is
called
discussing
on
the
criteria
we
need
to
use
to
promote
jobs
from
from
anywhere
in
death
grid,
to
release
put
it
where
lease
blocking
police,
informing
I
propose
a
I
to
a
tree
out
that
way,
I
drew
out
the
plans
for
a
fried
unicorn
in
there.
If
you
wanna,
if
you
want
to
read
it,
provide
a
provide
some
feedback,
but
the.
E
Is
all
that
everything
in
desparate
everything?
Every
single
test
is
in
a
way
replicated
between
the
audience
IgG
and
they
seek
released
dashboards.
You
know,
if
you
want
to
run
a
test
of
whether
tobacco
can
create.
You
can
create
a
pop
in
that
test
is
exist
in
the
60
Li
dashboard,
and
it
also
exists
somewhere
in
the
secret
list
dashboard.
So
we
just
a
so.
E
G
So
I
didn't
get
to
go
through
your
proposal
just
yet,
but
I
think
that,
if
we're
so
now
that
Josh's
dock
has
landed
I,
that's
part
of
what
I
wanted
to
happen.
First
now
the
Josh's
sock
is
landed.
I
think
that
we
have
enough
information
to
build
a
to
build
like
a
github
template
for
requests
for
master
blocking
jobs.
I
think
that
one
of
the
biggest
problems
that
we
have
is
that
someone
can
arbitrarily
promote
a
job
to
master
blocking
or
release
branch
blocking
without
any
without
any
intervention
from
us.
G
So
I
think
that
part
of
what
I
would
like
to
do
is
move
us
to
kind
of
a
directory
structure
where
we
have
kubernetes,
like
jobs,
kubernetes
and
informing
and
blocking
and
informing
and
blocking
stay
under
the
owners
file
for
cig
release.
So
if
you
want
to
bring
your
job
into
into
blocking,
you
are
basically
saying
that
you're
going
to
bring
your
job
under
sink
releases
purview
as
well
right
that
way.
We
have
that
way.
We
are
able
to
manipulate
they
the
annotations
as
we
need
to.
G
H
E
We'll
make
sure
to
bring
as
many
people
as
possible
to
get
to
get
coverage
and
get
good
feedback
to
stiffen
severe
stephenson
yeah.
Definitely,
that's
also
one
of
the
things
that
we
want
to
make
sure
that
doesn't
happen
again,
people
just
promoting
just
without
anyone
else,
knowing
whether
they're
good
or
what
they
do
for
that
matter
and
I
guess
that's
it
for
the
big
to-do
items
in
they
see
a
signal
world
now
on
to
actual
jobs.
E
So
currently
in
case
you
didn't
already
check
it
out
yeah
right
now
we
are
labeling
everything
as
green,
so
muster
a
master
blocking,
there's
nothing
failing
at
least
last
time.
Last
time,
I
check.
There
are
some
flakes
we're
just
gonna
a
same
as
usual.
We're
just
gonna
keep
an
eye
on
them,
see
if
any.
E
If
anything
funny
comes
up,
a
the
one
thing
I
do
want
to
bring
up
is
that
the
fix
for
the
IPA
for
the
Canada
for
the
ipv6
for
setting
up
a
for
testing
ipv6
a
finally
landed
yesterday
after
many
many
hours
so
now
and
now
a
lot
of
people
can
actually
merge
their
peers.
You
know
within
a
reasonably
within
a
reasonable
time
frame,
as
for
the
freaking
jobs,
I'm,
adding
a
new
section
at
the
bottom
of
at
the
bottom
of
my
update.
E
If
you
look
at
towards
the
bottom,
there's
flaky
jobs
involved
and
116
walking,
I'm
marrying,
there's
some
statistics,
so
all
of
you
can
see
how
flaky
the
flaky
flaky
jobs
have
been,
and
we
can.
We
can
continue
sharing
this
information
and
with
more
time
discuss
which
jobs
should
be.
We
could
probably
be
demoted
from
from
Berlin's
blocking
until
we
get
more
until
we
do
something
to
improve
the
flakiness
of
them,
but
TLDR
muster
blocking
things
are
good.
At
least
right
now
master
informing
a
comfort.
They
complain
the.
E
The
periodic,
a
conformance
tests
are
not
actually
been
won
periodically,
but
we'll
keep
you
updated
on
that
and
the
two
failures
on
mastering
forming
right
now
are
the
devs
and
rpms,
and
at
this
point
is
cutting
at
this
point,
is
kind
of.
There
are
many
things
going
there.
Many
things
happening
a
lot
of
a
lot
of
work,
that's
being
done.
If
Stephen
wants
to
give
an
update,
I'll
give
him
a
I'll
given
the
space,
but
I
think
say:
things
are
happening.
Yeah.
G
Sure
sit
so
so
there
was
an
issue
with
the
basically
the
job
runs
in
docker,
so
in
CI
it
it
also
runs
interactively.
So
we
had
to
do
some
tweaks
to
allow
it
to
run
docker
and
docker
and
and
non
interactively
when
it
is
not
when
it's
not
able
to
detect
the
tty.
So
there's
some
fixes
there.
I
also
wanted
to
make
sure
that
the
the
docker
container
is
not
running
as
root
or
the
user
within
the
container
is
not
root.
So
some
fixes
to
the
user
and
group
IDs.
G
Those
six
is
now
break
different
things,
which
are
essentially
like
some
directory
permissions,
so
I'm
tracking
that
stuff
down
right
now,
but
the
jobs
are
actually
like
running
now
and
giving
me
different
issues
so
I'm
pretty
happy
about
that.
I
also
increased
the
frequency
of
the
periodic
sfrom
for
hours
to
30
minutes,
because
it's
kind
of
impossible
to
debug
and
fix
things
and
get
some
sort
of
signal
within
every
four
hours.
So
so
until
these
jobs
are
cleaned
up,
they'll
run
every
30
minutes
and
once
that's
fixed,
I'll
I'll,
pull
that
so
progress,
yeah
lots.
E
We
need
to
tackle,
for
we
re
actually
need
to
create
a
path
for
people
for
people
to
not
only
create
jobs,
not
only
to
promote
jobs
to
where
he's
blocking
and
releasing
for
me,
but
also
to
create
the
jobs
whenever,
whenever
a
new
branch,
a
new
branch
is
created
in
the
past.
So
so
what
is
a?
What
is
currently
in
1/16
informing
it?
That
has
been
the
same
case
for
the
last
handful,
the
last
couple
of
produces
it,
the
only
the
only
the
only
job
that
has
been
that
has
been
born
in
USA.
E
What
is
it
you
ke?
A
UK
come
for
a
conformance
conformance
with
a
independent
or
whatever,
whatever
is
actually
sitting
on
mass
room
for
me,
so
that
another
to
do
is
to
actually
figure
out
a
good
way
to
a
I
guess
copy
and
paste
what
a
what
is
in
mastering
form
into
one
dot,
X
informing
for
now
and
for
the
future.
So.
G
H
G
G
Before
we
get
into
the
next
branch
cut,
so
we
have
some
time,
but
we
need
to
make
sure
those
annotations
are
on,
and
we
also
need
to
make
sure
that
the
the
configure
Forker
code
is
looking
through
the
correct
directories
for
that
stuff.
There's
some
discussion
happening
right
now,
where
we're
talking
about
what
to
do
with
the
branch's
4k
release
themselves
and
I.
G
H
I
E
Yeah,
so
I
guess
for
the
audience
the
DL
VR
is
we're
going
to
discuss
this
we're
going
to
we're
going
to
work
hard
of
making
all
of
this
easier
and
better
documented
for
future
releases
and
the
last.
The
last
thing
my
update
is:
release
miscellaneous
a
it's
also
work.
It's
also
working.
It's
looking
good
and
I.
Guess
with
that
I'll
just
end
and
keep
the
and
give
the
floor
for
anyone.
That
has
any
additional
comments,
questions
or
criticisms.
A
Oh
George
I
have
a
couple
of
questions
and
and
probably
a
statement
or
two.
The
first
thing
is
I'm,
trying
to
understand
the
value
of
the
flaky
job
section
and
one
so
just
I'm
trying
to
bubble
up
information
that
we
can
action
in
this
call
specifically
so
I
mean
this
is
good
to
have
visibility,
but
would
you
suggest
you
know
taking
the
top
three
or
four
high
percentage
you
know
of
failures?
I
sees
you
know:
GCE
cuz,
Cates
Peter
slow,
twenty
percent
failure
in
the
past
seven
days.
A
Do
we
want
to
just
take
the
top
n
and
have
the
CI
signal
team?
Do
some
investigation
as
to
what's
causing
that
n
number
of
failures?
If
it's
just
hey,
this
is
timing
out
nine
times
out
of
ten
or
whatever
twenty
percent
of
the
time,
and
then
we
know
we
could
walk
off
something
larger
like
what
errand
stuck
his
head
in
and
said
he's
doing
with
della
drone
and
try
and
split
out
the
large
jobs
that
are
genuine.
You
know
usually,
timing
out,
mm-hmm
yeah.
A
So
I,
don't
know
you
know
the
twenty
or
thirty
percent.
It
would
be
interesting
to
come
up
with
just
a
very
lightweight
action
plan
and
we
put
in
a
ticket
to
say
hey.
This
is
timing
out
twenty
nine
percent
of
the
time
we
need
to
split
up
these
jobs.
Can
somebody
split
this
out
in
two
separate
things
and
you
know
remesh
earth
at
at
in
velodrome
I'm,
just
trying
to
you
know
I'm
not
trying
to
give
you
more
work
to
do,
but
I
think
genuine,
D
flaking.
The
number
of
the
flights
here
looks
concerning.
E
So
yeah
I'll
be
helping
you
and
everyone
else,
so
we
can,
we
can
discuss.
It
is
one
further
because,
especially
the
flaking
these
jobs.
It's
gonna
be
a
lot
more
interesting
because
there's
not
something
per
se
he's
wrong
on
the
job.
There's
a
lot
of
minor
things
are
gone
wrong,
so
the
flaking
this
is
gonna,
be
more
interesting
than
and
deflating
some
other
jobs.
Yeah.
A
I
mean
even
if
you
just
take
one
and
we
come
up
with
a
plan,
I
think
that's
a
forward
progress,
and
if
it's
going
back
to
test
infer
and
saying
you
know,
twenty
percent
of
these
runs
are
failing.
Due
to
this
unknown
reason,
we
could
have
the
test
in
four
team
runoff
and
figure
out
how
to
make
that
piece
more
stable,
because
we
might
actually
fix
a
lot
of
the
jobs
with
the
same
fix.
E
A
Hopefully,
cautiously
optimistic
other
thing
that
is
interesting
and
I
think
this
is
just
a
point
to
understand
here.
So
first
point
is
Kara
vacation,
the
kind
I
pv6
master
parallel
jobs
has
nothing
to
do
with
dual-stack.
It's
actually
they've
added
test
coverage
to
a
feature
that
went
into
alpha,
which
is
pure
ipv6
clusters
in
1.9.
A
What
was
happening
here
was
they
went
off
to
actually
add
ipv6
support
to
kind
because
they
had
no
way
to
test
it
in
1.9.
That
feature
is
still
alpha.
I
went
and
just
checked
the
enhancements
and
I
was
aware
of
this
already,
but
moving
they
wanted
to
move
ipv6
to
beta
and
that
got
dropped.
So
this
test
I
still
genuinely
questioned
whether
it
should
be
in
blocking
I
like
that.
It
is
there
and
it
is
now
green.
A
Obviously,
but
I
know,
we've
talked
about
it
in
the
context
of
dual
stack:
it's
actually
not
chill
stack
ipv6
only,
which
is
for
most
people
get
less
useful.
At
this
point,
not
many
people
are
running.
Ipv6
only
has
been
an
alpha
since
1.9,
so
I
think.
A
E
E
The
job
is
that
I
think
it's
definitely
useful.
So
in
the
worst
case
we
just
we
just
we
could
move
it,
move
it
way
to
release
informing
and
Joe's
a
pass
down.
Please
no.
It
just
have
a
pass
on
this
knowledge
on
highly
on.
You
know
this
feature.
This
feature
is
something
that
it's
plan
to
move
on
tomato
and
feature
releases,
so
take
everything
with
a
grain
of
salt
but
and
yeah
I
did
I
like
the
electively
I'd
like
to
look
into
it.
So
I
can.
C
A
A
All
right,
well
I'll,
put
together
a
ticket
with
that
and
we
can.
We
can
get
the
folks
involved
was
it
was
Ben
Ben
elder
the
person
responsible
for
fixing
the
test,
so
I
haven't
looked
at
that
specific
sex
unbundle
Antonia,
okay!
Well,
we
can
we'll
go
talk
to
him
because
then
in
117,
assuming
it
goes
to
beta,
we
can
just
promote
it
to
blocking.
E
A
Now
the
the
final
thing
people
are
going
to
ask
me
is
well:
where
is
the
adjuster
tests,
so
I'm
just
popping
it
in
here
now?
This
is
the
other
question.
Now
now
we
have
the
dual
stack
tests
up
and
running.
There
is
one
more
piece
to
be
merged,
which
is
a
me
to
e
test
for
the
phase
two
piece,
so
we
actually
have
test
coverage
now
for
that
we've
had
what
two
green
runs.
A
A
Right
well,
I'll
go
and
do
my
homework
on
the
process
and
see
if
I
can
run
it
through.
There
I
think
the
interesting
thing
and
I
don't
know
right
now.
What
is
our
stance
on
alpha
features?
Should
they
be
in
blocking?
Because
this
is
an
alpha
status
feature?
No,
which
means
you
need
to
opt
in.
You
need
to
opt
in
with
flags
to
have
this
functionality,
so
it
would
have
been
informing
or
not
on
anything,
an
alpha
feature.
I.
H
G
Also,
like
do
the
so
there's
like
the
features
that
go
where
features
that
are
some
features
that
are
alpha
land
in
and
but
not
all
do
right.
So
is
that
checking
for
only
features
that
are
flagged
in
features
that
go
or
is
it
checking
for
any
random
alpha
thing
right?
We
need
to
figure
that
out.
I
also
have
questions
which
is
for
a
different
meeting
about
what
we
should
do
around
what
we
like
how
critical
we
consider
jobs
running
on
certain
I,
as
is
to
master
blocking
master,
informing
right,
like
this
isn't
like
I'm.
A
A
Totally
and
I
mean
in
this
case
the
not
all
clouds
support
ipv6,
so
we
had
to
run
it
on
the
azure
cloud
because
we
could
actually
test
the
feature
end-to-end.
So
we
could.
We
could
discuss
that
as
well.
So
what
is
the
next
steps
me
just
raising
your
ticket
about
what
board
this
should
land
on
and
we
can
figure
out
if
it
lends
an
alpha
I
think
the
only
question
I
have
for
alpha
it
does
that,
because
this
has
to
run
against
specific
infrastructure
that
supports
dual
stack.
J
H
Way
on
it,
yeah
I
mean
and
I
can
I
can
throw
cut
some
of
this,
so
so
to
understand
the
reasoning.
So
this
would
this
would
land
in
informing
for
a
number
of
reasons
number
one
is.
It
is
running
on
a
specific
cloud:
okay,
it's
that
would
put
it
in
for
me.
Second
only
runs
once
every
12
hours
yep
and
we're
requiring
stuff
in
blocking
to
run
at
least
once
every
three
hours.
If
we're
in
the
process
of
delaying
the
release,
we
can
get
signal
within
24
hours.
I.
H
G
F
A
A
D
Hey
everyone
so
today,
sadly,
it
might
be
a
little
bit
longer,
but
let's
get
started
regarding
our
stateÃs,
never
say,
yellow
or
maybe
we
can
even
reach
green,
the
Pentagon,
but
we
decided
having
some
issues
to
start
with
some
numbers
non-test
and
non
flake
issues.
Here
is
the
counted
45,
which
is
great
and
21
less
than
we
had
to
do
last
meeting
and
to
expand
a
little
bit.
I
have
updated
a
template
and
now
I
also
record
what
is
the
number
of
critical
urgent,
a
deportation
issues?
We
got
a
critical
Madrid.
D
Do
we
have
on
your
shop
and
I'm?
Not
sure
really
what
to
do
with
that?
One,
because
if
he
has
but
the
issue
is
five,
nine
eight
four
eight
and
it
has
bought
priority
critical
urgent
in
priority
partisan
labels.
I
guess
the
one
should
go,
but
we
have
tried
to
ping
the
issue
and
we
have
got
no
response.
You
should
like
called
from
February
2018,
and
he
also
we
try
to
ping,
goes
right
and
create
a
column
and
said
that
the
issue
is
critical
in
terms
of
safety.
D
A
I
would
say
just
for
that
one
specifically,
if
you
take
that
square
which
is
critical
and
urgent.
This
is
critical,
but
not
urgent,
given
the
factor
and
then
that
statement
from
Clayton
specifically
makes
me
think
it's
important
to
do
it's
going
to
require
considerable
reconstruction
of
kubernetes.
That's
going
to
take
many
releases
and
there's
going
to
be
need
to
be
many
community
members
bought
into
it.
Given.
G
G
A
D
A
D
I'm
excited
okay,
okay,
yeah,
so
regarding
priority
important
soon
we
have
23
for
the
record
now
to
PRS.
We
have
49.
This
is
two
more
than
the
last
meeting,
but
this
is
totally
okay.
We
consider
if
you're
approaching
the
code
freeze,
but
we
have
one
critical
merchant,
PR
and
similar
to
be
interested
to
see.
This
is
a
few
months
older,
but
it
is
close
to
bang
budget
and
we
just
need
the
final
approval.
D
D
C
D
So,
and
this
is
it
regarding
importance
on
PRS,
we
are
right
towards
it
all,
so
all
interest
we
have
for
the
milestone
is
that
57,
and
this
is
22
less
than
we
had
at
the
last
meeting,
which
is
great.
Now
we
on
the
last
meeting,
we
have
talked
a
little
bit
about
having
a
new
metrics
for
reporting,
the
state
to
say
and
measuring.
D
How
are
we
standing
and
we
have
talked
like
the
bachelors
team
and
have
decided
that
we
need
to
change
it
because
chemical
metrics,
based
on
the
number
of
open
issues,
this
PR
is
not
really
good
because
it
changes
a
cycle
to
cycle
and
depends
on
manufactures
that
we
really
get
changed.
So
we
thought
that
it
might
be
a
good
idea
to
have
a
metric
of
release
rocking
issues
now
how
how
that
would
work
like
at
the
beginning
of
the
cycle.
D
The
bacteria's
thing
could
families
with
potential
release
blocking
issues
and
ensure
that
they
are
active
and
that
it
is
somehow
target
is
released
working.
We
might
use
priority
critical
object
now,
as
it
has
been
mentioning
that
label
might
be
a
little
bit
broken,
but
this
is
something
we
might
try
to
fix
in
this
or
the
in
the
next
cycles,
or
we
maybe
make
an
introduce
a
new
label
to
annotate
the
release
blocking
issue
and
to
make
sure
that
it
is
fixed
at
the
time.
D
D
We
have
more
of
them,
but
in
the
mid
cycle
we
should
monitor
debt.
Those
are
getting
close
to
bank
merger
that
close
it
and
try
to
poke
around
six
and
outers
that
we
should
take
care
of
that
and
then
for
two
weeks
until
the
code
freeze,
chanak
to
red,
if
you
have
any
critical,
are
traditional,
because
that
should
be
fixity
that
I
frame
already-
and
this
is
what
he
had
as
idea
in
the
action
item
of
this-
is
probably
the
wrong
head
book
as
we
decide
on.
A
Excellent
I
mean
this
level
of
detail
was
much
more
interesting
to
me,
given
that
you
bubbled
up
things
that
were
labeled
critical,
urgent
on
the
issues
and
the
PR
side,
so
I
think
ad
at
a
minimum.
We
need
to
know
how
they're
trending
and
where
they're
at,
because
we
consider
them
release
blocking
I,
just
don't
know
if
the
next
step
down,
which
is
important
soon,
how
we
need
to
sub
triage.
That
is
it
yes,
this
is
going
in
this
release
and
hence
this
critical
urgent
or
no.
This
is
not
going
in
this
release.
A
Hence
important
soon.
It's
kind
of,
like
you
know,
I'm
thinking
about
the
hospital
scene
in
the
ER
who
gets
to
go
into
the
hospital
and
who
has
to
wait
out
and
who's
in
line.
And
how
do
you
restructure
that
line,
because
it's
clear
to
me
that
there's
always
going
to
be
a
line.
So
how
do
we
selectively
say
we
need
this
fix
and
if
you're
not
committing
to
this
fix
in
this
release,
then
you
get
out
of
the
pile.
A
And
then
you
come
back
in
the
pile
when
we
go
into
the
next
release,
because
it
seems
you're
suffering
from
a
lot
of
orphans,
long
hanging
orphans,
which
people
have
raised
things
and
then
you
know
never
updated
or
there's
very
election.
You
spend
a
lot
of
time
worrying
about
things
when
they're
not
actually
actionable
anymore.
G
So
I
think
that
the
the
critical
urgent
stuff
is
critical,
urgent
right,
I
think
that
the
combination
of
it
being
critical,
urgent
and
being
in
the
milestone
means
it
should
be
something
that
you
consider
trying
to
get
into
the
milestone
or
poking
the
person.
Until
we
get
into
the
milestone
important
soon,
I
mean
it.
It
honestly
depends
right.
This
also
depends,
if,
like
the
issues
are
even
prioritized
properly
great,
has
a
sig
gotten
to
them
and
made
sure
they're
prioritized
properly.
How
much
of
that?
G
G
Prioritize
them
correctly
so
yeah
what
I'm?
What
I'm
asking
is?
Should
that
be
our
job
and
I
think
the
answer
is
no.
We
should
not
have
to
maintain
all
of
the
issues
and
KK
for
the
sake
of
for
the
sake
of
the
entire
project
right.
This
is
a
this
is
a
job
for
the
entire
project
right.
So,
if
we're,
if
we're
finding
friction
at
code
freeze,
this
needs
to
be
raised.
Yes,.
G
D
Don't
and
almost
everything
is
going,
C
is
going
to
disappear
like
okay.
We
think
this
is
important,
so
we
should
take
that
on
a
level
of
a
project.
It
may
be
some
faux
document
about
this
priority
and
maybe
we'll
some
help
or
something
like
that.
That
is
okay.
We
want
that
to
improve,
but
it
is
a
little
bit
problem
how
to
improve,
because
we,
everyone
still
has
a
lot
of
work,
and
this
is
getting
like
cumulative
scares.
A
lot
of
issues
at
PRS
and
prioritizing
is
a
hard
job,
so
yeah.
G
G
I
D
G
G
A
Yeah
I
think
at
this
point
yeah,
let's
just
any
interest
in
moving
this
along
I.
Think
just
this
level
of
detail
is
good
good.
For
me,
it
helps
me
make
a
decision
as
to
the
status,
so
thank
you
for
doing
doing
that.
I
think
we
don't
have
to
make
too
many
knee-jerk
changes
at
the
moment,
this
level
of
detail
and
knowing
what
we
have
in
break
down
is
good
enough.
D
D
D
Yeah,
so
I
have
one
more
question
quickly.
It
is
also
we
start
with
the
code
freeze,
which
is
tomorrow
Pacific
time
of
the
day.
So
what
we
are
going
to
do
with
issue
is
NPR's
like
when
do
we
want
to
start
moving
them
out
of
the
milestone
to
be
one,
even
to
do
that,
so
we
cyclist
with
adjustments
to
make
sure
that
important
things
get
in
I.
A
G
G
If
you
think
it
should
have
been
in
the
last
milestone
and
it's
about
to
be
finished,
then
cool,
we
can
add
it
back,
but
also
we
have
like
the
milestone,
applier
stuff
that
happens
to
that
only
applies
to
the
PRS,
but
if
it
is,
we
haven't
so
right
now
the
milestone
apply
are
set
so
that
any
issue
that
merges
right
now
will
merge
into
will
get
get
applied
to
the
the
116
milestone
right
and
that
will
be
in
place
until
I.
Guess
we
cut
116.
G
G
If
you
think
that
your
thing
should
be
in
milestone
in
117-
and
you
have
come
back
and
triaged
it
again,
then
fine,
but
we
we
shouldn't
because
like
at,
is
moving
essentially
kicking.
The
can
to
the
next
milestone
means
that
the
next
person
who
is
doing
bug
triage
will
have
to
look
at
these
things
again.
Yes,.
D
F
Hello
everyone
so
for
this
week
for
dogs,
we
don't
have
much
updates.
We
have
a
deadline
coming
up
next
week,
Tuesday
right
now,
we
have
about
16
PRS
that
need
to
be
ready
for
review
before
set
about
sold.
I
was
living
towards
green,
but
just
to
be
on
the
safe
side.
I
just
changed,
yellow
I
expect
that
the
same
she
be
able
to
meet
the
deadlines,
and
we
should
be
grateful
for
them.
That's
it.
K
C
F
A
J
G
Management,
yeah,
I,
guess
one,
maybe
sometime
maybe
we
can.
We
can
also
talk
offline
about
this,
but,
like
maybe
we
should.
Is
this
the
point
at
which
we
should
be
switching
the
milestone
applier.
Now,
though,
that's
a
new
thing
in
the
mix,
or
should
it
be
later
I,
don't
know
right,
like
maybe
the
PR,
for
this
enabling
code
freeze
can
also
be
switching
them
out
the
milestone
to
117
for
relative
for
the
relevant
branches.
A
G
G
So
and
yeah
so
I,
just
I
just
put
this
down
as
like
we're
now
that
we're
in
we're
about
to
be
in
code
free
is
very,
very
very
soon
really
roll
leads
should
be
looking
at
who's
going
to
take
over,
for
their
roles
should
also
be
working
on
cleaning
up
the
set
of
people
who
are
listed
on
the
release
scheme.
If
you
have
anyone
who
has
been
inactive
in
your
role,
please
remove
them
from
that
roster,
and
if
you
have
questions
about
you
know,
okay,
this
person
looks
really
great,
but
I'm.
G
Thinking
about
this
and
I,
don't
know
what
to
do.
That's
what
we're
here
for
so
talk
to
us
I
think
I
think
that
now
is
probably
a
good
point
for
Josh
and
I
to
start
looking
through
the
feedback
from
both
this
cycle.
The
last
cycle,
improvements
on
the
the
questionnaires
and
and
all
that
good
stuff
and
so
I
think
I'll
try
to
start
getting
on
that
next
week.
A
A
So
that's
why
I
asked
Maria
and
the
enhancements
team
just
give
me
a
percentage
of
things
that
are
still
outstanding
because
I'd
like
to
know
what
we
think
is
at
risky
coming
in
late,
because
that
then
goes
back
to
Taylor.
So
the
sooner
we
get
that
to
Taylor,
and
he
knows
what
things
fall
out
of
the
milestone.
He
can
adjust
the
comms
messaging
accordingly
in
blogs,
Doc's
deadlines
under
spec
about
this
next
Tuesday
there
should
be
ready
for
review.
A
A
Yes,
it's
Wednesday,
9
4!
Never
doubt
yourself!
That's
what
we
learned.
Yes,
it's
9,
4,
okay,
so
and
young
is
updated.
There
we're
okay,
everything
looks
on
track,
so
that
gives
us
from
code
freeze
three
days
to
make
sure
we
try
and
take
a
look
at
CI
signals.
So
we
get
a
really
clean,
beat
or
two.
If
we
can
and
then
we
move
on
later
down
the
release.
A
I
think
we
have
an
RC
tentatively
scheduled
for
the
10th,
but
I
would
ask,
and
maybe
next
week
we
can
talk
about
whether
we're
doing
our
C's,
because
I
have
heard
things
about
our
C's
and
not
doing
them
and
doing
another
beta.
So
we
can
discuss
that
later.
Daily
burn
down
on
Tuesday
Thursday
is
added
next
week,
Monday
I've
canceled.
The
meeting
you
should
have
got
that
update
final
question
and
I
know
we're
low
on
time.
Is
the
Tuesday
Thursday
meetings,
I
took
a
pulse
from
people
in
Europe
and
9:00
a.m.
A
Pacific
seemed
to
work
for
them
in
the
majority?
Do
we
want
to
change
that
marker
had
raised
whether
we
could
do
something
that
was
more
time
soon
friendly
for
him
and
I
would
like
to
at
least
ask
that
so
I
can
re
go
and
take
a
survey
or
we
can
move
it
back
an
hour?
Is
there
any
compromise
that
we
can
make
now?
That
would
be
better
for
marker
with
an
hour
earlier
help
marker.
D
A
A
So,
with
that
in
mind,
I
mean
I'm
happy.
If
people
have
we
have
it
at
9
a.m.
I
took
a
pulse,
and
that
was
the.
That
was
definitely
the
mean
of
the
responses,
but
if
we
want
to
move
it,
please
speak
now,
I'm
happy
to
move
it
with
an
arrow
too,
and
if
there's
a
big
swing.
Anyone
in
the
morning
I
need
to
talk
with
Gwen
is
in
Europe
currently
or
Nico,
so
that
they
can
staff
that
meeting
from
a
lead
perspective.
A
So
please
I,
guess
if
you're
in
Europe
and
this
time
is
not
suitable
for
you
for
burn
downs.
Please
let
me
know
there's
four
of
these
meetings,
just
in
context
for
the
next
two
weeks,
so
we
would
be
changing
for
meeting
time
slots
happy
to
do
it.
I
guess
ping
me.
If
you
want
to
change
it.
Otherwise,
I'll
leave
it,
as
is
Marco,
has
expressed
interest
to
change
it
and.
G
A
Painters,
so
we
could.
We
could
talk
to
him
about
that,
but
please
just
make
it
known
to
me.
Make
some
noise
to
me
I
will
adjust
accordingly.
I!
Guess,
that's
the
call
to
action
if
it
does
not
work
for
you,
I
would
like
to
know
about
it.
Yeah.
Okay,
we
have
five
minutes.
There
is
super
late
stage
exception
in
the
open
discussion,
yeah.
G
A
G
No
very
strong
negative
one,
so
essentially,
there
have
been
there
have
been
kind
of
back-and-forth
about
the
functionality
of
cube
CTL
copy
and
the
discussion
has
become
like
okay.
Well,
someone
removes
a
thing
that
does
like
path
traversal
or
does
this
thing
and
someone
adds
it
back
right
or
we
find
a
new.
G
We
find
a
new
security
vulnerability
and
the
reason
this
kind
of
popped
up
is
because
there
is
something
to
be
announced
regarding
this,
so
the
so
the
thought
was
what,
if
we
just
removed
it
right,
so
the
proposal
was
to
remove
cube
CTL
copy
and
it's
like
whoa,
no
like
it's
not
that
simple.
So
this
started
on
the
architecture
and
and
and
6ui
mailing
list
and
I've
copied
sig
release
and
release
team.
So
y'all
should
have
popped
up
in
your
your
inboxes.
G
At
some
point
we
need
to
be
I'm,
one
I'm
fiercely
defensive
of
all
of
you,
and
but
we
need
to
make
sure
that
we're
watching
things
like
this.
So
if
you're
not
part
of
like
things
like
the
architecture
mailing
list,
it
might
be
good
to
join
that
one
just
to
see
when
things
like
this
pop
up,
essentially
I
I,
said
kept
it
like.
Let's
make
a
decision
kept
it
like
solve
it
there,
it
shouldn't
be
on
a
mailing
list,
but
also
like
potentially,
but
we
can't
deprecated
something
in
one
cycle
right
like
our
like.
G
Even
with
so
we
have
an
exceptions
policy,
so
we
have
an
exceptions
policy
for
things
that
come
in
to
come
in
as
enhancements,
but
we
also
have
an
exceptions
policy
for
what
we
do
around
deprecations
for
features,
flags
things
or
GA
beta
alpha
all
that
stuff
right.
So
they
wanted
to
exercise
exceptions,
policy
for
feature
deprecation
and
even
still
it
looks
if
you
read
through
it,
looks
sketchy
so
I
think
that's
a
decent
case
study.
If
anyone
has
time
to
go
through
that
thread,
yeah.
A
And
I
think,
as
it
relates
I'm,
not
sure
sure
if
you
mentioned
this,
the
case
in
point
was
we
want
to
remove
this
and
we
want
to
remove
it
in
1/16
yeah,
with
with
three
days
notice
before
code
freeze.
So
you
know
it's
an
interesting
go
and
have
a
look
at
the
back
and
forth.
It
is
an
interesting
thread.
Yeah.
G
And
it-
and
it's
it's
one
of
those
things
that
I
you
know,
I,
don't
know
if
it's
more
work
that
we
have
to
be
doing
in
terms
of
I,
don't
know
a,
but
I
really
don't
know.
You
know,
because
you
know
it's
it's
something
that
we
mentioned.
The
release
calendar
is
up
and
it's
available
and
it's
active
for
all
of
the
releases
moving
forward.
A
A
That
can
still
happen,
but
I'm
trying
to
get
all
our
ducks
in
a
row
so
that
the
next
two
weeks
we
know
exactly
where
we
stand
from
a
bug,
triage
perspective,
MSCI
signals
perspective,
so
I
just
wanted
to
say.
Thank
you,
everybody
for
the
level
of
detail,
they're
bringing
to
each
release
meeting
and
with
that
I
will
close
this
burndown
meeting,
it's
lovely,
to
see
you
all
happy
Wednesday.
We
will
see
you
at
9
a.m.
Pacific
on
Friday.
Thank
you.