►
From YouTube: k8s 1.16 - Week 1 - Release Team Meeting 20190701
Description
Release details: http://bit.ly/k8s116
A
Okay,
fantastic
hello
and
welcome
to
the
first
of
many
1/16
release
team
meetings.
This
is
week.
One
today
is
July
1st
2019
and
that's
a
Monday
a
couple
of
housekeeping
things
before
we
get
into
it.
This
call
is
subject
to
the
kubernetes
code
of
conduct,
which
says:
please
treat
everything
muddy
with
restrictive
respect
and
be
awesome
to
one
another.
So
everybody
this
meeting
is
being
recorded
and
will
be
uploaded
to
YouTube
after
this
call
so
be
mindful
of
your
words.
A
This
is
the
first
of
12
weeks
of
the
1.16
release,
and
hopefully
everybody
has
found
the
release
note
as
the
meeting
minutes
I'm
going
to
grab
a
link
here
for
everyone
and
could
I
get
a
volunteer
to
take
notes
as
well.
Please
go
ahead
and
place
your
name
in
the
week
1
template,
which
is
halfway
down
I'm
just
grabbing
the
meeting
link.
Here
we
go
putting
it
in
the
chat
and
go
ahead
and
add
yourself
as
an
attendee
in
the
week
1
section
there
with
your
Associated
role.
That
would
be
very
much
appreciated.
A
I
can
see
already
everybody
doing
that
fantastic.
So
to
kick
off
the
release
team
meeting.
I
would
like
to
go
through
and
actually
just
provide
a
round
of
introductions,
starting
with
the
leads
I
guess:
I'll
be
first
cab
off
the
rank
and
then
we'll
go
around
and
if
you've
chosen
is
your
shadows
as
well.
Please
take
the
opportunity
to
introduce
them
and
then
we'll
get
into
the
formalized
agenda.
That's
there
on
the
minutes
there,
okay,
my
name
is
Lachlan
Evensen
I
go
by
lucky
or
Lachlan
I'll,
be
your
lead
for
116.
A
It's
my
pleasure
to
serve
I'm
looking
forward
to
a
fantastic
release.
I
you
can
find
me
in
SiC
p.m.
I
serve
as
a
chair
there,
along
with
Steven
and
a
few
other
folks,
so
feel
free
to
come
there.
We
are
the
keepers
of
the
kept
process
amongst
many
other
things.
So
if
you
have
a
p.m.
related
question,
please
feel
free
to
reach
out
to
me
there
as
well
and
I'm
excited
to
introduce
my
shadows.
I
have
three
shadows,
I
believe
they're.
A
B
Good,
my
name
I'm
Claire,
nice
anchor
I
am
calling
in
from
Seattle
and
the
United
States
Pacific
Northwest
I
work
at
github
for
my
day
job,
and
actually
this
is
part
of
my
day
job,
so
I
am
really
excited
to
see
everyone
and
work
with
some
of
you
that
I've
never
worked
with
before
and
and
get
to
meet.
Some
of
you
a
little
bit
more.
B
C
C
A
Might
be
on
vacation
vacation,
yes,
Oh
Nico
was
one
of
the
lead
shadows
in
115,
so
Nico
was
returning
as
lead
shadow
for
116.
We're
excited
to
have
him.
Nico
works
independently
out
of
Berlin,
so
he
keeps
the
European
hours
and
you'll
see
him
in
and
out
this
release.
I
believe
he
has
some
vacation
up
front
thanks.
Steven
I
will
pass
it
over
to
Enhancement
slave
lead,
Kendrick
I
know
you
probably
want
me
to
leave
everybody
foggy.
D
D
No
I'm
good,
so
my
name
is
Kenny
Coleman
I
am
the
enhancement
lead
for
116.
I
was
also
for
115.
I
was
also
for
one
or
no,
not
115.
Was
it
yeah,
115
and
also
113
as
well
I
stuck
around
it
at
some
things
in
112
and
114
too
so
I've
been
a
familiar
face.
I
think
a
little
bit
around
here
for
a
little
bit
round
a
year
now.
So
it's
glad
to
be
a
part
of
this
team
once
again
day.
D
Job
I
work
for
VMware
and
again
part
of
my
job
is
to
be
able
to
help
and
do
cool
stuff
like
this,
so
very
excited
to
make
sure
that
I
can
do
that
as
well.
This
release,
I'm
gonna,
have
I'm
bumping
it
up
with
additional
shadow,
so
we're
having
three
shadows
on
our
team.
I,
don't
know
if
anybody
on
the
team
was
actually
able
to
make
this
call,
because
two
of
them
didn't
have
the
invite,
and
then
mr.
Bobby
tables
or
Bob
Kealing
is
everybody
might
not
know.
D
He
is
going
through
a
house
move
this
week,
so
you
can
imagine
how
much
fun
that
is,
to
pack
up
a
whole
house
and
move
it.
So,
besides
Bob,
we
also
have
Maria
Italia
who's
been
on
here
also
before
we
also
have
Eddie
who's
coming
from
Microsoft,
but
we
have
RIA
who's
coming
from
Microsoft,
so
you're
gonna
see
sorry
I
said
it's
wrong
for
total
shadows,
plus
me
going
through
this
particular
cycle
cycles.
D
So
it
should
be
good
plenty
of
people
to
help
pick
up
any
slack
that
that
I
end
up
dropping
so,
but
it
should
be
a
relatively
fun
side
on
our
end,
Bob's
already
kind
of
like
updated.
The
sheet
wants
to
kind
of
do
some
automated
polling
from
github,
so
we're
gonna
start
testing
that
out
this
release
with
some
tiny
bit
of
automation
inside
the
spreadsheet.
E
F
Yes,
I'll
start:
my
name
is
Jim
angel
I'm
shadowing
first
GI
signal
I've
been
on
the
release
team,
since
112
mainly
focusing
on
doubts,
then
transitioning
oversee
icing
will
learn
a
little
bit
more
about
the
project.
I've
already
said
this,
but
I'm
based
out
of
Austin
Texas
worked
for
General
Motors.
My
day.
Job
is
really
just
making
cooper
neighs
easier,
so
that
kind
of
blends
right
in
with
the
release,
team
and
kind
of
the
goal,
the
project,
so
I'm
really
excited
to
be
back,
and
this
is
a
great
group
of
people.
A
A
E
A
G
Everyone
I
mark
mother
in
each
back
tears
lead
for
this
release.
Cycle
I
have
been
shuttling,
but
we
ask
for
one
poit
for
14
and
14
and
I'm
very
excited
to
leading
this
role
in
this
release
cycle.
I
hope
we
will
have
on
also
cycle,
and
so
I
am
located
in
Belgrade,
so
set
of
European
time
zone
is
of
my
day.
G
Job
I
am
a
software
developer
at
Lucy
and
I
am
a
computer
science
student
at
the
University
of
Belgrade,
but
currently
only
summer
breaks
or
who
yeah
I
am
excited
about
bug,
triage
and
hoping
that
I
can
help
to
improve
the
wardrobe.
How
we
take
care
of
issues
and
so
on,
and
we
will
see
how
it?
How
will
it
go
on.
H
Hello,
everyone,
my
name
is
Jung
Lee,
so
I've
been.
You
know
the
release
team
for
several
cycles
and
I'm
going
to
be
the
much
manager
Lee
at
this
time.
So
we
have
I,
believe
13,
shadows
or
associate
this
time
so
I'm
very
exciting
to
see
they
are
here
and
looking
forward
to
work
with
you
yeah.
Thank
you.
A
I
Hi
I'm
Sasha,
eyewash,
hello
for
115
and
now
I'm
leading
116
and
it's
a
pleasure
to
meet
you
all
I
think
some
one
of
you
may
know
me
and
I'm
located
in
Central
European
summer
time,
so
a
little
bit
tricky.
But
we
have
selected
four
shadows
some
minutes
ago
and
they
are
all
not
here
and
one
of
the
shadow
is
Lindsey,
which
was
lead
for
1:15
and
I
think
they
will
have
get
their
time
to
introduce
theirselves
in
the
next
meeting.
Maybe.
J
Everyone
happy
Monday.
My
name
is
Taylor
Dolezal
during
the
day
I
work
for
Walt
Disney
Studios,
leading
the
SRE
team.
Despite
the
number
of
applications
we
manage
it
still,
never
as
crazy
as
the
final
weeks
of
a
kubernetes
release.
I
have
three
shadows
that
have
confirmed
welcoming
back
David
McKay
and
then
introducing
Karen
shoot
and
Emraan
Pucci.
That
will
be
helping
me
add
this
release.
A
Okay
turned
out:
well,
we
will
try
again
the
next
meeting,
but
thank
you
for
joining
and
I'm.
Unfortunately,
audio
issues
getting
in
the
way.
If
you
come
back
and
you
get
a
fix,
feel
free
to
interrupt
and
we
can
introduce
you,
he
dropped
off,
okay.
So
moving
on
to
the
main
part
of
the
agenda
now
so
I'm
going
to
provide
an
update,
then
move
over
to
the
admire,
a
nurse,
advisors,
Josh
and
Steven,
and
then
there's
an
open
discussion
at
the
end.
A
Now
most
of
this
is
housekeeping
today
on
the
agenda,
so
make
sure
that
you
and
your
leads
have
joined
the
kubernetes
release
team
Google
Group.
That
should
give
you
access
to
the
Google
calendar,
invite
for
the
whole
schedule
and
if
you
pop
to
the
top
of
this
release
meeting
document
here,
there's
all
a
bunch
of
interesting
links.
One
includes
the
whole
release
team
calendar
as
well.
If
you'd
like
to
take
two,
take
a
look
at
that
in
its
entirety.
A
A
Moving
on
to
the
release
plan,
so
we've
proposed
a
schedule
that
you
can
find
on
the
release.
Specifics
in
the
cig
release
for
116
I'd
kind
of
share
my
screen
here
quickly,
so
that
everybody
can
see
right.
Can
everybody
in
my
screen?
Okay,
fantastic,
so
I'm
just
going
to
pop
over
and
do
the
driving
from
here.
This
specific
document
highlights
the
TLDR
on
all
the
key
milestones
for
the
release,
so
we're
starting
the
release
cycle
today.
Obviously
July
30
and
add
a
PS
T.
A
We
have
enhancements,
freeze,
Thursday,
August,
29th
code,
freeze,
September,
9th
Doc's
must
be
completed
in
review
and
we
have
scheduled
as
the
release
date
is
September.
16
now
I
know
that
there
are
a
few
summertime
holidays
across
different
continents.
So
I've
tried
to
account
for
that
and
if
you
pop
down
to
the
timeline
here,
you'll
see
a
breakdown
in
each
and
every
milestone
in
the
release
all
the
way
out.
A
But
if
there
is
a
date
or
something
that
I've
overlooked
feel
free
to,
let
me
know,
or
one
of
the
lead
team
know
and
we'll
try
and
work
on
moving
around
that
now.
You
will
notice
that
the
end
of
this
week,
the
only
thing
we
have
scheduled
here
is
skid
finalizing
the
schedule.
We
actually
have
the
team
finalized
at
the
end
of
next
week,
but
we're
asking
that
people
do
that
sooner
rather
than
later,
as
there
are
quite
a
few
bunch
of
shadows
that
applied.
A
So
if
you
can
have
that
finished
by
the
end
of
the
week,
time
permitting
and
everybody
responding
understanding
that
we
do
have
a
short
week
here
in
the
u.s..
That
would
be
fantastic
and
the
first
big
milestone
after
that
is
kicking
off
enhancements
tracking,
which
starts
at
the
Tuesday
on
week.
Three,
we
also
have
the
Alpha
branch
manager
taking
care
of
the
first
alpha
release
as
well.
So
that's
a
high
level
of
all
the
all
the
milestones
in
this
release.
A
If
there's
any
that
anything
that
I've
missed
or
anything
that
doesn't
work,
I'd
be
interested
to
know.
So
please
do
let
us
know
the
other
thing.
Is
we
call
out?
What
are
we
going
to
do
differently
in
this
release?
So
there
are
two
large
items:
there
might
even
be
three
there's
a
branch
management
changes
as
well.
Stephen
might
take
us
through
that,
if
there's
anything
worth
noting
on
this
call,
but
we
have
dissolved
the
test
info
role.
A
There
is
one
central
tracking
issue
so
for
the
things
that
are
automated
and
the
pieces
that
need
to
be
broken
out
into
other
roles.
Please
make
sure
you
get
your
handbooks,
updated,
I'm
going
to
go
through
and
take
a
look
at
that
where
the
status
of
that
issue
is
and
where
the
Associated
P
is
and
make
sure
that
everybody
is
comfortable
with
that
and
the
release
notes,
so
we're
going
to
go
exclusively
to
PR
changes
being
noted
on
the
release
notes
site
rather
than
in
the
changelog
markdown,
where
they
have
been
in
existing
releases.
A
So
if
there's
any
questions
about
that,
we
did
in
both
places
for
115
and
116
will
be
only
doing
it
in
the
revenue,
release,
notes,
site
and
I.
Think
the
only
other
thing
worth
mentioning
here
is
emeritus
advisor.
We
really
appreciate
a
giass
work
in
115,
so
we're
going
to
keep
that
role.
Josh
is
going
to
be
staffing.
It
and
Josh
and
Steven
have
been
splitting
the
work
currently
given
timeline
classes
for
Q
con
Shanghai
last
week.
A
High-Level!
That's
it
so!
Please
make
yourself
familiar
with
this
document.
There's
a
whole
bunch
of
interesting
facts
here
about
the
release
and
that's
just
a
great
place
to
go
and
take
a
look,
and,
as
I
mentioned
back
at
the
top
of
this
document,
there's
a
whole
bunch
of
links
here
just
so,
you
can
get
to
places
quickly
with
these
bit
ly
links.
So
if
you
have
any
questions
about
them
either
or
you
feel
something's
missing
that
either
I
or
the
team
know,
the
115
retro
I
would
encourage
everybody
to
go
and
take
a
look.
A
I
think
we
haven't
scheduled
in
the
second
part
of
the
retro.
Is
that
correct,
Steven
that
might
be
in
it's
that's
tomorrow
tomorrow,
so
if
you're
part
of
115
or
116
I
would
encourage
you
to
come
because
basically,
the
outcome
of
the
things
that
we
want
change
and
the
things
that
were
agreed
on
is
part
of
the
end
of
115.
A
Each
individual
team
member
would
be
responsible
for
picking
that
up
and
helping
work
on
that
as
part
of
116,
and
we
actually
go
back
at
the
end
and
say:
did
we
actually
follow
up
on
these
items?
So
there's
quite
a
few
things
there
I'd
encourage
you
all
the
comments
during
the
I
guess
it's
during
the
release
team
cig
release
meeting
tomorrow.
Is
it
Steven
and
that
is
at
1:00
p.m.
peace
to
the
East
Pacific,
or
is
it
Oh
I'll
put
two
okay
so.
A
It
otherwise
it'll
be
recorded,
and
the
document
for
the
retro
is
there.
I
spoke
about
changes.
This
release
upcoming
milestones
is:
please
select
your
release,
team
and
associated
shadows,
have
it
all
locked
in
and
peered,
and
you
can
update
the
contact
sheet
as
well.
The
contact
sheet
helps
us
get
out
swag
at
the
end,
so
there's
your
incentive
to
get
that
done
and
July
16
is
the
1/16
hour
for
one
release,
which
is
first
I.
A
Have
this
project
board
that
we're
going
to
start
doing
the
rundown
in
this
meeting
of
so
go
and
take
a
look
and
make
yourself
familiar
with
this,
but
this
should
have
items
for
the
release
team
specifically
or
cig
releases
working
on,
but
there
are
pieces
that
each
individual
team
can
pick
up
here.
So
go
take
a
look
at
the
different
associated
areas
in
the
backlog
specifically,
and
if
you
think
you
are
capable
of
picking
up,
one
of
these
items
feel
free
to
go
and
pick
it
up
and
move
it
to
in
progress
or
to.
K
Do
so
one
note
about
the
release?
The
release
cig
release
project
boards,
at
least
there
are
four
different
ones,
because
we
have
that
much
work,
so
don't
feel
that
you
are
limited
to
just
the
release
team.
One
there's
a
cig
release
board.
There
is
a
release
team
one
and
there's
a
release,
engineering
one
and
there's
also
a
licensing
one.
So
you
can,
if
you
hit
that
projects
link
you'll,
be
able
to
view
all
of
the
the
org
level
words
for
kubernetes
and
those
will
be
included
in
that.
H
A
I've
got
one
more
now
down
here,
which
is
the
testing
for
role
removal.
So
for
everybody
who
was
involved
in
that
decision,
it's
been
gardening
and
shepherding
it.
Please
go
and
make
sure
that
your
issue,
the
issues
up
to
date
and
all
associated
POS
with
handbook
changes
have
been
made
and
that
there
is
that
the
lead
is
a
part
of
that
discussion
as
well,
because
they'll
be
taking
on
the
changing
role,
the
extra
responsibilities
there.
M
Everybody
so
Steven
and
I
are
young
for
this
and
partly
was
because
of
Shanghai
last
week,
partly
it's
actually
working
out,
because
we
now
have
separate
shadows
for
the
release,
engineering
team
and
so
we're
gonna
have
to
develop
the
shadow
programs
all
over
the
place.
So
the
and
anyway
we're
currently
in
the
process
of
selecting
shadows,
I
think
all
of
the
leads
in
this
call
have
been
involved
in
reviewing
it.
I
realized
that
it's
difficult
because
all
of
you
got
and
at
this
point
unprecedent
number
of
applications
I
think
we
were
averaging
17
per
position.
M
K
K
So
that's
someone
doing
this
stuff
for
nine
months
or
so
right.
So
the
first
thing
that
we
did
around
release
engineering
was
turned
that
into
a
team
right,
so
we
have
a
set
of
four
people
who
are
who
are
ready,
willing,
able
and
have
the
appropriate
access
to
cut
releases
for
kubernetes
right.
That
was
the
first
step,
we're
taking
it
a
step
further
taking
branch
management
out
of
the
release
team
right.
K
So
what
we're
trying
to
do
here
is
essentially
build
a
ladder
of
release
engineering
and
within
kubernetes
write
a
place
so
that
we
can
consolidate
the
knowledge,
make
sure
everything
is
well
documented.
Have
a
team
of
people
who
are
ready,
willing
and
able
to
iterate
over
the
bash
fire
that
is
kubernetes
release
the
kubernetes
release
repo
right
start,
rewriting
some
of
those
tools
identifying
identifying
gaps.
I,
don't
know
if
Peters
on
the
call,
but
Peter
was
working
over
the
weekend
to
to
do
a
bunch
of
shell
checking
on
the
bash
scripts
there
and
kubernetes
release.
K
So
it
was
kind
of
like
Peter
tossing
up
a
PR
and
me
approving
the
pr's,
and
so
so
I
think
we've
got
we're
starting
to
get
like
nice
traction
on
the
release
engineering
stuff.
So
we
did
something
kind
of
I,
wouldn't
call
it
funky,
but
interesting
for
branch
management
we
took
on
I,
believe
28
people
applied
and
we
took
on
13
shadows.
K
Our
13
release
manager
associates
the
idea
there
is
to
gather
a
large
team
through
them
at
this
release,
engineering
problem
and
hopefully
be
in
a
much
nicer
place,
looking
into
one
117
118,
so
blah
blah
blah
blah
blah
all
that
stuff.
So
if
the
the
TLDR
of
that
is
branch,
early
branch
management
is
out
of
the
release
team.
It's
currently
under
the
release
engineering
sub
project,
as
of
116
right
in
terms
of
selections,
I,
have
approved
PRS
for
pretty
much
every
role.
I
believe
the
only
one
remaining
is
bug
triage
and
Marco.
K
You
sent
me
an
email
earlier,
that's
IO!
U
response
on
all
that
stuff,
but
we're
just
about
done
with
shadow
selection.
The
next
step,
josh
and
I
josh-
has
a
a
informational
rejection.
E
template
for
the
people
who
were
not
selected
I
am
I
still
need
to
go
over
that
stuff.
I
need.
Basically,
since
we've
changed
some
of
the
roles.
K
M
What
covers
everything?
The
we're
gonna
have
other
things
to
go
over,
because
we
have
the
feedback
from
last
release
cycle
that
we
still
need
to
go
over
and
maybe
changing
things
up
depending
on
on
this.
In
the
meantime,
I
mean
we
have
a
lot
of
Shadows
miss
meeting.
If
you
are
a
lead,
please
make
sure
that
your
shadows
have
the
information
they
need
to
attend
the
release
meetings
and
encourage
them
to
do
so,
particularly
if
you
are
unable
to
make
the
meeting
a
meeting
yourself.
M
K
So
an
additional
requirement
or
expectation
of
the
leads
is
that
you
are
actively
mentoring.
Your
shadows
right.
These
are
people
that
you
are
training
to
take
over
this
role,
for
you
right,
so
I
expect
everyone
to
be
engaged
in
that
I
expect
expect
to
occasionally
hear
back
about
how
shadows
are
doing
right
there.
There
are
now
exit
surveys
for
the
exit
questionnaires
right
Josh,
for
the
release
team
that
we
want
to
be
able
to
make
sure
we're.
M
K
So
some
of
the
stuff
that
we
want
to
work
on
is
we
want
to
make
sure
that
we
kind
of
go
through
the
feedback
that
we've
gotten
from
the
retro
and
then
also
go
through
the
feedback
that
we
got
on
the
on
the
shadows
questionnaire.
We
got
a
lot
of
good
feedback.
A
lot
of
it
was
like
this
is
perfect.
There's
nothing!
You
need
to
do
to
fix
this,
and
some
of
it
was
like
hey.
K
It
would
be
great
if
blah
right,
so
we're
gonna
try
to
iterate
over
some
of
that
feedback
during
this
cycle
and
I
think
I
think
that's
all
I
got
on
on
the
shadow
recruitment,
at
least
so
I
think
everyone
Lee
DeWyze,
isn't
a
good
place
to
have
as
their
shadows
locked
in
in
PR.
But
triage
is
the
last
one
and
Marco
I
owe
you
something
for
that,
but
that
will
be
coming
soon.
So
the
next
item
is
I
kind
of
wanted
to
go
around
the
room,
really
quick
and
get
an
idea
of
I.
K
I
think
that
it's,
it
would
be
something
that's
interesting
and
nice
and
time
capsule
II,
to
have
recorded
at
the
beginning
of
the
release
cycle,
to
see
how
we
fared
against,
like
our
previous
expectations
of
ourselves
right
so
I
kind
of
want
to
go
around
the
room,
and
if
you
can
succinctly,
you
know
just
a
few
sentences
talk
about
like
if
there's
like
the
one
thing
I
could
achieve
for
my
role.
Where,
like
what
is
my
grand
goal,
my
role
I
wanted
I
want
to
get
that
right
so
like.
K
If
you
take
Aaron
in
one,
was
at
113,
okay
113,
he
said
I'm
gonna
make
sure
that
I'm
gonna
make
keps
a
requirement
for
the
release
cycle
right
lots
of
friction
right,
but
also
lots
of
value
like
high
value
out
of
that
stuff
right.
So
I'll
start
with
you
lucky.
If
there
is
one
thing
that
you
could
get
done
for
this
release
cycle,
what
would
it
be.
A
Yeah
so
I
think
the
biggest
thing
that
I
can
contribute
to
this
release
cycle
is
encouraging
further
automation
akin
to
something
like
tests
infra,
so
I
would
be
really
encouraging
a
lot
of
these
roles.
There's
a
lot
of
rinse
and
repeat
so,
while
leads
are
looking
at
things,
try
and
find
an
area
that
you
could
potentially
spend
some
time
on
automation.
So
an
example
of
what
I
heard
from
Kenny
was
that
Bob's
also
started
automating
some
of
the
spreadsheet
to
be
reactive
to
what's
happening
in
github.
A
So
the
testing
for
all
was
automated
completely
in
115
by
Katherine
and
the
team,
which
was
a
fantastic
outcome,
but
I
think
just
a
lot
of
that.
You
know
a
lot
of
that,
wash
and
repeat
repeat:
can
we
can
we
automate
pieces
so
I'll
kind
of
put
it
out
there
to
the
leads
to
try
and
identify
one
piece:
that's
right
for
automation,
I'd,
really
like
to
Shepherd
that
through
awesome,
awesome.
E
Let
me
see
well,
if
I
one
goal
I
would
like
to
one
thing:
I
would
like
to
make
sure
that
happens,
for
this
release
cycle
is
to
make
sure
that
all
of
the
shadows
feel
completely
comfortable
contributing
with
contributing
with
other
six
a
monitor
monitoring
issues
they
take
in
the
kingdom
up
a
notch
in
in
containing
contributing
contributing
to
fix
them
or
whatever
happens,
to
be
the
solution
for
that
other
than
that
I,
don't
know!
That's
why
I
only
like
Oh.
K
Something
additional
of
requests
instead
of
a
goal,
is
I
would
love
to
see
succinct
criteria
for
what
release
foo
jobs
are
right,
so
release
blocking
and
forming
miscellaneous
all
that
stuff.
We
have
a
general
rubric
right
now.
It
is
not
perfect,
but
it
is
getting
close.
I
would
love
to
see
that
get
iterated
over
for
the
cycle.
D
My
goal
is
to
just
stay
the
course
we're
going
good
I'm
just
kidding.
What
we'll
do
is
for
the
most
part.
Really,
you
know
I've
already
kind
of
talked
to
Bob
and
I
really
want
him
to
be
ready
to
go
and
be
able
to
take
over
for
1:17.
So
it's
gonna
be
a
lot
of
me
sort
of
shepherding
getting
anything
done,
but
working
really
hand-in-hand
with
him
to
make
sure
that
he
is
super
comfortable
ready
to
take
over
for
117,
but
also
giving
a
lot
of
the
exposure
to
everybody
else.
Underneath
of
it.
D
I
myself
didn't
set
any
lofty
goals
to
start
automating
anything.
This
can
be
too
busy
with
with
everything
else
going
on
in
my
life.
So
you
know
Bob's
already
kind
of
started
down
that
path,
and
so
I
want
to
try
to
encourage
him
and
teach
it
or
show
the
people
where
the
gaps
are
within
our
current
system
and
what
we
can
do
to
try
to
find
either
something
that
makes
sense
or
anything
beyond
that
cool.
G
I'm,
not
very
sure,
is
it
allowed
to
have
my
two
girls
is
this
something
that's
we
want,
but,
okay,
so
basically
the
first
one
is
to
try
to
automate
the
Butler's
stuff
as
much
as
possibility
see.
How
can
we
improve
the
tracing
of
the
issues
and
how
are
we
going
to
take
care
of
that,
but
also
as
another
girl
to
see
how
we
can
improve
the
communication
when
it
is
related
to
Butler?
G
K
N
Hello,
so
for
me
the
main
goal
for
me
this
release
is
there
was
this
issue
that
we
had
last
release
and
the
one
before
way
by
surrounding
like
a
merge
conflict
resolution.
So
the
goal
is
to
make
sure
that
does
not
repeat
itself
and
also
to
document
the
process
and
make
sure
those
that
come
after
me,
especially
like
the
current
shadows,
know,
are
very
very
aware
of
the
process.
That's
the
first
go.
N
The
second
goal
is
to
make
sure
that
most
of
the
time,
dogs,
the
action
takes
place
towards
the
end
of
the
release
for
dogs,
so
I
would
like
to,
like
you
know,
make
shadows
to
be
more
and
more
involved
with
every
step
during,
like
you
know,
towards
the
end
of
the
release,
so
that
keeps
them
to
be
more
in
more
informed
and
also
it
helps
to
train.
You
know
the
next
leader
possible
leader
for
dogs.
So
it's
that's.
Those
are
my
two
goals
right
now.
I
So
I
think
we
have
multiple
targets
for
this
release,
but
to
keep
it
in
one
sentence.
I
would
say
that
we
want
to
enhance
the
release
more
notes
and
for
crosslink
documentation
like
deprecations
caps
and
other
dependencies,
and
we
want
as
well
evaluate
our
survey,
which
is
currently
running
on
the
release,
notes
site
so
about
our
two
main
goals.
J
Yeah,
so
so
definitely
this
this
release
a
lot
of
the
the
past
two
releases
that
I
was
on.
It
was
definitely
a
lot
of
ad
hoc
type
of
communication.
Definitely
and
that's
the
nature
of
the
role
right.
You
know,
depending
on
the
caps
that
actually
make
it
and
the
features
and
everything
else
to
get
released.
It's
it's
you're,
not
always
certain,
on
what
the
what
you're
going
to
be
talking
about
and
what
actions
need
to
be
done.
J
That
being
said,
we
could
still
make
it
generic
enough
that
we
can
document
what
the
overall
goal
of
the
processes
and
then
once
we
have
that
done
once
you
have
a
documented,
you
can
actually
automate
that
process,
so
I'm
gonna
be
looking
to
for
sure
document
everything
in
terms
of
the
process.
What's
expected
of
us
who
could
talk
to
you
and
then
finally
start
to
investigate
some
actions
that
we
can
actually
get
implemented?
This
first
tool
is
concerned
sounds.
K
A
Steven
so
open
discussion,
I'm
just
going
to
call
out
we're
going
to
have
an
EU,
friendly
release,
team
meeting
weekly,
so
I
think
the
best
way
to
attack
this
is
wait.
All
the
shadows
are
selected,
then
I
can
send
out
a
doodle
and
see
it
folks.
What
folks
would
like
to
do
and
then
we
can
get
one
scheduled,
I
think
in
previous
releases,
its
come
around
about
in
the
third
or
fourth
week.
A
If
that's
wanted,
but
I
hear
and
see
quite
a
few
people
in
that
region,
so
I
think
it's
probably
valuable
not
to
have
it
at
the
end
of
Monday
for
everybody
every
week,
so
is.
Is
there
any
objection
so
that
the
wait?
Oh
wait
till
we
get
all
the
shadow
selected,
then
I'll
send
something
out
to
everybody,
and
then
we
can
go
from
there.
Okay
are
there
any
other
items?
A
B
Yes,
I
have
this
is
not.
This
is
really
more
of
a
follow-up
because
it
has
been
mentioned.
I
would
be
very
curious
to
pool
all
of
the
efforts
to
automate
in
one
place
so
that
we
don't
duplicate
work.
I
was
not
here
for
the
last
release.
Team
I
want
to
know
what
Catherine
did
I
want
to
gather
all
that
information.
Just
so
we
can
not
come
up
with.
You
know
five
custom
solutions
depending
on
who
happens
to
be
working
on
it
at
the
time.
Is
there
an
issue?
Is
there
it?
B
B
B
K
De
Waal
and
maybe
Sheryl
as
well
so
when
we
broke
up
the
test
in
feral,
it's
been
divided
across
branch
management
and
and
bug
triage
and
test
in
front
on
call.
So
I
don't
think
that
bug
triage
got
any
of
the
responsibilities
to
date.
That
might
change
but
yeah,
but
most
of
the
stuff
is
broken
up
into
test
infer.
K
B
Yeah
I
might
ping
you
with
with
username
requests,
yeah.