►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200113
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
So
good
morning,
afternoon
and
evening,
fellow
people
of
communities
welcome
to
another
meeting
of
the
kubernetes
one
hitting
relay
relay
release
cycle.
I
am
your
humble
host
or
killer
cone,
and
this
time
I'll
actually
remember
to
mention
that
there
is
a
code
of
conduct
which
essentially
boils
down
to
be
nice,
be
kind
to
each
other
and
we
get
started
this
time.
I
also
wrote
a
note
about
asking
for
some
volunteer
to
take
notes
during
this
call,
and
with
that
let's
actually
get
started
this
time.
First
person
up
is
gonna,
be
lucky.
Please
take
care,
oh.
B
Thanks
George,
hello,
everybody
and
welcome
to
all
the
shadows.
We
have
a
full
roster.
My
name
is
Lachlan
Evensen
I'm,
an
emeritus
lead
on
the
118,
released
him
and
sorry
for
the
change
of
order.
I
have
a
doctor's
appointment,
so
I
asked
George
to
bump
me
up
earlier
in
the
order
today
so
appreciate
that
George.
So
a
couple
of
updates
from
me
first
one
is
the
shadow
selection
is
complete
and
I'd
like
to
say
a
massive.
Thank
you
to
all
the
leads
for
getting
that
done
in
a
timely
manner.
B
There
is
a
link
to
the
updated
roster,
which
is
in
the
repository
where
all
things
one
1.18
are,
so
you
can
take
a
look
there.
Thank
you
and
welcome
to
all
the
shadows
that
are
joining
this
call.
For
the
first
time,
we're
excited
to
have
you
and
the
release
team,
just
a
quick
reminder
to
the
leads
that
they
should
be
providing
their
shadows,
access
to
the
release
team
mailing
list
and
the
release
calendar
cig
release
calendar,
which
has
all
the
meetings
for
this
1:18
release.
B
So
just
make
sure
you
get
that
in
a
timely
matter
and
make
sure
if
you
have
any
questions,
feel
free
to
reach
out
to
me.
But
you
should
have
access
to
both
those
things
as
a
priority
and
then
will
follow
on
for
there.
I
will
be
sending
out
a
notification
to
all
applicants
in
the
next
24
36
hours,
just
thanking
them
for
applying
and
that
we've
chosen
the
release
team
and
to
encourage
them
to
apply
again
in
future
release.
B
So
just
appreciate
just
keeping
widespread
notifications
until
I've
sent
out
that
email.
That
would
be
great
and
finally,
I
will
be
reaching
out
to
all
the
leads
in
the
next
week
to
plan
and
schedule
shadow
orientation,
and
this
will
be
led
by
each
lead,
with
each
of
their
team.
Shadows
and
that'll,
be
just
an
onboarding
30
minutes
to
an
hour
conversation
with
all
the
shadows,
working
them
to
the
team
and
getting
them
access
to
all
the
resources
and
answering
any
questions.
A
Please
ask
me,
or
if
you
already
hey,
if
you
already
have
a
link,
go
to
the
internal
contact
sheet,
please
put
down
their
name
email
and
there
is
a
column
for
whether
they
have
a
they
still
need
to
get
access
to
the
mailing
lists.
If
not,
then
me
one
of
my
shadows
or
someone
will
eventually
get
to
it
and
send
the
money
bite.
Also,
please
check
your
email
for
a
lot
of
a
for
a
lot
of
people.
Just
shall
not
really.
Hopefully
they
they
already
got
a
invites.
A
B
C
A
Thank
you
for
that,
a
for
that
as
well.
You
can
either
I,
don't
think.
Lanky
is
gonna
mind,
but
a
you
can
a.
You
can
also
add
me
as
a
sponsor
or
Steven
a
one
of
us
if
you
had
one
of
us
as
a
sponsor,
eventually
a
Joe
getting
the
couple
a
in
the
governor's
organization
with
that
anyone
has
any
last
comments.
Questions.
A
D
F
I'm
Kirsten
no
video
right
now,
cuz
it's
early,
but
yeah
I'm
really
excited
to
be
a
shadow
I'm.
A
software
engineer
at
Red,
Hat
I
work
on
open
shift
in
1.17
I
was
a
shadow
for
bug
triage,
so
hi
Sylvia.
If
you're
here
and
yeah
I'm
really
excited
just
to
learn
a
little
bit
more
about
this
part
of
kubernetes
of
the
kubernetes
release
process
and
I'm
really
excited
to
meet
you
all.
So
hi
all.
G
Everyone
and
from
Bangalore-
and
this
is
my
second
pane
in
the
release
team
in
the
last
cycle-
I-
was
also
in
a
national
shadow
and
this
time
I'm
continuing
the
role,
but
from
that
I'm
reading
the
registrations
at
the
contributor
summit
for
keep
on
Instagram
and
yeah.
That's
it
I've
been
contributing
to
abilities
the
last
six
seven
months,
yeah
pretty
excited
for
this
civil
cycle.
Thanks.
H
D
You
so
much
super
excited
to
have
everybody
on
the
team.
So,
let's
jump
into
the
enhancements
update
for
today
we
have
been
pinging
all
of
the
open
issues.
There
are
a
hundred
and
nineteen
that
haven't
responded.
Yet
15
have
responded
with
the
affirmative
that
they
want
to
be
in
the
Monte
release.
One
of
them
doesn't
have
a
kept.
Let's
merge,
so
I
marked
it
as
at-risk
I
figured.
We
could
keep
track
of
these
things
as
we
go
on.
D
Just
have
an
idea
of
how
many
things
I've
said:
they're
gonna
be
in
the
milestone,
but
don't
have
all
the
criteria
to
meet
the
enhancements
freeze
yet
so
so
far
of
the
15
one
of
them
does
not
of
the
15.
We
have
seven
that
are
going
to
graduate
beta
five.
That
will
be
new
alpha
things
and
three
that
will
be
graduating
system.
I
J
Can
you
first
so
my
name
is
John
Reese
in
software
developer,
probably
for
about
nine
years
or
so
a
lot
of
that
space
and
Nancy
sharp.
But
me
as
a
company
working
at
Plex
systems,
not
the
the
media
server.
We
actually
do
manufacturing
software
just
took
the
name
somehow
somehow
it
got
away
with
that.
But
now
we've
been
transitioning
to
go
and
kubernetes
and
I
love,
open
source
and
contributing
so
I
kind
of
not
only
wanted
to
give
back,
but
also
just
learn
how
a
system
such
as
cooking
and
he's
so
big.
K
I
Exciting,
so
no
more
sad
words
today
there
were
able
to
join
the
ghost
of
the
timezone
stuff,
so
I
think
that
we
can
just
continue
with
the
reporting
okay.
So
this
week,
I
can
describe
our
situation
as
a
yellow
master.
Blocking
dust
boar
is
is
green
with
some
flake
itself,
but
it's
okay,
but
muscle
reforming.
There
are
many
jobs
that
are
failing.
I
So,
let's
start
I
hope
to
see
coach
master
reboot.
We
don't
have
any
response
from
see
cloud
provider
I
try
to
ping
them
again
today.
Hopefully,
in
the
next
days
we
have
some
activity
there
yeah.
So
then
we
have
other
two
jobs:
the
build
a
data
set
PMS
and
post
submit
of
the
release
level
that
are
failing
for
the
same
thing
and
it
seems
that
Steven
is
working
on
the
fix.
So
hopefully
we
won't
promote
this
as
soon
as
possible.
I
I
Then
we
have
three
other
jobs
that
we
find
out,
that
their
jobs
responsibilities
to
be
fixed
by
the
sink
videos
theme
see.
We
just
got
dinner
the
master
and
our
1.16
at
1.17
windows.
Jobs
are
failing,
I
tried
to
ping
with
the
steam
today
and
yesterday.
Maybe
they
didn't
have
the
chance
to
take
it
yet,
but
I
will
try
ping
them
pinging
them
in
the
next
days
as
well.
Other
two
jokes
that
they
felt
today.
I
This
is
master
skill
correctness
is
DC
master,
skilled
performance,
those
two
jokes:
our
protest
on
flakes
because
those
jobs
are
running
once
per
day
and
we
have
same
reasons
of
failure.
The
previous
days
as
well,
one
of
this
say,
have
already
draw
some
attention
and
we
change
the
priority
production
because
of
course
it
doesn't
seem
that
we
can
fix
it
right
away.
I
It's
like
testing
for
our
actual
issue,
so
we
will
consider
that
as
a
flag
well,
either
way
we
are
going
to
come
on
tore
down
them
in
the
next
days,
and
maybe
we
can
just
change
the
label
to
from
a
failing
test
to
flag
a
job
and
try
to
investigate
more
release.
Misc
everything,
greens,
flaky
jobs
in
one
place,
17
blocking
one
job,
is
failing,
which
is
the
same
with
a
job
in
muscle
forming.
We
expect
that
to
be
sore
the
next
day,
see
if
we
got
final
response
from
sick
cloud
provider
as
well.
I
In
one
point
in
informing,
we
have
two
other
jobs:
the
felling
for
the
same
reason,
like
the
other
two,
must
reform
as
well.
Okay,
so
this
release
we
decide
to
focus
more
on
flaky
jobs,
so
one
of
our
shadows
is
focusing
on
opening
issues
and
trying
to
find
more
details
about
how
any
flaky
job-
and
we
did
a
good
job
here
and
open
some
issues,
and
we
do
some
intentions
and
the
first
one
that
this
is
ingress
job.
It
seems
that
the
last
everything
runs.
It's
green,
nothing
mert's,
but
welcome
to
continue
wandering
it.
I
The
next
job
to
seek
goes
burdens
better
cereal.
It
stiff
like
if
we
have
an
open
issue
for
that
and
cost
burdens
better
default.
There
is
an
object
for
it
for
it,
so,
hopefully,
in
the
next
days,
when
we
melt
it,
do
you
see
some
progress
and
finally
remove
the
flakiness
of
it
so
that
this
equals
mastery
boot?
Okay,
that's
a
new
one!
Actually
I,
don't
know
George.
If
you
remember
in
1.16,
we
have
an
issue
about
it
about
this
is
the
same.
I
Frankness
of
the
same
tests
are
starting
flagging
again,
so
we
are
going
to
news
about
it
and
finally,
the
aggression
master.
It
seems
that
it's
it's
flaky
as
well
weapon.
This
is
who
gives
this
so
I
think
that
I
would
try
to
find
out
more
details
and
fixed
as
well.
However,
we
have
some
additional
notes
here.
I
didn't
put
those
but
I
tried
to
take
that.
It
seems
that
there
is
a
problem
with
Bosco
school
and
some
jobs
that
have
been
disabled
from
Friday.
It's
a
North
tenth,
so
I
don't
have
any
more
details
about.
J
I
have
that
fixed
in
a
PR
that
should
merge
today,
hopefully
the
so
for
a
bunch
of
the
tests
that
are
labeled
beta
gates,
beta
or
something
just
be
on.
The
lookout
for
potential
issues
with
those
I
have
a
PR
open
that
is
moving
basically
shifts
some
of
the
the
generic
version
suffixes.
So
that's
beta,
stable,
1,
2,
&
3,
it's
kind
of
a
chunky,
PR,
so
I'm
gonna,
try
to
see
if
I
can
maybe
break
it
out
into
multiple
ones,
but
essentially
it's
the
the
the
thing
to
note
is
that
version.
J
Generic
version
suffixes
are
bad
and
it
leads
into
a
bunch
of
problems
where
we
don't
understand
the
skew
that
the
tests
are
using.
So
upgrading
downgrade
that
say,
like
there
are
a
few
that
say
like
112
and
113
that
are
actually
using
like
stable,
1
and
beta
1
and
beta,
or
something
like
that
so
I'm
trying
to
knock
out
some
of
those
problems.
I
think
that
one
of
the
things
I'd
like
to
see
CI
signal
work
on
is
tweaking
some
of
those
tests.
J
There
are
some
easy
ones
to
fix
that
I'm
going
to
take
the
first
pass
at
once:
I've
merged
some
other
updates,
but
the
harder
ones
will
be
the
the
jobs
that
are
generated
as
a
result
of
the
generate
tests
that
py
script.
That's
in
testing
for
us,
so
that's
testing
for
us,
slash,
relevant,
generate
jobs,
underscore
generate
underscore
tests
pvy
and
that
one
uses
a
test
config
that
takes
a
bunch
of
different
a
fixes
so
like
GCE
or
gke,
cos
vs.
Ubuntu,
plus
a
generic
suffix,
plus
what
it
does
serial
default.
J
J
I'd
mentioned
this
in
the
sig
release
meeting
that
we
just
had
Jorge
and
I
have
been
talking
about
a
CI
signal,
sub
product
right,
so
expanding
the
scope
of
CI
signal
to
not
just
the
current
release,
but
all
of
the
blocking
informing
working
on
working
on
flakes
and
tooling
around
CI
signal
processes.
A
bit
more
extensively.
J
E
J
Will
be,
of
course,
reviewed
by
Jorge
right
right
and
hopefully,
I
got
it's
gonna
be
this
week,
but
early
next
week
at
the
latest
for
that
proposal.
So
if
there
are
people
interested
in
and
so
so
for
this
cycle
at
least
nothing
will
change
and
the
CI
signal
team.
J
But
the
idea
next
cycle
will
be
essentially,
there
will
be
like
a
CI
signal
liaison
which
will
handle
the
master,
blocking
informing
everything
around
master,
blocking
and
forming,
and
the
current
release
branch
of
blocking
and
informing
and
making
sure
that
that
signal
is
good
and
the
entire
team
will
be
responsible
for
all
of
the
open
release
branches.
So
stay
tuned
for
more
details
on
that.
If
anyone
is
interested,
please
let
me
know
and
you'll
be
included.
Oh.
I
That's
a
good
news,
though
one
more
thing
I
wouldn't
wash
to
what's
the
plan
about
the
1.14
jokes
right.
J
J
J
The
idea
is
that
we
want
to
disambiguate
the
removal
of
the
last
supported
jobs
from
the
cut
of
the
release
branch.
Those
those
two
things
don't
need
to
happen
together
and
we're
basically
putting
money,
spinning
up
tests
for
branches
that
we
don't
support
anymore.
So
that's
the
reason
Thanks,
so
I
I,
believe
everyone
is
tagged
on
that.
Pr.
Give
me
a
rather
the
CI
signal
team,
as
well
as
release
engineering.
People
who
are
part
of
those
github
teams
are
tagged.
E
A
A
L
A
He
was
still
being
investigated
by
Katherine
and
all
the
wonderful
people
in
cig
testing
and
the
more
important
note
is
I
believe
every
single
job
uses
cheeky
for
for
a
foreign
end-to-end
test
is
actually
on
post
right
now.
So
you
might
hear
so
for
some
reason.
Someone
who
looks
a
finds
a
job,
the
has
an
into
with
jjigae.
You
might
not
be
seeing
any
results.
The
other
thing
that
I
wanted.
The
other
thing
that
I
wanted
to
bring
up
is
the
GC
cause
must-have
reboot
in
twin
jobs,
actually,
all
of
them
we
might.
A
That
is
that
that
was
deprecated
by
cluster
fly
cycle,
and
essentially
it's
just
one
of
those
were
a
contributors
might
come
in
fix
it
and
that's
what's
been
keeping
it
alive
in
the
last
handful
of
cycles,
but
we
don't
actually
have
a
group
of
owners
and
that's
why
it's
in
the
cloud
you
see
a
clown,
GCSE
cloud
GCP.
So
if
we
can
fix
it,
you
might
be
useful.
If
we
cannot
fix
it,
we
might
actually
look
into
removing
it
as
we
did.
We
thought
they
upgrade
in
down
greatest
so.
J
On
that
note,
so
yes,
Katherine
has
disabled
all
of
the
gke
tests.
Any
tests
that
you
see
that
are
listed
as
G,
K
or
GC
GC.
Consider
them
suspect
because,
like
like
query
said
there
are,
there
are
pretty
much
no
owners
there,
we're
assumed
to
be
the
de
facto
owner
of
these
jobs,
which
is
not
correct
ish.
So
we
should
be
looking
for
opportunities
to
delete
these
jobs
where,
if
they're
not
providing
value
I
also
want
I,
would
love
for
CI
signal
to
be
watching
these
boards.
J
The
job
config
errors
board,
as
well
as
the
generated
board
the
generated
board.
You
won't
be
able
to
see
all
the
things
on
the
boards,
because
there
are
that
many
so
yeah,
so
job
config
errors,
there's
a
little
slew
thing
that
would
be
involved
in
that
essentially
job
configures
are
a
variety
of
things
that
I
decided
were
configures,
one
of
them
being,
if
it
only
lands
on
a
cig
release.
J
Dashboard,
like
I,
considered
a
configure
because
there
should
be
an
owner
for
the
job,
so
it
landed
in
job
configures
if
it
is
using
a
generic
suffix
like
the
the
table
and
the
generic
suffix
does
not
match
the
release
that
it's
targeting
and
that's
a
job
configure
to
me,
but
see
if
you
can
look
at
the
configs
within
the
cig,
release
job
config
errors,
board
and
figure
out.
What's
up
with
them,
some
of
the
work
that
I'm
doing
on
that
PR
should
fix
some
of
them.
J
Some
of
the
work
that
Catherine
is
doing
on
the
gke
side
fix
others.
The
work
that
we're
doing
together
on
the
tweaking
the
generate
test
script
should
fix
even
more
of
them,
but
it
will
take.
It
will
take
some
more
eyes
to
determine
like
are
these
things
being?
Are
these
things
being
attended
to?
Have
they
been
failing
a
lot
across
multiple
cycles
do
like?
Are
they
being
useful
to
people?
If
not,
we
should
get
rid
of
them
so
totally
an
agreement
there.
A
I
I
J
So
the
idea
of
the
generated
dashboard
was
to
get
them
off
of
the
dashboards
that
they
shouldn't
have
been
on
because
they're
generated
there
are
a
lot
of
them,
because,
basically
it's
a
way
of
us
looking
at
one
dashboard
and
being
able
to
say
okay
well,
at
least
we
know
these
are
all
generated.
The
reason
they
are
ending
up
on
that
dashboard
is
because
the
generated
tests,
the
generated
test
script
will
go
in
and
say
before.
It
was
doing
all
right.
J
Well,
this
should
blend
on
master
blocking
or
they
should,
if
it's
not
unblocking
or
not,
on
informing
or
something
it
should
land
over
here
great
I
tweaked
that
to
just
put
everything
on
generated
because
they
they
were
jobs
that
were
commonly
not
being
attended
to
right,
so
I
consider
that
kind
of
a
job
configure,
but
not
a
job
configure.
That
is
a
manual
job
configuration
it's
a
generated.
J
Job
configuration
so
I
know
that
that
board
should
eventually
maybe
go
away
as
long
as
as
long
as
they,
the
jobs
that
are
configured
on
that
board
actually
begin
to
have
owners
right
if
we
determine
that
they
never
have
owners
and
the
entire
board
goes
away.
All
of
those
job
goes
go
go
away
right,
so
it's
just
kind
of
a
you
know
the
facto
parking
lot
for
for
generated
jobs.
I
J
A
L
N
The
same
Anna
I'm.
L
O
P
Q
Everybody,
my
name
is
Marky
I
am
a
software
engineer
at
Cystic
and
I
work
on
Falco
I
did
bug
triage
for
117
and
I
also
do
a
lot
for
the
the
contributor
summit
for
cube
cons.
So
everybody
knows
me
I
hope
and
if
you
don't
welcome
to
everybody.
M
Yeah
once
again
welcome
everybody
happy
to
have
you
in
the
in
the
team
and
moving
on
to
the
current
status
for
bug
triage.
So
we
are
green,
and
this
is
because
we're
not
really
paying
a
lot
of
attention
to
the
to
the
numbers
of
issues
and
PRS
in
this
stage
of
the
of
the
release
and
we
have
51
open
issues
and
on
tests
or
flakes
and
56
open
PRS
with
77
in
total
issues
open
for
118.
So
in
this
one
18
milestone
and
like
I
said,
I
mean
it's
so
early
in
the
in
the
release.
M
M
R
G
S
G
G
You
and
we
have
a
fourth
person
this
time
like.
Why
are
we
like?
She
is
not
here.
Yes
like
this
time.
We
have
four
shadows
for
the
dog,
so
I
just
increased
one
number.
So
usually
we
have
three
and
then
this
time
we
met
before
yes,
I'm
coming
to
the
status
of
the
dogs.
We
are
right
now,
green,
as
we
don't
have
much
to
do
any
dogs
tracking
at
this
point
of
time,
but
next
week
we
are
planning
to
do
a
shadows
on
boarding.
So,
yes,
we
are
green
from
dogs.
Thank
you.
J
Just
just
a
note
on
the
dark
side
that
Jim
I'm
not
sure
if
Jim
angel
is
on
the
call,
but
he's
gonna
be
working
on
improving
the
the
Krell
fast
forward
tool
which
handles
branch
fast
forwards
and
step
stuff
to
hopefully
use
that
for
the
to
hopefully
use
that
for
the
docs
side
as
well.
So
Doc's
has
a
branching
workflow
that
we
would
like
to
make
easier.
So
please
work
with
Jim
as
he
asks
for
things.
If
he
asks
for
things
around
Doc's
branch
management
that.
J
U
V
W
Hi,
my
name
is
James
I'm
a
Solutions
in
today
with
jet
stack,
which
is
a
EQ
days.
Consultancy
based
in
the
UK
I'm,
pretty
new
to
the
community
I
attended
Kubek
on
San
Diego
and
I
asked
how
to
get
involved,
and
there
suggested
I
applied
to
be
a
shadow
on
the
release
team
and
thus
Here
I
am
so
I'm
working
to
do
awesome.
X
U
Awesome
thanks
everyone
for
trying
to
come
on
board
to
the
shadow
team
and
looking
forward
to
working
with
you
guys
on
this
lease
on
this
release,
just
update
on
our
site.
We
are
green,
the
release
notes,
draft
has
been
submitted
and
the
PR
the
requisite
PR
is.
Is
there
a
PR,
99037
and
also
release
notes
Cates
that
IO
has
been
updated
with
the
1.8
zero
alpha
one?
U
P
J
J
It's
and
I
think
that
this
is
I,
think
that
this
is
the
right
move.
I
just
want
to
make
sure
the
PRS
looks
to
already
be
ready
and
have
been
ready
for
a
while
I
think
all
I
want
to
make
sure
we
do
is
gather
consensus
from
the
community,
since
these
are
things
that
everyone
consumes.
So
the
idea
here
would
be
I
also
want
to
introduce.
Maybe
the
idea
of
like
what
kind
is
more
important
right.
So
a
deprecation
is,
is
super
important
and
you
should
know
about
that.
J
J
U
J
I
believe
so,
I
haven't
I,
don't
look
at
the
content
appear
in
a
bit?
Yes,
the
tool,
that's
yes,
a
package
notes
document
go
and
an
package
notes,
notes.
Co
are
being
updated,
yeah,
so
just
stay
tuned
for
that.
Sasha
has
been
kind
of
all
over
this
stuff
in
the
refactor
of
our
in
the
creation,
I
guess
of
Krell
release,
notes
or
whatever
we're
calling
the
thing
now,
but
yeah.
So
so,
sync
up
with
Sasha
and
just
make
sure
you
have
details
on
what
direction
he's
going
in
kind
of
like
sure,
okay,.
Z
Y
Z
Perfect
Paul
are
you
there
yep.
AB
Claudia
hi
everyone,
my
name
is
Claudia
I
am
a
software
engineer
based
in
Seattle
I
work
at
Microsoft,
I'm,
the
commercial
software
engineering
team,
I
work
with
docker
and
kubernetes
in
the
daily.
So
I'm
really
excited
to
contribute
to
this
upcoming
release
and
learn
more
about
the
release
cycle
and
then.
Z
J
So
just
a
note
for
comms
I
want
to
make
sure
that
so
one
I
think
we've
discussed
this
for
people
who
are
already
on
117
and
attended
the
retro
on
all
that
good
stuff.
Releasing
on
Mondays
is
bad.
We're
not
going
to
do
releases
on
Mondays,
so
it
was
Tuesday
and
forward,
but
in
that
also
requires
communication
to
scan
CF
and
press
and
yada
yada
yada.
So
I
would
request
this
cycle.
Can
we
make
sure
that
anything
that
goes
out
to
an
external
person,
whether
it
be
CNC,
a
press?
J
Whatever
include
the
sig
chairs,
include
the
sig
chairs
and
the
release
team
leads
on
that
communication
or
just
the
release
team
leaves
I
want
to
make
sure
that
there
are.
We
had
a.
We
had
a
miscommunication
about
a
date
which
caused
a
few
internal
things
to
go
crazy,
as
well
as
external
things
to
go
crazy,
so
I
want
to
just
make
sure
that,
like
we
have
multiple
eyes
on
these
emails
going
out
externally,.
J
Yeah,
so
my
note
here
is
I
noticed
that
I've
been
I've
been
added
to
the
notes,
as
as
the
branch
manager
I'm,
not
the
branch
manager
for
the
cycle.
I'm
a
faculty
member
Carlos
is
the
primary
branch
manager
for
the
cycle.
Sasha
is
the
secondary
for
the
cycle,
so
they
should
be
about
roughly
splitting
up
the
roughly
splitting
up
all
the
releases
across
the
cycle,
as
well
as
introducing
the
release
manager
associates
to
the
process.
J
So
les
last
cycle
we
had,
we
had
Marco
and
and
Sascha
basically
take
the
wheel
for
an
alpha
write
to
see
if
they
you
know,
can
walk
through
the
the
alpha
cut.
So
we're
gonna
continue
doing
that
the
cycle,
but,
like
I'm,
happy
to
answer
any
questions
that
you
all
need
on
like
release.
Engineering
overall,
but
Carlos
is
the
primary.
So
please
forward
any
branch
management
related
things
do
nothing.
Yes,.
AD
J
So
that
means
that,
between
the
time
that
we
initially
cut
the
alpha
for
118
say
there
were
multiple
commits
I
think
1800
plus
commits
to
master
since
then
right
to
get
to
get
people
to
a
point
who
are
consuming
kubernetes
to
get
them
to
a
point.
That's
more
closely
in
line
with
what
118
would
look
like
we're
planning
to
I
have
an
action
item
to
add
that
to
the
branch
management,
a
handbook.
J
So
basically
you
handle
all
of
your
cycle
plus
you
handle
so
if
you're
on
118,
you're
handling
all
the
releases
for
118
and
then
you're
also
cutting
the
119
alpha
one
right.
So
that
way
we're
in
line
before
we
start
the
next
cycle,
so
we'll
see
that
PR
just
shifts
shifts
the
release
numbers
in
the
release.
Schedule
down
a
number
right.
AD
A
J
There
is
a
release,
managers,
MD
and
what
I
can
do
is
edit
it.
So
so
it
says,
who's
primary
and
secondary
the
primary
and
secondary
thing
is
kind
of
like
all
the
stuff
we
do
is
kind
of
new,
but
it's
essentially
just
to
make
sure
that
there
is
a
single
or
a
few
points
of
contact
right
now
there
are
only
there
are
only
two
branch
managers.
We
hope
to
build
that
up
in
the
following
cycles,
but
but
yeah
as
there
as
there
going
to
be
more.
J
We
want
to
know
that
there
one
there's
a
body
of
people
who
can
handle
the
work
if
y'all
need
them
to
handle
certain
things,
but
also
that
you
have
a
dedicated
resource
to
the
release
team
right.
So
so
we
want
to
make
sure
that
the
primary
and
secondary
are
attending
release
meetings
and
providing
status
updates,
and
all
that
good
stuff
here
is
the
link
in
the
chat.
Let
me
actually
put
it
in
yeah.
AA
E
A
AC
AC
A
Thank
you
very
much
for
that
wonderful
introduction
and
for
agreeing
to
be
a
shadow
you
make
an
edge
of
making
the
whole
process
so
much
easier
and
that
Mia
was
pressurized
would
start
around
anymore.
So
let's
just
leave
that
one
for
later
I
think
I
think
she's
in
India
and
there
are
a
handful
of
hours
a
so
so
it's
like
I'm,
pretty
sure
it's
closer
to
midnight
or
something
so
moving
on
to
release
leader
updates.
A
So
a
couple
a
couple
things
that
in
a
couple
things
that
I
just
mentioned
that
is,
and
that
I
just
mentioned
in
the
notes-
is
this
time
around.
We
are
change
a
we
have
been
changing
the
whole
the
important
process
for
foreshadow.
So
as
I
as
we
previously
mentioned,
there's
a
contact
sheet.
All
leads,
please
add
your
shadows
in
there
a
please
make
sure
to
have
an
a
to
have
an
email
for
them
and
we
will
make
sure
to
get
everyone
in
the
community
is
a
release.
A
The
mailing
list,
which
is
the
one
source
of
truth
for
all
meaning
same
and
the
stuff
other
than
that
reached
out
to
seek
two
six.
Eight
two
people
from
six
color
will
marry
hope
into
two.
What
we
on
just
I
just
talked
it.
It
just
told
me
to
keep
the
communication
moving
forward
and
from
the
last
cycle
the
format
was.
Somebody
from
scalability
was
going
to
make
sure
to
drop
an
update
before
before
this
meeting
started
in
our
MIDI
notes
and
usually
because
of
time
differences.
A
Is
that
that
easy
to
get
someone
to
actually
come
from?
$6
million
speak
a
speak
for
the
update,
but
you
know
if
they
can
write
it
down.
We
can
read
it
in
the
other
thing
that
I
actually
added
good
in
procedurally,
because
I
didn't
I
didn't
last
time
a
last
a
last
check,
not
everyone
has
channels
but
I'm
planning
to
send
Durrell.
Some
is
something
this
week
a
please
please
pass
around
a
please
pass
it
on
to
everyone
who's,
a
member
of
the
release
team.
We
want
to
that.
The
rule
is
torn
away.
A
I
want
a
doodle
just
to
see
if
people
want
to
move
this
mean
some
other
time
some
other
day
and
also
possibly
another
doodle
or
some
sort
of
a
you
know,
format
pending
some
way.
It's
a
one
we
want
to
see
if
people
want
to
move
this,
meaning
to
some
other
time
to
some
other
day.
The
second
thing
is:
we
also
want
to
check
if
people
from
if
people
a
want,
the
second
meeting,
a
that's
more
Europe
or
Asia
friendly,
and
those
are
my
action
items
obvious
a
couple
at
least
a
couple
things.
A
A
couple
things
and
I
haven't
I
was
planning
to
do
for
this
week
and
my
in
that
affect
everyone
else
in
the
released
him
other
than
that
a
common
milestones.
So
last
week
we
began
enhance,
enhance
miss
tracking
and
this
week
the
plan
was
for
this
week
to
finalize
the
release
team.
It
seems
like
that's
the
thing
and
other
than
that
after
to
next
Tuesday,
with
that
anyone
has
any
comments.
Questions
concerns
well.
R
K
J
You
know
I
said
it
and
I
don't
really
know
I'm
gonna
do
a
doodle
you'll,
do
a
doodle,
we'll
choose
an
end
date
and
you
know
I
figure
that
I.
You
know
if
I
put
it
out
today,
then
maybe
we
can
close
it
next
Wednesday
and
that
should
be
sufficient
time
for
people
to
vote,
and
then
we
can
start
up
with
a
new
the
new
time
for
release
and
release
engineering
on
the
week
of
the
27th.
A
A
J
Yeah
first
so
I
just
want
to
say
awesome
job
so
far.
I
think
that
this
is
the
quickest
I've
ever
seen,
shadows
get
locked
in
and
the
coordination
so
far
on,
the
the
118
team
has
been
incredible
between
the
release
team
leaves
and
and
the
and
the
emeritus
advisor
locky.
Thank
you
for
cracking
your
advisor
wit
seriously
that
that's
I
think
it's
the
fastest
it's
ever
been
done,
and,
and
that
means
that
the
shadows
have
more
time
to
settle
into
the
release
cycle.
So
so
thank
you
all
for
for
making
that
experience
positive
for
everyone.
A
Say
a
second
that
thank
you
very.
Thank
you
very
much
for
all
the
way
for
all
the
work
that
it
is
lucky.
Okay.
Hopefully,
you
can
hear
this
in
the
recording
and
thank
you
very
much
for
all
the
leads
for
doing
this
so
efficiently
and
actually
one
last
note,
I
was
thinking
the
next
week.
I
was
actually
I
was
actually
trying
to
wait
for
all
the
shadows
to
be
selected,
but
what
you
all
think
about
it
next
week,
starting
to
go
through
the
release
team
project
born
I,
do
not
week
on
a
weekly
basis.
J
A
Sounds
perfect,
so
there's
work
starting
next
week.
Hopefully
everyone
it's
gonna,
enjoy
it
with
that
I
mean
last
issue
is
comments.
Anyone
wants
to
bring
up
going
once
twice
sold
so
again.
Thank
you
very
much
for
everyone.
Thank
you
very
much
written
in
this
meeting.
Thank
you
so
much
for
volunteering
for
volunteering
to
work
on
the
release
team.
You
are
all
awesome
and
amazing
people
and
hope
a
hope.
You'll
have
a
nice
rest
of
your
Monday,
see.