►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180910
A
The
main
focus
today,
I
think,
will
continue
to
be
CI
signal,
but
all
I'll
go
through
the
agenda.
Let
me
just
paste
it
in
zoom
for
anybody
who
doesn't
have
it
handy,
but
who
is
here
as
always,
if
you
could
put
your
name
in
the
agenda,
that
would
be
useful.
I
am
Sig
release
and
zoom
aka
Tim
pepper
the
lead
for
the
112
release.
This
is
a
recorded
meeting,
so
please
be
wonderful
people
during
the
meeting
it
will
be
or
it
is
recorded
and
it
will
be
uploaded
to
YouTube
for
posterity
after
the
call.
A
So
where
are
we?
We
are
two
weeks
in
a
day
from
the
release
the
release
target,
we're
looking
to
cut
beta
to
tomorrow,
a
week
after
that,
RC
one
and
a
week
after
that
release
the
first
thing
to
talk
about
in
a
minimal
bit
of
detail.
Just
glancing
actually
he's
not
here,
which
is
good
he's
working
on
it.
So,
just
as
a
mention
Cole
is
looking
to
switch
over
the
code.
A
A
Next,
on
the
list,
CI
signal
since
Friday,
not
a
whole
lot
has
happened.
Necessarily,
we've
had
a
couple
things
merge
that
were
thought
per
to
improve
things,
but
I,
don't
think
I'm,
seeing
it
today
on
test
grid,
a
couple
things
that
I
thought
were
gonna
improve
and
particular
there's
one
around
on
paint
node
by
condition
that
where
something
has
merged
they're
late
yesterday
and
if
it
was
going
to
make
a
change,
we
should
have
seen
it
today.
A
B
A
Let's
see,
we
do
have
one
thing
that
looks
like
it
fixed
conclusively
on
the
list:
six,
eight
three
one
three
and
then
there
was
one
last
week
that
on
Friday
I
thought
it
looked
like
it
had
gotten
fixed
and
discussion
had
been
indicating.
So
six,
six,
two
forty
three
but
it
turned
out.
I
was
just
tricked
by
test
grid
and
it
was
failing
all
along
and
we
hadn't
actually
gotten
confirmation
from
the
owners
that
that
changed
happen.
A
A
C
D
A
C
A
Okay,
I
think
that's
the
main
things
we
needed
to
talk
about
from
that
list.
Did
I
hear
Mohammed's
voice?
Do
you
want
to
add
anything
else.
E
B
B
F
G
Anyway-
and
let
me
have
situated
I
am
like
you
said,
nothing
much
happened
over
the
weekend.
There
is
a
new
issue,
another
six
storage
issue,
I
triage
the
related
pull
request
into
the
milestone,
it's
a
really
large
one,
so
I'm
hopeful,
but
just
a
little
cautious
about
that
one
Westborough
zone,
the
very
last
one
on
the
bottom,
six
I,
three,
seven,
eight
new
into
the
moment
new
in
the
milestone.
It's
not
a
new
issue
I
well!
No,
it
is.
G
It
is
a
new
issue
to
four
days
old
and
on
Friday
treeoche
depend
milestone
after
the
meeting.
There
are
a
couple
relatable
requests
where
I
just
decided
to
add
them
to
the
milestone
and
add
the
critical
urgent
label,
simply
because
it
was
on
the
related
and
the
related
issue,
and
it's
just
faster.
If
I
do
it,
because
so.
G
And
we're
at
that
point
in
the
release
I'm
currently
going
through
these
individual
issues
to
update
them
a
couple
of
them
flipped
from
red
to
at
least
orange,
which
is
nice
but
I,
still
haven't
seen
any
pull.
Requests
to
merge
I
see
a
whole
lot
of
issues
that
are
like
this
close
to
merging
so
hopefully
by
Wednesday
we'll
see
improvements
here.
I,
don't
think
that
things
got
worse,
even
though
there's
an
extra
issue
but
overall
I
think
we're
holding
level
with
hope
for
the
future.
Last.
A
A
So
my
strong
hope
is,
by
kind
of
middle
of
the
week
those
things
that
are
really
close.
We
close
on
and
we're
seeing
gradual
improvement
on
the
test
status
that
as
well
for
the
things
that
are
test
related
I.
A
No.4
anybody
who's
not
looking
at
the
chat
there
good
morning,
goofy
chat
going
on
alright,
well,
I
think
that's
probably
good,
then,
for
issues
and
again
like
this
is
kind
of
a
reminder
that
the
issue
paces
is
really
low
compared
to
say
earlier
this
year
and
prior
times
when
issues
were
required
in
the
connection
to
PR.
So
as
we
as
we
move
forward,
I
suspect
we
are
gonna
want
to
do
some
thinking
about
what
to
do
for
how
we
deal
with
issues
and
how
that
ties
in
with
proposed
changes
through
sig
p.m.
A
A
Probably
yep
and
I
appreciate
that
you're
looking
at
them,
I
just
I.
My
my
worry
is
that
a
PR
is
slightly
different
than
a
bug
report.
A
good
PR
is
hey.
Here
is
the
bug
and
here's
the
fix,
but
the
fixed
part
usually
lags
the
recognition
of
the
bug
part
just
end
by
definition.
So
I
worry
about
the
visibility
there.
A
The
way
we're
doing
things
that
we
we
have
a
little
less
risk
management,
because
we
don't
have
time
to
see
quite
as
much
and
maybe
something
languished
for
a
week
or
two
when
we
could
have
rallied
some
help
to
the
individual
doing
the
PR.
But
it's
hard
to
it's
hard
to
know,
because
we're
kind
of
we
don't
have
a
lot
of
visibility
there
anything
else,
but.
A
H
A
To
mention
I
guess
there
I,
for
if,
if
you're,
on
the
milestone
burned
down
list,
you'll
have
seen
a
few
exception.
Requests
come
by
for
a
few
things
that
were
basically
immediate
right
at
the
beginning
of
the
week
and
saying
like
hey.
This
is
there's
just
now.
If
a
feature
we
need
just
another
day
or
two
we're
basically
ready.
We've
been
pending
a
review
for
the
last
week
or
two
or
something
like
that.
Just
the
the
reviews
are
done
and
one
other
person
was
needed
to
respond
with
an
LG
team
or
something
like
that.
A
Yeah,
okay,
fine
I'll,
let
it
in
because
alpha
is,
is
a
little
bit
lower
risk
and
in
that
again,
at
the
cigs
discretion,
I'm,
not
gonna
block
it.
There
have
been
a
few
where
I
basically
wasn't
happy
but
deferred
to
the
sig
and
the
sig
said
no,
let's,
let's
wait
and
then
there's
one
issue
598
on
webhook
conversions.
Firstly,
our
DS
there's
desire
for
this
makes
sense.
I
mean
it
was
discussed
at
Kubik
on
in
Copenhagen.
It's
a
it's
a
obvious
need,
but
they're
basically
saying
that
they
need,
until
the
release
date
to
be
ready.
A
H
I
I
haven't
heard
it
anything
with
regards
to
the
CRT
web
book
conversion,
since
that
discussion
so
I
like
to
assume
that
it's
strike
down
but
I'm,
not
too
sure.
Yet.
With
regards
to
the
features
the
current
status
is
44,
total
features,
8
are
at
risk.
I've
left
them
at
risk
with
regards
to
Docs
I'm
tracking,
in
addition
to
the
docs
name,
I'm,
also
like
following
the
docs
PRS
that
remain
to
go
in
it
looks
like
we're
getting
LG
TMS
and
approvals
on
some
of
them,
so
I
think
I
would
I
would
say,
I.
A
The
next
on
the
agenda
has
just
in
the
classic
burn
down
agenda
format
that
we've
had
was
PRS,
but
I've
actually
gotten
bumped
that
up
into
the
bug
triage
section,
since
we
were
talking
about
that
and
Gwyn
had
already
commented
on
it.
But
we
can.
We
can
start
for
the
next
number
of
days,
just
kind
of
giving
it
treatment
there
together.
That
I
think
that
actually
makes
more
sense.
I
A
I
I
I
can
spread
to
you
for
for
docs,
which
is
which
is
worrying,
because
it's
not
even
a
face
holder,
I,
don't
know
which
ones
I
thought
my
head,
but
I
am
feeling
just
as
everyone
suspected
on
Friday
I'm
feeling
much
better
about
after
I
actually
spent
the
time
and
got
some
more
done
with
merging
everything.
So,
yes,
that's
where
we're
at
okay.
A
Okay,
let's
see,
do
we
have
Nick
I,
don't
see
Nick
I,
don't
know
that.
There's
too
much
more
note,
oh,
but
we
have
Mike
go
ahead.
Mike
yeah.
J
Hey
guys
so
I
hope
that
some
girls,
I
should
say
we
all
of
the
release,
notes,
shadows
and
Nick
laughs.
We
got
together
and
we
did
the
final
cut
from
the
release
notes
draft
into
the
hacked
indie
so
that
we
can
start
out.
You
know,
interacting
with
cig,
leads
to
get
them
to
both
revise
the
set
of
release,
notes
that
were
for,
like
a
taxpayer
sig
as
well
as
put
together
a
paragraph
in
prose
for
kind
of
the.
What
do
they
call
it
them?
J
The
main
kind
of
you
know
to
talking
points
of
the
release,
notes
which
are
in
prose
at
the
top
of
the
dock.
Unfortunately,
we
ran
into
a
problem
where
hack.
The
document
is
too
long
for
hack
Andy.
Unfortunately,
so
right
now
we're
back
to
how
we
were
doing
it
last
release,
which
was
we
took,
the
markdown
put
it
in
a
Google
Doc
and
then
invited
over
to
the
Google
Doc
less
than
ideal.
A
Well,
thank
you
as
a
bummer
on
the
hakama
D
issue,
but
it
things
happen
so
comms
I
know.
We
owe
you
review
of
the
document
there
by
tomorrow.
I
need
to
do
a
scrub
with
Steven
on
things
that
have
dropped
since
sort
of
Thursday,
Friday
I
know,
there's
a
couple
of
things:
glancing
at
the
document
that
have
fallen
away
from
like
so
the
windows
server
containers,
that's
not
going
to
be
officially
announced
as
stable
GA,
but
I
need
to
do
a
detailed
look
through
the
the
feature
list
relative
to
to
the
draft
there.
A
H
K
D
Just
gonna,
say:
I
think
we're
in
really
good
shape
other
than
that
windows
feature
dropping
I
think
we're
in
really
good
shape
with
the
other
three
that
we're
going
to
be
the
major
announcements
and
then
I'm
guessing
some
from
the
additional
notable
feature
section
have
dropped.
So
I
can
help
clean
that
up
this
week
as
well,
I'm
missing
one
sink
review,
but
otherwise
I
think
we're
still
still
in
pretty
good
shape.
D
A
If
either
of
you
talk
to
say,
cluster
lifecycle
and
Tim,
st.
Claire
in
particular,
I
I
had
been
under
the
impression
earlier
in
the
cycle
of
the
cube,
a
diem
one
there
on
simplify
cluster
creation,
that
that
wasn't
gonna
happen
till
113.
But
then
it
is
still
listed
as
present
and
they
seemed
slightly
on
the
fence
and
I
was
supposed
to
get
an
answer
definitively
on
Friday,
but
we'll
follow
up.
Unless
you
all
have
heard
yes
affirmative.
It
is
happening.
A
A
A
That
one
slipped,
then,
then
so
that
we
had
to
there
was
basically
cube.
Atm
cluster
creation
and
cube
idiom
upgrade,
but
I
was
unclear
on
which
or
if
both
slipped
for
sure,
so
I
will
go
nail
that
down
for
sure
and
and
confirm
because
that's
actually
that's
a
very
either
of
those
going
stable.
Ga
is
a
really
noteworthy
one
and
if
either
is
happening.
H
A
A
We
like
to
do
a
retrospective
and
talk
about
things
that
we
could
have
done
better
things
that
we
did
do
better,
that
we
should
continue
to
do
and
then
also
anything
that
our
that
something
concrete
that
could
end
up
as
an
improvement
to
the
role
handbooks
for
the
release
process
would
be
awesome
and
then
Aisha's
1/13
team
is
starting
to
staff
up
there
been
some
PRS
and
things
out
there,
so
I'm.
Definitely
looking
for
for
volunteers,
especially
I,
think
in
the
shadow'
ranks
there
anything
that
you
want
to
mention.
I,
Shh,
I'm,.
C
A
Yeah,
it's
Monday.
We
have
the
full
hour
so
yeah
we
can
so
before
we
go
to
that
anything
else.
112
release
blocking
critical
that
needs
brought
up
or
discussed.
A
So
the
thing
that
wasn't
being
picked
up
on
test
it
does
look
like
it
needs
the
it
pulls
in
the
latest
release,
not
the
latest
head
of
the
the
prior
branch
on
the
upgrade
test
so
with
the
one
11.3
released
today
that
should
that
change
should
get
picked
up
and
test
and
I'll
follow
up
with
Michelle.
Unless
somebody
else
has
already
updated
that
issue,
then
we
will.
A
Okay,
whoa
watch
that
space
today.
Oh
this
reminds
me
of
something
else
too:
I
am
getting
on
a
plane.
A
few
minutes
into
the
meeting
the
scheduled
for
tomorrow
morning
ice.
Is
there
any
chance
that
you
would
be
available
to
run
tomorrow's
meeting
Jim.
A
A
C
So
yeah,
thanks
to
Steven,
we've
kick-started
the
113
team
filling
out
the
team
rolls
and
let
me
quickly
paste
the
link
to
the
bug
and
the
PR
in
the
chat
in
case
some
of
you
missed
it.
So
there's
a
github
issue
and
a
tracking
PR
where
folks
have
been
self
nominating
and
also
nominating
incoming
shadows
and
leads.
C
H
D
H
H
H
So
I'd
like
to
make
one
note
regarding
features.
Moving
moving
into
the
next
release
cycle.
There
is
active
work
between
sig
p.m.
and
save
architecture
to
move
the
Cape's
process
forward,
so
moving
away
from
design
proposals,
I'm
moving
away
from
features
being
the
primary
means
of
tracking
that
will
probably
take
at
least
one
release
cycle.
But
I
want
to
note
for
this
release
cycle
that
we
will
be
changing
the
name
of
the
features
role
to
enhancements
right
just
to
kind
of
track
along
with
that
effort.
H
C
Welcome
Kendrick,
we
can
go
through
the
leads
first
and
then
and
then
quickly
jump
to
the
shadows
and
4ci
I've
had
a
couple
of
discussions
with
Mohamed
around
this
around
filling
the
CIL
role
for
113
and
given
the
criticality
of
the
rule,
Mohamed
and
I've
spoken
also
to
Josh
in
couple
of
other
folks,
Josh
volunteered
to
fill
the
CI
role
for
130
and
Josh
is
not
on
the
call
today.
I
think
he's
away.
C
Josh
is
that
this
is
Josh
Burris.
He
was
a
release
lead
for
111,
so
yeah
he
kindly
act.
Was
he
kindly
offered
to
fill
any
role
that
we
might
need
help
with
and
CI
was
one
thing
that
came
up
in
the
discussion,
so
I
would
like
to
know
if
everybody
is
on
board
with
it
or
if
anybody
else
wants
to
self
nominate,
we
can
can
open
it
up
to
discussion.
Is.
C
And
okay,
then
I'll
go
on
to
the
next
one
test.
Intra
again,
we
had
Cole
who,
who
was
the
lead
for
test
entre
for
112,
and
it
was
a
shadow,
but
considering
113
would
be
the
first
full
release
that
will
be
untied
Cole
kind
of
preferred
to
be
to
continue
as
the
lead
so
that
we
can
battle
test
ID
through
a
through
the
entire
release
cycle
and
close
up
any
loops.
That
is
there
so
that
the
next
shadow
will
be
able
to
run
with
it
most
smoothly
from
114.
C
A
Really
appreciate
that
he's
staying
on
for
this
I
do
think
this
is
an
area
where,
especially
those
of
us
who
are
not
at
Google.
We
need
to
work
with
our
sort
of
our
corporate
sponsor
entities
to
bring
more
people
into
the
space
to
get
more
folks
engaged
on
tests
infra
and
the
Google
commitment
to
fund
this
through
the
CNC
f
is
awesome,
but
we
need
other
people
to
join
in
that,
and
it's
not
not
just
the
dollars
funding
but
like
the
the
the
human
brain
cells
hands
on
keyboard
as
well
to
be
more
active
there.
G
So
I
had
a
fairly
I
had
what's
an
above
average
number
of
shadows
and
they
were
awesome
and
it
was
really
really
hard
to
pick
one
of
them,
but
it
turned
out
that
with
everyone's
responsibilities
and
things
out,
nick
parotitis
is
the
best
choice
and
he
has
happily
agreed
to
take
on
the
role
for
113.
So
that
is
my
nomination.
G
G
Know
it
they
made
it
easy.
They
were
super
helpful
and
actually
Nick
was
the
one
who
made
my
spreadsheet
look
awesome
before
I
showed
it
to
you.
I
was
just
like
hey
ash
thinks
I'm
awesome,
because
you
made
his
spreadsheet
look
better.
So
there's
that
yeah
and
I
think
Nick
also
has
some
ideas
for
shadow,
so
I'm
not
sure
what
exactly
happened
there.
He
can
speak
to
that.
I
think
that
she's
on
the
car
right
now.
E
C
Yeah
branch
manager,
I,
don't
know
if
jug
is
on
the
call,
yeah
I,
see
Doug
and
again.
This
was
something
that
Tim
Doug
and
I
discussed
offline
a
little
bit
again.
It's
similar
to
the
test
in
front
role.
The
branch
manager
also
went
through
quite
a
bit
of
piloting
and
all
for
the
good
to
move
the
role
a
little
bit,
untie
it
from
being
Google
centric
and
both
Tim
and
Doug
did
great.
C
They
went
leaps
and
bound
and
getting
this
done
this
milestone,
but
there
are
still
some
open
ends
there
that
need
to
be
fixed
and
towards
that.
The
suggestion
was
for
Doug
to
remain
as
the
branch
manager
and
close
that
out
and
then
so
that
the
shadow
can
take
over
in
114,
but
I
liked
him
and
talked
to
this
a
little
bit
more
and
then
we
can
again
discuss
that
in
case.
Somebody
else
wants
to
fill
the
role
as
well.
I
think.
A
You
summarized
it
well
a
lot
change
there
and
it
would
be
useful
to
have
a
little
bit
more
continuity.
I
know,
erin
has
mentioned
like
this.
Wholesale
shift
of
one
set
of
people
to
the
to
the
next
is
sometimes
problematic.
So
especially
where
there's
a
lot
that
happened,
it
would
be
good
to
have
that
continuity
just
for
another
few
months
and
make
sure
we've
really
got
things
solidified
and
transfer
knowledge
well,
I.
L
Agree,
I
was
originally
expecting
the
role
to
get
here
into
one
of
the
shadows,
but
when
I
spoke
with
ice
about
it,
you
know
I'm
happy
to
do
it
and-
and
you
know
we
still
actually
made
it
through
a
full
release.
Yet
so,
and
we
still
probably
have
more
to
learn-
and
you
know
things
like
this
past
Friday
were
pretty
eventful
and
we
learned
quite
a
bit
there.
So
my
plan,
Tim
and
I,
had
had
zooms
a
number
of
times
to
kind
of
get
our
footing
with
the
stooling
process
and
with
113.
A
Would
also
mention
that
we
had
two
really
awesome
shadows
here.
Both
Hannes
and
young
lead
the
the
fact
that
this
was
in
flux
and
question,
well
that
they
were
around
help
trial
and
back
up
Doug.
While
he
was
gone.
If
either
of
you
are
interested
in
continuing
to
shadow
I
would
see
you
as
great
candidates
to
take
over
the
role
in
the
near
future
as
well.
If
you're,
interested
or
willing
I.
I
F
A
We
heard
most
of
it
Tim
anything
you'd
like
to
say
so.
We
can
hear
that
awesome
accent,
yeah.
N
J
Making
sure
that
the
Lightning
branch
cuts
before
the
actual
release
also
have
the
fully
contextualized
release
nodes,
integrate
some
ongoing
copy,
editing
stuff,
so
that
this
last
two
weeks
is
a
little
easier.
The
next
time
stuff
like
that,
so
whether
whether
you
know
I'll
be
leader,
shadow
I'm,
definitely
I'm
happy
to
keep
working
on
that
stuff.
Thanks.
C
C
C
A
Does
not
look
like
it,
I
don't
see.
Caleb
now
so
I
gather
I
chatted
a
bit
on
Friday,
one
of
the
things
that
I'd
like
to
see
here
and
Aaron
had
mentioned
this
earlier
as
well,
that
having
one
person
solely
alone
responsible
for
patch
releases
for
nine
months
is
potentially
not
the
most
sustainable
thing
over
time.
So
I
I've
got
some
ideas
there
and
if,
if
nothing
else,
we
can
start
making
it
a
team
weather,
so
I
had
sort
of
self
nominated
as
as
lead.
A
There
continue
to
try
to
build
out
a
bit
of
a
team
and
do
some
changes,
hopefully
to
to
ensure
that
as
the
but
the
project
grows
and
is
it
it
gets
a
higher
level
of
stature
with.
Potentially
then
what
typically
happens
in
open
sources
projects
really
start
to
grow.
They
get
more
attacker
eyeballs
Liana
when
you
start
having
more
CVEs,
and
that
leads
to
a
lot
bigger
workload
on
back
parts
and
things
like
that.
So
that's
not
necessarily
happening
today.
A
It's
not
necessarily
gonna
become
a
tidal
wave
that
over
overwhelms
us
over
the
next
nine
months
alone,
but
I
think
it's
time
to
start
thinking
about
how
we
do
a
more
sustainable
process
than
just
having
one
individual
there
and
obviously
with
CBE's.
You
also
have
the
security
teams
help
on
and
making
sure
that
back
ports
and
stuff
happened,
but
I
think
it's
an
area
where
we
need
to
do
some
thinking
so
I'm
totally
fine.
A
If
alexandra
is
interested
in
leading
that
I'd
like
to
also
try
to
shadow
there
and
similar
to
what
was
I
was
doing
with
Doug
just
trying
to
make
sure
that
we've
got
improved
documentation
or
thinking
about
making
sure
we
have
something
solid,
going
forward.
C
A
H
So
I
totally
agree
with
what
you're
saying
to
him,
I
think
just
in
in
kind
of
mulling
around
how
to
do
the
sacral
ease,
Charter
I
feel
that
we
have
three
teams
emerging,
a
sub-projects
one
being
the
release
team
itself,
which
we
kind
of
say,
is
the
sub-project,
but
have
not
actually
documented
so
again
that
that
PR
is
in
flight.
I
will
be
doing
that.
H
Secondarily,
we
should
have
an
official
release
engineering
team,
so
people
who
are
interested
in
that
and
this
kind
of
leads
to
I,
see
agreeing
so
secondarily,
we
should
have
a
release.
Engineering
team
and
Tim
I
think
you
would
be
a
good
advocate
for
that
and
last
we
have
an
effort
around
licensing
and
compliance
and
assuring
that
things
that
happen
in
inventor
folders
and
things
that
happened
across
the
project
have
the
appropriate
license
is
for
the
scenes.
Yes
I'm,
leading
that
effort
I
think
along
with
Nikita
and
Steve
Winslow
from
the
scenes.
H
C
Erin
says
that
he
has
a
proposal
by
retro
time
for
the
subgroup
yeah
awesome
Aaron
did
you
want
to
add
something
before
we
wander
the
shadows,
you,
okay,
all
right.
So
if,
anyway,
if
nobody
has
objections,
I'd
like
to
move
on
to
the
shadows,
so
first
up
is
really
shadow
thanks
to
Aaron
he's
kindly
accepted
to
be
the
shadow
for
113
I'm,
going
to
be
leaning
a
lot
on
him
for
guidance
and
how
things
and
also
domain
expertise
and
everything
thanks,
Aaron
and
yeah.
He
can
watch
over
me.
Well.
C
I
kinda
tried
to
find
my
way
around
113
yeah,
so
Aaron
is
our
release.
Lead
shadow
next
up
is
features
we
had.
We
had
about
three
shadows.
Last
time,
four
features:
it
was
me
bringing
my
screen,
my
kill
Gwen.
Oh
no,
last
time,
shadows
were
different,
and
this
time
we
have
nominations
like
Michael
and
Gwen
have
put
their
names
for
it.
There's
anybody
else,
wanna
shadow
features
so.
H
We
have
some
additional
is
some
additional
requests.
I
think
just
came
in
with
regards
to
feature
shadowing
Chiappetta,
who
is
my
co-chair
for
cig?
A
sure
I
would
like
to
see.
Michael
continue
as
a
feature.
Shadow
I
think
he
was
very
excited
about
it
and
an
interested
in
continuing
so
he's.
Definitely
up
for
one.
H
H
C
We
also
had
Gwen
have
Gwen,
who
is
interested
in
shadowing
features.
Is
that
right,
Gwen
yep,
that's
right,
Robert
or
agender?
If
any
of
you
are
on
the
call
to
shout
out,
if
you
want
to
shadow
once
again,.
C
Okay,
moving
on
to
CI
signal
is
Christian
or
Suraj
either
of
you
who
shadowed
from
last
time,
if
you
guys
are
on
the
call,
neither.
C
A
This
we
as
we
find
that
we
have
gaps
and
this
as
well.
We
can
go
to
the
community
meeting
and
other
forums
as
well
and
put
the
call
out
additionally,
I
mean
it's
been
out
there
before,
but
it's
I
think
for
a
lot
of
people.
It's
daunting
to
volunteer
for
something
like
this.
It's
I
know:
I
should
mention
it
earlier
and
I'll
say
it's
daunting
to
do
it,
but
it's
fun
and
rewarding
right.
A
So
you
are
doing
a
useful
contribution
here
and
I
think
for
somebody
who's,
maybe
a
little
on
the
fence,
and
this
was
my
case
going
back
to
a
year
ago
in
December,
like
you
hear
that
broad
call
and
it's
like
I,
don't
know,
but
as
it
gets
a
little
more
specific,
you
maybe
think.
Well,
you
know
I
could
do
that
and
there's
somebody
out
there
who's,
which
you
will
hear
the
message
and
be
interested
in
volunteering
as
it
becomes
a
little
more
focused,
and
hopefully
we
can.
We
can
suss
out
a
few
more
volunteers.
There.
K
H
There
was
some
discussion
and
and
I'm
not
sure
that
we
specifically
nailed
it
down,
but
the
idea
of
interviewing
shadows
that
maybe
may
be
interested
in
the
cycle
just
to
get
you
know,
kind
of
where
their
heads
at
and
and
an
idea
of
time
commitment
might
be.
A
might
good
moves
to
make
sure
that
we
kind
of
continue
the
process
and
we
have
people
who
are
dedicated
to
it
for.
A
C
A
couple
of
new
folks
have
been
pinging
me
on
slack
before
they
sign
up
for
shadows,
which
is
like
a
good
thing.
So
I've
been
like
clarifying
a
little
bit
about
the
commitment
and
expectation
there,
but
yeah.
It's
always
good
to
maybe
have
like
a
fun
informal
questionnaire
or
something
just
so
then
both
ways
to
be
appearance.
E
Your,
although
another
thing
need
to
make
it
very
clear
that
they
will
have
to
do
something,
I
mean
I,
get
that
they
might
have
to
pull
off
your
or
something
or
that.
But
that
can
happen.
I
am
for
enforcing
courses,
but
they
need
to
be
aware
that
they
need
to
actually
be
actively
involved
to
diminish.
Out
of
this
one.
C
M
C
G
Not
actually
sure
what
the
current
status
is
on,
I
asked
one
of
them
as
much
I
asked
I
know
to
shadow,
but
I
think
he's
interested
in
a
different
shadow
role.
So
currently
I
think
what's
going
on,
is
that
Nick
had
some
idea
for
a
shadow
and
but
I
don't
know
the
actual
current
status
of
that
no
issues.
I
think
we
can
yeah
Jeremy
might
be
up
for
shadowing
again,
though
so
so.
H
F
C
Okay
and
last
few
branch
manager,
this
role
had
quite
a
few
people,
interested
I,
know
yang
and
Haynes.
If
I'm
telling
the
name
correctly,
you
guys
expressed
interest
in
continuing
as
shadows
and
there
was
also
a
double
yeah.
He
was
interested
in
shadowing
and,
of
course,
Jeremy
is
that
Jeremy
I'm?
Sorry,
if
I'm
getting
again
the
name
wrong,
he
was
interested
in
shadowing
as
well.
I
I
think
the
shadows
were
going
to
be,
for
Jim
angel
was
interested
in
doing
them
and
then
I
was
too
but
kind
of
more
from
like
a
mentor,
slash,
automation,
II
role.
I
would
like
to
sort
of
flesh
out
more
some
of
these
lovely
little
tools
that
we've
built
in
the
thoughts
seemed
to
pester
people
and
to
review
PRS
a
bit
quicker.
So
that's
legal
and
being
part
of
the
release
team,
but
it's
specifically
geared
towards
early,
so
I
figured
I'd
just
say.
H
C
I,
don't
know
if
Dave
or
yeah
Lyndsey
any
of
them
are
on
the
call.
They
were
the
shadows
from
112.
C
A
Lindsey
had
reached
out
to
me
on
slack
and
indicated,
probably
a
little
less
availability
had
been
interning
during
the
summer,
going
back
to
school,
to
finish
and
but
is
interested
in
continued
to
be
involved
in
the
project.
So
I
was
looking
for
four
ways
to
do
that,
so
we'll
see
what
we
can
figure
out
as
the
time
goes
by
here,.
C
G
Can
you
hear
me
yeah,
hey
there?
This
is
Kristen
I'd
love
to
shadow
Kaitlin
again
for
113.
C
A
Nothing
else
to
say:
Erin
mentioned
I,
guess
there
and
zoom
that
we
are
switching
to
tight
or
we
have
switched
successfully
rather
so
yeh.
N
A
K
O
O
There
is
a
little
bit
of
a
question
that
I
have
so
it
is.
It
is
working
now
there's
a
one
like
minor
catch,
though,
which
is
that
we've
been
getting
pretty
high
error
rates
from
github
this
morning,
so
I
just
deployed
the
config
so
that,
however,
tide
will
start
considering
Kay
Kay
but
I
didn't
restart
the
time
deployment
itself.
So
that
means
that
existing
PRS
that
haven't
been
updated
since
we
started
it
are
not
gonna
have
their
status
is
updated
until
we
restarted
the
time
pod.
O
J
A
O
A
And
I'm
I'm
gonna
guess
it
most
there's
like
one
or
two
or
something
like
that:
I
mean
yeah.
We
at
any
moment
we've
had
like
at
most
20
things
that
are
like
20,
open,
PRS
or
so
so
it's
it's
not
like.
There's
a
big
volume
right
now-
and
this
is
with
one
of
the
benefits
of
doing
this
now
versus
during
normal
development,
part
of
the
cycle,
cool.
O
Well,
tides
already
emerged
a
few
things
because
of
the
because
we
have
relaxed
requirements
with
tide.
We
can
merge
things
to
the
previous
release
branches.
Those
those
branches
had
some
PRS
that
were
actually
ready
to
be
merged,
so
we're
we've
merged
some
and
we're
batch-testing,
some
other
ones
in
hell
and
then
there's
some
there's
two
things
in
the
release:
branch
that
are.
Oh,
yes,
that's
one
11,
knowledgeable
yeah,
but
things
seem
to
be
working
properly.
Cool.
F
A
Right,
well,
we
are
at
the
end
of
the
hour,
so
thank
you.
Everybody
I
shall
follow
up
with
you
about
tomorrow's
meeting.
Okay,
awesome!
Thank
you
and
we'll
see
everybody
who's
able
to
make
the
meeting
tomorrow.
If
you're
not,
please
drop
an
update.
I'll
get
the
meeting
agenda
ready
for
tomorrow.
Right
now,
just
so,
you
can
put
status
up
there
as
you
have
it,
and
we
will
do
this
all
again.