►
Description
A
Okay,
cool:
let's
go
ahead
and
get
started
so
good
morning.
Everyone
today
is
February
12
volt
good
morning
for
me,
because
I'm
not
in
standard
time.
For
me,
it's
9:00
a.m.
I
know
for
some
of
you,
you
may
perhaps
be
another
time
of
day
I'm
Mike
or
paya
I'm.
The
release
lead
shadow
for
114
pleasure
to
be
hosting
your
release
team
meeting
today.
This
is
the
first
european
time
zone
meeting
that
we're
gonna
do
for
the
1:14
release.
A
So
if
this
goes
well,
we'll
continue
doing
this
every
release
and
if
people
find
it
helpful,
let
me
know
and
keep
them
going,
but
yeah.
This
is
just
to
make
sure
that
there's
a
bit
of
a
friendlier
time
for
people
in
other
time
zones,
because
we
have
pretty
wide
distribution
on
the
release
team.
Especially
this
release
reminder.
This
is
a
recorded
meeting.
It's
going
to
be
posted
on
the
internet,
so
you
know,
follow
the
kubernetes
code
of
conduct,
which
basically
boils
down
to
don't
be
a
jerk
alrighty.
A
So,
as
far
as
how
this
meeting
is
gonna
go,
there's
a
release
team
meeting
yesterday
that
some
of
you
were
at
some
might
not
have
been
at
it.
So
what
I'm
going
to
do
is
basically
give
brief
summary
of
the
release
lead
section:
oh
yeah,
it's
great!
Please
thank
you
Jeff!
So
please
go
to
that
doc
that
Jeff
just
posted,
which
is
the
release
team
meeting
minutes
and
put
your
name
under
the
attendees
so
that
we
can
just
you
know,
track
who
comes
and
make
sure
that
you
know
we're
taking
notes.
A
So
since
there's
only
a
few
of
us
today,
one
thing
I
want
to
do
just
so
you
know
perhaps
get
to
know
each
other
loom.
Why
I
mean
I
know
some
of
you
already
to
varying
degrees,
but
I
would
love
to
just
go
around.
Introduce
yourself
say:
are
you
you
are
you
in
a
European
time
zone
or
you're
you're
just
joining,
because
you
happen
to
be
awake?
What
team?
What
like
role?
B
I'll
go
next
in
some
left
of
you
on
my
screen.
My
name
is
Jeffrey
chica
I'm
the
release,
notes,
shadow
for
this
release
and
I
figured.
We
should
try
and
have
representatives
from
each
team
on
here
and
I
wasn't
sure
if
anyone
else
release
notes
was
gonna
hop
on
so
I
have
done
and
I'm
in
Eastern
time
zone.
So
it's
like
11
o'clock
for
me.
So
this
is
more
or
less
my
lunch.
C
D
E
I'm
Alexander
Nevsky
I
work
for
interim
based
in
Finland
I,
was
mostly
participating
in
our
six,
like
quasi
life
cycles,
hid
node,
a
resource
management
and
so
on.
To
me
it's
always
was
interesting
to
see
like
what
is
happening
in
released
him.
Unfortunately,
for
me
it
was
like
really
late
at
night,
so
happy
to
see
what
there
is
some
European
activity.
I
don't
know
if
I
can
contribute
this
cycle
much
to
it,
but
let's
see
maybe
next
cycle
a
little
bit
more
given
wisdom
as
well.
You.
F
F
A
Great
well,
awesome
I
think
you
know,
since
smaller
meaning
that
makes
much
more
personal.
Now
that
we've
all
gotten
to
know
each
other,
so
cool,
so
I'm
gonna
go
through
Erin's
updates
and
if
you
know
my
Internet's
been
a
little
flaky
today.
So
if
I
start
to
break
up
just
either
send
a
message
or
wave
your
arms
and
I'll
shut
off.
My
video
and
I
know
you'll
all
be
sad,
but
it'll
probably
make
for
higher
throughput
communication.
So
most
notably
we're
halfway
through
the
release
this
week
today
is
also
today.
A
Tuesday
is
me
dot
one
14.0
alpha
3
is
being
cut.
So
that's
awesome,
honest
probably
talk
more
about
that
and
how
that's
going,
perhaps
that's
underway,
who
knows,
but
that
exceptions
coming
soon
we
have
burned
down
in
two
weeks,
which
is
a
noteworthy
thing
that
I
think
everyone
is
preparing
for
and
if
you're
wondering
when
the
114
release
is
finally
going
to
be
cut,
that's
going
to
be
in
just
under
six
weeks
or
five
weeks,
six
days
on
a
Monday,
so
that's
really
exciting.
A
It's
getting
pretty
close
and
it's
gonna
get
really
busy
really
quickly
over
the
next
few
weeks.
So
that's
awesome
and
if
you
were
wondering
how
you
can
know
when
all
of
these
dates
are
Aaron
put
together
a
release
team
calendar
for
114,
so
we've
had
this
kind
of
for
a
few
other
releases
in
the
past.
It's
really
useful.
It's
basically
just
you
know
exactly.
A
It
sounds
like
a
shared
calendar
and
if
anyone's
not
familiar
that
I'm
happy
to
share
my
screen
and
show
this
I
also
I
did
pull
up
like
I
was
going
through
the
notes,
the
things
that
there
are
a
few
things
where
people
were
referring
to,
like
you
know
certain
things
about
caps,
the
enhancements
calorie
I'll
show
my
video
is
that
better?
Can
you
guys
hear
me
now?
A
Hopefully,
alright
so
I
noticed,
there's
a
few
I,
don't
know
if
my
internet
is
going
to
allow
it,
but
I
did
notice
that
there's
a
few
like
Docs
and
web
pages
and
various
things
that
different
roles
you
use
as
a
part
of
their
role.
So
if
anyone
is
interested
in
any
of
them,
I'm
happy
to
share
my
screen
and
pull
them
up
just
to
show
y'all
where
you
can
get
at
this
information,
but
but
yeah.
That's
that's
that.
A
So
we
have
a
shared
calendar
now,
if
you
need
a
link
to
it,
it's
in
the
it's
in
the
minutes.
So
add
that
to
your
calendar,
it's
good
stuff
yeah
and
the
last
thing
that
I
talked
about
was
reviewing
a
cap,
so
enhancements
see
I
signal,
Doc's,
release,
notes
all
have
kind
of
explicit
things
that
are
different,
that
they
should
be
looking
for
through
the
cap.
So
just
familiarize
yourself
with
you
know,
go
through
the
issues.
A
Click
the
milestones.
Look
at
the
114
milestone,
see
what
kept
sir
in
there.
This
is
also
roughly
analogous
to
the
enhancements
tracking
spreadsheet
so
check
that
out
as
well,
if
you
prefer
that
format,
but
just
get
familiar
with
what
caps
are
doing
in
getting
understanding
for
the
feature
site,
look
through
the
caps,
if
you
see,
if
you're,
on
the
release
notes,
for
example-
and
you
see
things
that
are
in
the
caps
that
aren't
in
the
release,
notes
or
vice-versa,
you
know
this
is
noteworthy
so
stuff
like
this.
A
You
know:
pay
attention
to
the
graduation
criteria
and
the
testing
checklists
and
stuff
like
this
and
just
make
sure
that
we're
on
top
of
what's
going
into
the
release
because
we're
trying
to
make
enhancements
the
primary
you
know
representation
of
what's
going
into
the
release
and
I.
Think
in
my
opinion,
that's
definitely
the
most
significant
change.
That's
happening
that
this
releases,
our
commitment
to
caps
and
so
far
so
good
so
and
I,
don't
think.
There's
anyone
from
in
Hanson's
here
so
I
will
just
continue
here.
A
Basically,
the
kept
deadline
we
wanted
was
for
the
cap
to
be
merged
with
this,
like
the
the
document
in
the
enhancements
repository
to
be
merged
with
a
status
of
implementable-
and
you
know
that
was
not
the
case
for
a
good,
fair
bit
of
the
caps,
so
there
were
seven
exceptions
improved
for
a
total
of
forty
enhancements
now
for
114
12
alpha
features,
14
beta
features
and
10
stable
features.
Now
this
week
the
enhancements
team
is
basically
going
through
all
the
caps
making
sure
that
they
have
an
accurate
representation
of.
A
What's
going
in
making
sure
there's
nothing,
that's
miss,
making
sure
there's
not
gonna,
be
anything
complicated
with
a
any.
You
know,
feature
development,
that's
going
on
that
perhaps
doesn't
have
kept
yet
and
stuff
like
this.
So
that's
awesome.
If
you
have
a
feedback
on
the
on
the
caps
process,
please
talk
to
Claire,
myself,
Ben
or
obviously
Aaron
and
we'd
love
to
talk
to
you
great,
that's
getting
that's
enhancements
any
questions
about
enhancements
or
the
any
of
the
things
I
talked
about
in
the
release
lead
update.
A
A
D
So,
actually,
this
morning,
I
just
sent
out
the
CI
signal
report.
If
you
guys
want
to
go
a
look
more
in
depth
at
it
other
than
that
things
seem
to
be
getting
a
little
bit
better.
Last
couple
of
weeks
was
a
bit
of
a
big
red
plump
one
desperate
there
are
now
only
two
failing
tests
on
must
master
blocking
make
a
lot
of
a
lot
of
the
flaky
once
they
have
been
have
been
resolved
in
the
last
couple
days.
We're
still
working
on
a
master
of
great,
they
seem
to
be.
D
A
Okay,
no
worries
for
bug
triage
yesterday.
Nico
talked
about
three
topics.
Basically
in
the
meeting.
The
first
was
that
metrics
look
normal
so
far,
but
you
know
the
second
topic
he
made
note
of
was
that
we
still
have
three
weeks
until
freeze.
So
you
know
they're
just
a
lot
of
active
development,
that's
happening
and
that's
going
to
continue
to
happening
that
or
it's
going
to
need
to
happen.
So
we
need
to
you
know
be
mindful
of
the
fact
that
things
could
change
at
any
moment
and
constant
vigilance.
A
Hiko
also
enumerated
three
proposals
for
tracking
autumn
for
tracking
automation.
Okay.
So
if
this
is
interesting
to
you,
then
please
check
out
his
three
proposals
and
offer
feedback.
I
don't
want
to
do
anyone
a
disservice
by
trying
to
explain
his
proposals,
so
I
won't,
but
they
are
on
the
minutes.
So
please
check
them
out.
Is
there?
Are
there
any
questions
about
any
anything
with
regrets
about
triage
all
right,
great
I'm
gonna
meet
real,
quick
and
sharpen
my
pencil.
A
A
A
lot
of
aspects
of
you
know,
testing
and
releasing
yeah
each
release
happen
via
CI,
so
the
the
team
has
added
the
CI
jobs
and
there's
also
some
new
automation
for
creating
these
jobs,
so
that
in
future
releases
it
will
not
be
as
much
of
a
manual
process
to
create
DCI
jobs,
for
you
know,
115
and
on
that's
awesome
there.
Unfortunately,
we're
prow
and
github
outages
last
last
week
that
everyone
had
to
contend
with.
You
know.
Unfortunately,
software
goes
out.
Sometimes
we
live
with
it.
Any
questions
for
testing
structure
rated
thanks
all
right
awesome.
A
Pindy
my
meeting
give
chance
so
for
docs
I
would
just
there
were
no
significant
updates
really
last
week
other
than
the
fact
that
Doc's
and
release
notes
are
going
to
be
syncing
up
to
kind
of
you
know,
synergize
a
little
bit
and
the
person
who
is
doing
the
docs
update
yesterday
Jim
referenced.
How
you
know
people
had
told
him
from
you
know:
sick
Doc's,
to
chat
with
the
release
notes.
Folks,
I
also
after
last
shoot
con
had
after
I
give
my
release
notes.
A
Lightning
talk
had
a
conversation
with
Jen
from
sick
Doc's
and
we
had
dinner
and
it
was
great
and
we
talked
about
a
lot
of
different
Docs
and
release,
notes
things
so
I
agree
with
Doc's
folks
that
sigdoc
since
or
did
the
docs
lead
in
the
release,
notes
lead
have
a
lot
of
you
know:
potential
hashtag
synergies
that
could
be
made
so
I
agree,
they're
kind
questions
for
docs
before
we
get
into
release,
notes
where
it's
a
release
is
actually
extremely
well
represented
today,
so
Jeff
for
Lindsay
and
or
Lindsay.
B
Do
this
one
because
Lindsay
did
yesterday,
if
you
don't
find
so
we
had
a
meeting
yesterday
to
kind
of
get
both
Doc's
Communications
and
release
notes
on
the
same
page,
and
really
that
was
mainly
a
Arin
talking
with
the
comms
people,
to
figure
out
the
blog
schedule
and
just
letting
Docs
and
release
notes,
know
if
there's
something
relevant,
please
let
them
know
ahead
of
time,
because
we're
gonna
be
the
ones
in
the
weeds
actually
paying
attention
that
sort
of
thing.
Also,
yesterday
Lindsay
updated
the
release
notes
draft
for
the
week.
B
So
if
people
want
to
take
a
look
and
see
what's
been
updated,
that
would
be
good.
That's
in
the
cig
release
repo
under
114.
What
else
has
been
happening?
We've
started
to
gather
themes
from
all
of
the
SIG's,
we're
gonna
be
reaching
out
over
the
next
couple
of
weeks
and
actually
getting
what
they
want
out
in
the
release
notes,
and
that's
that's
more
or
less
it.
This
was
kind
of
a
Down
week
for
us.
The
next
couple
weeks
start
getting
busy
nice.
A
And
I
was
traveling
towards
the
end
of
last
week,
but
I
promised
for
sure
that
I
will
get
y'all
merged
into
the
release.
Repository
with
the
reason
it's
I
swear,
it'll
happen,
I
just
need
to
add
some
hashes
to
the
basal
dependencies
because
nobody
likes
pulling
down
dependencies
that
I'm
not
checking
the
hashes,
though
you
know
you
know
it's
a
good
time
for
that.
Awesome
well
sounds
good.
The
next
section
was
comms,
so
anyone
here
from
combs
I
don't
think
so.
Anyone.
A
So
basically,
I'm
not
too
familiar
with
the
comms
process.
However,
from
what
I
can
gather,
it
seems
like
they
are
pretty
heads
down
on
preparing
the
blog
for,
like
the
release,
blog
topics
and
they're
gonna.
Do
a
five-day
blog
series,
so
they're
having
a
series
of
meetings
about
coordinating
this
planning
topics
planning
the
execution
of
it.
So
if
you're
interested
in
this
and
please
ping
etosha
and
you
know
who's
in
woods,
3
on
slack
and
she
will
for
sure
add
you
to
the
to
the
meeting
awesome
and
now
Hannes.
C
So
114
alpha
3,
has
been
cut
today
a
couple
of
hours
ago.
So
that's
out
before
doing
that.
I
wanted
to
give
my
shadows
yesterday
evening.
My
time
which
is
like
noon
to
evening
us
time,
I
guess
a
quick
run-through
one
on
what
this
means,
because
we
wish
we
don't
give
all
the
shadows,
all
the
X's
to
all
the
things
right
away.
So
that
means
we
need
to
pare
on
stuff
that
went
horribly
wrong
because
screen
sharing
and
stuff
did
not
work.
C
So
what
that
means
is
I
will
try
for
the
next
things
for
the
next
cuts
and
for
whatever
we
need
to
do
to
find
a
more
us
friendly
time
and
we
have
to
pair
with
them
on
the
actual
thing
other
than
that.
What
is
interesting,
let
me
see
so
there
was
a
whole
discussion
about
packages
in
the
last
couple
of
weeks
and
see.
Cluster
lifecycle
started
working
on
the
generation
of
the
package
of
the
packages
and
I
linked
the
issue
on
that
on
on
where
they
are
tracking
progress
in
D.
C
In
our
meeting
dogs,
however,
there
was
it
was
unclear
to
me,
because
the
thing
is
they
already
started
working
on
that
without
me
knowing
or
understanding
in
parallel
I
created.
A
cap
word
tried
to
organize
my
thoughts
and
findings,
how
packages
are
currently
baked
and
where
we
might
want
to
go
so
I
had
the
question.
So
what
what
do
we
want
to
do
with
that?
Do
we
want
to
like
close
out
my
cap
and
still
just
rely
basically
on
the
working
in
their
issue
can
with
or
whatever
what?
What
should
we
do
about?
C
C
Maybe
it's
I
will
help
as
much
as
I
can
to
update
the
cap
with
what
they,
what
they
are
thinking
and
maybe
or
and
help
them
to
get
an
exception
for
this
cap,
because
we
already,
after
after
the
deadline
for
caps,
so
that's
gonna
happen
in
the
next
days.
I'll
try
to
to
sync
up
with
say,
cluster
life
cycle
folks.
A
C
C
A
Awesome,
well,
that's
all
the
roles,
those
are
all
roles
for
the
release
team,
so
putting
my
notebook
away,
wear
down
my
agenda
pencil.
So
this
is
open
discussion
time.
So,
if
anyone
has
open
discussion
topics,
they
want
to
talk
about
things
that
they
want
to
bring
up
today.
Now,
it's
for
sure
the
time
do
it
I'm
going
to
meet
myself
and
write
notes
for
a
second
but
feel
free
to
bring
up
any
open
discussion
topics.
C
A
A
B
B
As
far
as
release
notes
go
not
really
again,
it's
pay
attention
if
there's
anything
that
is
outside
of
what
they
are
planning
comms
wise,
let
them
know
because
it
may
impact
what
they
do,
blog
wise.
What
I
listen
to
near
the
end
of
it
was
Erin
was
asking
the
comms
people,
specifically
the
CN
CF
blog
people.
Oh
sorry,
yeah!
B
This
is
the
comms
meeting
that
I'm
talking
about
erin
was
talking
to
the
comms
people
about
how
to
pick
the
blog
topics
and
kind
of
the
what's
the
schedule
for
it
like
when
do
I
need
to
know
what
the
topic
of
the
five
blogs
is.
How
do
we
pick
the
topic
of
the
five
blogs?
Does
it
have
to
be
five
blogs
that,
like
you
know
getting
into
the
minutiae
of
it,
and
it
was,
it
was
pretty
productive,
I
think.
A
F
B
We
don't
have
a
plan
right
now.
We
didn't
actually
get
to
talk
with
Doc's.
Specifically,
it
was
a
comms
driven
meeting
and
I
didn't
even
see.
Who
is
all
on
the
call,
because
again
I
was
on
my
phone,
so
I
don't
even
know
if
Doc's
was
represented
at
the
meeting
I
just
know
they
were
invited.
Lindsey,
do
you
by
chance
know
I,
don't.
H
Claire
Kaitlyn,
so
mostly
CNCs
and
Aaron
was
there
and
somebody
else
that
I
don't
remember
right
now,
but
yeah
it
was.
It
was
informative
because
Aaron
has
been
talking
about
making
the
release
notes
kind
of
more
suitable
for
a
user
to
read
them,
I
mean
if
we
just
have
a
dumping
ground
of
like
all
the
work
that
the
SIG's
have
done.
It's
useful
for
people
that
are
contributors
to
kubernetes,
to
kind
of
see
what
difference
things
are
doing,
but
it
might
not
be
so
useful
from
a
user
perspective.
H
So
I
think
that
it's
kind
of
just
useful
to
see
what
other
people
are
doing
to
get.
The
word
out
and
Crom
seem
to
have
a
pretty
good
handle
on
what
users
want
to
see
from
my
perspective.
So
it
gives
us
content
to
talk
about
in
our
future
release
notes,
meetings
about
how
we're
going
to
reframe
things.
A
Nice
yeah
I
mean
it
was,
it's
always
been
a
I
mean
it's
a
yeah.
It's
been
it's
nice
now
that
we're
so
committed
to
enhancements,
because
it
gives
us
another
programmatically,
accessible
source
to
pull
some
reliable
data
about
the
beliefs
and
I.
Think
that
perhaps
especially
if
we
continue
using
caps
to
document
everything
that
goes
into
the
release,
that
it
will
be
a
nice
place
to
pull
some
additional
human
kind
of
curated
text
about
various
things
that
are
going
through.
That's
awesome
thanks
guys.