►
From YouTube: SIG Release's Personal Meeting Room 20200724
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
All
right
welcome
everyone
happy
friday,
we've
made
it
yet
again
in
our
week
this
week
was
especially
busy
with
119,
knocking
out
prs
and
critical
issues
and
just
a
massive
amount
of
involvement
from
everyone
in
the
community.
So
thank
you
very
much
for
your
help.
As
always,
you
are
all
fantastic.
A
B
Hello,
everyone,
I
hope
you
all
are
having
an
amazing
friday
or
starting
to
have
a
very
good
friday,
so
enhancements
is
currently
green.
We
are
tracking
34
enhancements
nine
in
alpha
15
in
beta
and
10
graduating
to
stable
the
la
since
last
update
the
only
one
pr
that
was
flaking
out,
also
got
merged,
and
so
yeah
announcements
will
be
enhancements.
Update
will
be
boring
from
now,
so
it
will
be
all
weekly
kind
of.
D
Hey
folks,
happy
friday,
it's
been
a
crazy
week,
but
we're
looking
a
lot
better
than
we
have
in
a
while.
We
have
zero
failing
tests
on
master
blocking.
If
you
see
kind,
ipv6
master
parallel,
saying
it's
failing,
that's
just
because
it
hasn't
run
enough
times
to
correct
itself.
We
had
a
new
test
merged
there.
That
was
not
passing
so
that
got
reverted
master.
Alpha
features
has
been
green
since
the
merge
that
fixed
that
testing
issue,
which
was
mainly
just
around
how
we
were
watching
for
pod
deletion.
D
D
The
main
one
that
we're
investigating
right
now
is
verify
master
just
because
this
has
to
run
on
every
pr
and
right
now,
if
you've
been
trying
to
do
anything
lately,
you've
probably
had
to
do
retest
quite
a
bit
on
that.
So
there
are
a
few
well
there's
actually
quite
a
few
things
that
happen
on
verify
master
that
are
owned
by
different
sig.
So
we're
going
to
try
and
split
that
out
into
more
granular
issues,
so
we
can
get
that
address
faster
and
also
from
a
ci
signal
perspective.
D
Maybe
address
some
of
those
things
ourselves,
but
other
than
that.
Looking
pretty
good,
some
updates
on
master
informing,
so
we've
talked
a
few
times
about
the
openstack
conformance
job
that
runs
in
a
completely
separate
ci.
So
it's
pretty
hard
for
us
to
get
any
insight
on
how
to
fix
those
things
and
some
of
the
folks
actually
work
on
the
openstack
stuff.
Don't
actually
have
insight
to
it
either.
D
D
There
is
a
fix
in
place,
but
we're
waiting
for
someone
to
get
back
from
pto
to
approve
the
review,
because
it
is
kind
of
like
a
significant
change,
because
they're
pulling
the
xcd
image
on
build,
so
that'll
probably
get
moved
to
milestone
1.20
because
we're
pretty
confident
in
it,
but
it
does
kind
of
like
reduce
our
signal
right,
because
that
test
is
not
even
running
quite
a
few
tests
there.
So
a
little
bit
of
concern
windows,
jobs,
we've
had
a
lot
more
action
on
that.
D
It
seems
like
some
folks
from
sig
windows
have
gotten
more
involved
there,
and
one
of
the
things
we
notice
is
the
some
of
the
tests
that
were
removed,
that
we
didn't
want
to
run
anymore
and
have
been
failing
that
wasn't
being
reflected
in
the
job.
So
we
changed
the
job
configuration
that
didn't
work.
Then
we
realized
that
the
windows
builds
are
basically
happening
later.
So,
if
we're
using
the
latest
from
master,
it's
not
actually
the
latest
commit
from
master
the
build,
that's
being
used.
So
that's
why
those
are
still
being
reflected
there.
D
So
in
a
few
weeks
that
should
pop
up,
but
we
want
to
address
the
underlying
issue
as
well
and
then
1.19
is
pretty
much
the
same
same
flaking
and
failing
issues
there,
as
as
you
would
imagine,
while
we're
still
in
in
our
fast
forward
phase
here.
So
lots
of
improvement
this
week
and
lots
of
burn
down
and
some
issues
have
been
open
for
a
while,
so
exciting
stuff
to
see.
A
Thank
you
so
much
dan
yeah.
It's
I
took
a
look
at
the
we'll
get
to
it,
but
I'm
terrible
with
spoilers.
I
love
throwing
them
out
as
soon
as
I
can,
with
the
issues
the
critical
issues
and
the
prs.
Those
have
been
reduced
significantly
I'll
hold
on
the
number
until
you
know
tonight,
at
11.
I'll
reveal
it
at
the
end
so
that
you
stick
around,
but
it's
just
nothing
short
of
incredible
incredible
burn
down.
So
thank
you
very
much
in
that
front.
A
Dan,
wonderful,
let's
move
on
to
thank
you,
dan.
Let's
move
on
to
bug
tree
ash's
lab.
E
Hey
nothing
much
on
our
side.
We
are
still
red,
even
though
we
are
12
inches
down
this
since
wednesday.
E
We
started
to
play
this
guess:
a
sig
game
guesses.
He
gives
a
trademark
of
gianluca,
so
we
are
going
through
pr's
and
issues
that
have
need
c
label,
and
essentially
guess
you
seek
that's
pretty
much.
It.
A
Awesome,
thank
you
so
much
vlad.
If
you,
if
you
need
any
help
or
phone
a
friend,
I
definitely
recommend
reaching
out
to
lori
apple
she's
been
really
helpful.
This
week
too,
in
terms
of
running
and
running
running
in
front
of
that.
A
Awesome,
thank
you
very
much
bye
any
questions
for
bug
triage
or
for
vlad.
I
don't
know
if
any
of
us
know
the
rules
to
guess
a
sig,
but
we
can
we
can
try.
That's
a
question.
A
C
Hey
everyone
happy
friday,
we
are
green,
there
has
been
no
changes
from
last
update.
Our
branch
is
healthy
and
we're
good
from
dark
side.
A
Wonderful
release
knits
with
adolfo.
F
Hi
everyone
so
we're
green.
In
terms
of
the
note
generation,
we've
started
drafting
the
google
doc
to
what's
going
to
become
the
the
final
document,
and
so
I
I
just
had
a
question
regarding
what
gets
included
in
the
in
the
final.
F
In
the
final
themes,
we've
been
busy
contacting
the
sixth
this
week
and
last
week
we
only
have
four
left
to
go,
and
but
a
couple
of
questions
have
come
up
mostly
regarding
what
six
may
or
may
not
suggest
to
be
included
in
the
notes
and,
for
example-
and
I
it's
a
good
thing
that
I
see
someone
here
from
seeing
architecture,
because
one
of
the
questions
came
out
there.
F
This
came
from
tim
bannister
and
he
was
asking
to
include
in
the
in
the
notes
and
a
mention
of
required
transition,
which
is
a
cap
which
is
mostly
from
what
I
can
gather
from
it.
It's
like
a
like
a
policy
change
to
force,
features
to
come
out
of
beta
sooner
so
that
they
don't
languish
in
beta
forever,
and
while
this
is
not
really
a
feature
of
the
code
or
artifacts
or
whatever,
it
certainly
portrays
the
end
users
and
has
come
up
during
the
cycle.
F
So
I
don't
know
if
we're
supposed
to
take
those
or
hand
them
over
to
dogs
or
even
to
comes
to
be
including
the
final
blog
post.
I
don't
know
if
any
of
you
have
any
guidance
on
that.
So
we
and
I
got
another
similar
question
from
from
tim
alker
because
they
for
they
they
have
cube
adm.
It's
the
only
entry
project
that
they
ship
with
kk
and
on
the
last
part
of
the
cycle,
and
they
were
there
was
there
was
chatter.
F
If
we
should
include
enhancements
to
the
other
projects
that
they
should.
I
don't
know
if
any
of
you
have
any
anything
to
say
about
those
those
things.
A
That's
a
good
question.
I
don't
I
don't
know
off
the
top
of
my
head
to
be
honest
with
you.
I
think
we
could.
We
could
always
interact
with
sig
docs
and
and
see
if
there's
if
they
might
have
any
idea
on
that
front.
Otherwise,
if
anyone
has
any
ideas,
please
yeah.
F
A
F
With
saudi,
we
would
say
yesterday
and
just
to
to
let
her
know
our
efforts
and
and
we're
going
to
be,
recording
a
full
review
of
the
the
final
document.
Once
once,
we
get
all
the
six
content,
cool
cool.
A
Awesome,
thank
you
delfo
yeah.
If
you
need
any
help
on
that
front
I'll
ping
zig
dax
this
morning,
and
then
we
can
we'll
work
with
savitza
and
team
and
see
how
we
can
knock
that
out
all
right
cool.
Thank
you.
A
Any
questions
for
release,
notes
or
dolpho
can't
ask
the
bike
question.
I
already
asked
that
one.
Thank
you.
Dolpho.
Let's
move
on
to
comms
with
max.
G
Hey
so
far,
no
real
update
from
the
last
time
we're
waiting
for
some
input
from
cncf
about
the
yeah
events
in
the
ecosystem
and
what
is
all
planned
around
the
release
date,
better
say
after
the
release
date.
A
Wonderful
moving
on
to
release
branch
management-
I
don't
see
carlos
on
the
line.
I
do
know
that
if
dan,
if
you
can
correct
me,
if
I'm
wrong,
that'd
be
fantastic,
I
know
that
stephen
has
been
hard
at
work
working
on
the
go,
1.15
updates.
A
A
D
Yeah,
I
think
there
might
be
an
accelerated
patch
for
1.16
coming,
but
besides
that,
I
don't
think
there's
too
much
else
to
report.
A
Awesome
keep
production
boring.
I
like
it.
I
don't
see
tim
on
the
line.
I've
talked
to
tim
this
week.
I
know
he's
also
been
busy
with
quite
a
bit,
but
he's
been
the
message
simplified
is
keep
on
keeping
on.
So
I
really
appreciate
his
support.
He's
been
helping
people
out
on
one
offs,
so
thank
you
so
much
for
that
tim
release.
Lead
updates.
The
milestones
I
have
for
you
haven't
changed,
which
is
you
know
yet
another
good
thing.
A
August
3rd
monday,
our
burn
down
meetings
will
start
daily
august
6th.
We
have
both
the
cherry
pick
deadline
end
of
day,
pacific
and
test
freeze,
n,
a
pacific
I'm
going
to
regarding
code
saw.
I
believe
that
we
are
getting
very
close.
If
not
there
already.
A
I
definitely
want
to
ping
a
few
more
sigs
and
you
know
just
make
that
kind
of
a
team
effort
across
kubernetes
make
sure
that
we're
in
a
good
state
before
opening
up
the
gates
again
and
then
I'm
going
to
share
my
screen
to
share
with
you
the
oh
look
at
that.
I
just
had
to
happen.
I
happen
to
have
that
open,
we'll
refresh
this,
like
any
good
project
manager,
does
before
looking
at
a
board,
so
we
can
see
that
we're
down
to
just
four
critical,
urgent
priority
tickets.
A
Each
of
these
have
assignees,
and
I
took
a
look
at
the
conversation
going
on.
Each
of
these
everything
does
look
fantastic
and
then
same
here
we
have
assignees
for
all
of
these,
which
are
these.
There
is
motion
going
on
with
each
of
these
tickets
happy
to
see
things
get
closed
out
or
moved
to
120.
You
know
kind
of
following
some
of
the
items
that
we
had
deemed.
You
know
good
path
forward
with
the
community.
A
A
To
awesome,
silence
is
golden,
sometimes
sig
scalability.
We
don't
have
an
update
there,
but
you
know
looking
at
test
grid.
It
looks
like
everything
is
all
right.
Moving
into
open
discussion.
We
did
add
quite
a
few
things
this
week
from
the
retro.
Just
in
terms
of
you
know,
it's
always
dns.
It's
always
communication.