►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191021
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
A
B
A
we
are
green
with
enhancements,
freeze-over
and
all
the
exceptions
in
we
are
currently
tracking
45,
with
12
alpha
13,
beta
and
20,
going
to
stable.
Now,
looking
looking
pretty
good
for
this
really
so
far,
and
all
three
of
the
exceptions
were,
you
know
pretty
close
to
being
done
and
seemed
pretty.
You
know
it
didn't
seem
like
that
much
of
a
risk,
so
things
should
be
good.
Yay.
A
C
Right
well
green
this
week
as
well
last
week,
yeah
last
week
was
pretty
like
I.
Wasn't
that
optimistic
at
this
week
about
this
week,
it's
like
everything's,
looking
very
good.
There
was
like
a
lot
of
work
from
various
six
on
various
issues
that
helped
us
like
move
a
lot
of
jobs
to
like
greenish
color.
So
in
terms
of
massive
looking,
we
still
have
like
free,
flaky,
free
flaky
jobs.
C
One
of
the
one
of
the
things
that
I
want
to
call
out
is
like
a
scheduling,
scheduling
test
that
was
actually
which,
which
I'm,
like
really
really
glad,
would
be
cooperation
with
that
sake,
because
they
they
seem
to
be
really
on
top
of
that
and
they
already
submitted
an
issue
of
sorry
submitted
a
PR.
They
already
like
reduce
the
flakiness,
and
they
are
still
like
working
on
like
making
that
even
even
greener,
as
it
is,
so
that's
pretty
cool
in
terms
of
mastery
forming.
C
So
what
I
really
want
to
co
about
is
that
we
finally
have
the
conformance
test
running
for
OpenStack
again.
That
is
so
like
a
that
is.
That
is
a
job.
That
is
a
work
that
was
done
by
one
of
my
shadows,
nikolaos.
That
was
like
really
really
good
work,
so
kudos
to
that.
So
he
reached
out.
He
created
an
issue
and
like
reached
out
to
that
sick
and
really
made
that
made
it
happen,
so
that
job
is
running
again,
which
is
pretty
exciting.
C
Unlike
the
last
positive
note,
there's
like
couple
of
jobs
read
right
now.
Add
that
happened,
I
think
Friday.
There
was
like
a
merge
from
from
Signet
work
that
like
broke
couple
of
jobs,
but
I
checked
I
think
hour
ago,
and
they
already
submitted
a
PR
and
they
are
also
trouble.
That's
so
pretty
pretty
positive
week.
A
C
Yeah
so
I
I,
don't
know
a
few
salts
like
I
reached
out
to
do
two
to
one
of
the
guys
from
seasick
scalability.
So
he
identified
some
jobs
that
we
should
be
monitoring
for
this
release
and
yeah.
He
he
will
be
identifying
the
enhancements
that
cause
like
improve.
I
got
early
improves
scalability,
so
we
should
probably
keep
an
eye
on
those
as
well.
But
you
know,
I
think
the
the
corporation
is
is,
is
looking
good,
so
I'm
positive
on
that
front
as
well.
Yeah.
A
E
E
A
C
F
Perry
so
bug
triage,
just
looking
green,
we
have
ticket
issues
and
PRS
have
been
quite
stable
for
priority
protocol
elegant
issues.
We
have
only
a
change.
A
single
issue
in
added
importance
to
issues
have
not
changed
much
PRS.
Also,
we
have
part
priority.
Critical
Agent
P
are
increasing
by
one
priority
important
in
PRS,
also
increase
in
by
one
on
our
money.
Ho
we've
had
high
to
slow.
He
twitches
to
be
expected
at
this
time
of
the
release
cycle
for
old
and
still
issues.
F
A
Yeah,
so
my
only
concern
is
that
we're
having
we're
having
on
a
lot
of
open
issues
so-
and
that
was
the
case
last
release
as
well.
One
thing
that
we
can
we
can
maybe
get
get
working
on
is
to
just
gently
poke
the
issues
that
haven't
seen
a
lot
of
action
and
a
lot
of
traction
in
the
last
couple
weeks
or
so,
and
just
kind
of
just
make
a
little
bit
of
noise
on
them
so
that
maybe
they
may
appear
in
people's
notifications.
A
I
know
that's
a
lot
of
individual
like
work,
so
please
lean
on
your
shadows,
I
guess
or
in
your
case,
but
but
yeah.
If
you
can
get
a
jump,
start
on
that
and
will
make
your
life
a
little
bit
easier
in
the
next
in
the
coming
weeks
and
it
will
make
Mical
make
everyone
in
charge
of
the
release
a
little
bit
more
like
relaxed
about
it
too.
That's
that's
my
only
thing
again
I
this.
This
is
this
is
not
unusual
at
all.
A
A
Doc's,
we
do
not
have
a
Doc's
update
today.
Where
do
we.
G
A
A
G
A
A
The
final
final
dog's
deadline
right
up
on
throw
on
top
poster.
Let's
see
dogs,
release,
notes,
Haven.
H
Hope
y'all
had
a
good
weekend
and
no
big
update
today
we're
still
looking
green.
We
had
a
couple.
We
had
one
PR
get
proof
thanks
Steven
for
the
the
draft
and
we're
also
had
a
PR
put
in
with
the
release
notes
site
to
add
in
the
filters
for
the
alpha
releases,
so
we're
just
waiting
for
an
approval
on
that.
So
if
someone
has
power
to
do
that,
we
have
the
looks,
looks
good
to
me
from
Sasha.
H
D
H
D
I
D
H
D
A
D
D
So
I
am
actually
so
Carlos
has
a
note
in
the
notes.
I
knew
it
in
the
notes
about
do
asking
if
he
can
do
the
cut.
What
I
would
like
to
see
is
I'm
going
to
see
if
I
can
identify
a
release,
manager
associate
that
is
new
to
the
game.
To
do
one
of
the
alphas
I
want
to
make
sure
I
want
to
try
to
get
them
in
early
for
the
alphas,
as
opposed
to
doing
like
a
scary
like
a
beta
or
are
they
are
sees
just
so
they
can.
D
You
know
what
their
whistle
on
some
walking
through
some
of
the
tooling.
So
if
I
cannot
identify
someone
by
the
end
of
today,
then
Carlos
will
do
it
in
the
morning.
In
his
time,
I
will
be
cutting
the
beta
0
when
that
comes
up,
because
that's
a
lot
of
branch,
nonsense
and
I've
been
I've
been
playing
around
at
stuff.
A
Sounds
like
we're
on
track
with
that
Thank
You
Steven
next
is
me:
I
have
mostly
mostly
I,
just
jumped
on
the
notes
that
I
will
give
on
Thursday
at
the
meeting
next
week.
We
are
cutting
the
release
branch
and
the
117
jobs
will
be
set
up
so
get
ready
for
that
everybody
then
we
have
we've
been.
This
has
also
been
covered.
We
have
added
back
the
test,
the
OpenStack
tests
to
make
sure
that
we
have
at
least
some
test
coverage
in
some
areas.
D
There's
active
discussion,
I,
don't
know
if
the
I
don't
know
if
it's
been
resolved,
but
I
I
think
people
have
been
chatting
back
and
forth
about
whether
the
open
stack
test
is
actually
a
test
on
real
infrastructure
or
a
synthetic
test,
so
they're
trying
to
determine
that,
but
just
to
be
aware
that
we're
trying
to
make
sure
that,
in
addition
to
kind
that
there
are
also
tests,
unreal
infrastructure
happening.
So
thank
you
again
to
everyone
who
has
been
involved
in
that
process.
D
Gorge
for
for
running
with
making
sure
the
the
conformance
stuff
has
gotten
in
as
well
as
everyone
on
CI
signal
to
mate,
make
sure
that
stuff
got
cleaned
up.
I
know
it's
still
active
and
I
know
it's
a
bunch
of
a
few,
a
few
of
the
tasks
or
undefined
work,
but
I
really
appreciate
y'all.
Getting
on
top
of
that.
A
A
A
A
A
A
D
Whoever
is
responsible
for
the
scalability
meeting
anything,
that's
probably
a
Elena.
Please
make
sure
that
the
cig,
scalability
chairs
the
cig,
release
chairs
the
release,
team,
lead
and
shadows
are
invited,
as
well
as
a
CI
signal
team.
Even
if
those
people
cannot
show
up,
please
make
sure
that
they're
all
included
on
that
invite.
C
D
A
A
G
Have
a
question
so
like
venom,
you
dog
shadow
self,
join
the
release
team
of
few
people
who
are
asking
me
like
questions
like
what
are
this
alpha
and
Ruby
releases
and
how
exactly
they
work
so
do
we?
Are
we
planning
to
have
any
interpreting
session
for
new
shadows,
joining
the
release
team
or
any
pointers
for
such
resources?.
A
A
D
So
one
if
anyone
on
the
call
has
never
seen
this
document,
please
take
a
look
at
it.
Really
Steve
onboarding
I'm,
pretty
sure
that
most
of
you
have
there
are
lots
of
valuable
resources
and
the
cig
release
repo
in
general,
including
role
handbooks,
which
you
can
the
role
handbooks
for
release
engineering,
as
well
as
the
release
team.
Those
were
there
and
yeah.
D
So
so
alpha
beta
RC
releases,
the
you
know
the
primary
concern
there
is
to
be
able
to
vet
one,
the
you
know
the
status
of
kubernetes
at
any
one
point
in
time,
as
well
as
the
as
well
as
being
able
to
exercise
the
tooling
that
we
use
over
time
right
as
tooling
changes.
Things
may
not
work.
You
know.
Tests
may
fail
all
that
good
stuff.
So
we
want
to
make
sure
that
we're
we're
turning
we're
cranking
the
wheel
ever
so
often
to
make
sure
that
things
are
up
now.
D
The
people
who
consume
these
things
are
it's
not
as
large
of
a
group
as
I
would
like
it
to
be,
and
it's
primarily
because
of
discoverability.
We
don't
have
so
people
who
are
aware
of
where
the
artifacts
land
for
aqua
beta
Knightley's
can
pick
those
artifacts
up,
whether
it
be
a
tarball
or
a
Deb
and
consume
them.
D
Not
that
that
group
of
people
is
a
very
small
group,
unfortunately,
so
we're
working
towards
a
system
where,
where
where
things
are
more
easily
consumable,
but
we're
also
untangling
a
lot
of
the
technical
debt
around
the
release
engineering
process.
So
you
know,
if
you
are
someone
who
wants
to
consume
Knightley's
or
our
alpha
beta
RC
releases
of
kubernetes
from
an
after
yum
repo.
You
can't
do
that
today
right.
D
So
so
you
know,
and-
and
that's
because
the
of
the
way
our
repos
are
designed
are
apt
and
repos
are
designed,
we're
working
on
a
new
design
for
those
things
where
you
will
be
able
to
consume,
nightly
and
nightly,
and
testing
versions
of
kubernetes,
but
we're
a
little
ways
away
from
that.
There's
still
lots
of
there
there's
a
lot
of
stuff
in
the
infrastructure.
So
if
you
were
on
the
the
cig,
release,
call
I
was
kind
of
walking
through
the
kubernetes
build
process.
D
Our
briefly
walking
through
the
kubernetes
build
process
and
some
of
the
stuff
I'm
trying
to
change
in
it.
It's
yeah
yeah
there
there's
still
some
unknown
unknowns
and
the
the
Deb's
and
rpms
are
kind
of
like
the
last
mile
of
that.
So
there
are
a
few
things
process
wise
that
we
need
to
lay
down
before
we
can.
We
can
move
there,
okay,
go!
Thank
you,
yeah,
no
problem.
A
Thanks
for
asking
always
good
to
ask
questions
any
other
questions
before
we
scan
the
board.
C
B
A
A
No
worries,
okay,
release
retrospective
action
items.
I
do
believe
that
everybody
on
this
team
should
take
a
look
and
see
which
ones
are
in
their
wheelhouse
and
which
ones
maybe
have
been
worked
on
already.
I
do
know
that
the
six
scalability
meetup
is
on
there
and
I
have
not
updated
this
issue.
So
that's
what
to
do
for
everyone,
I,
don't
necessarily
I.
If
we
have
time
at
the
end
of
the
meeting,
we
can
open
it
again.
I
know:
there's
22
checkpoints,
yes,.
A
A
Otherwise,
I'll
have
to
pick
it
up
and
do
it
cool.
This
is
that
big
meta
issue.
E
D
D
D
So,
basically,
it's
it's
people
who
have
not
been
on
the
release
team
for
a
while,
but
want
to
come
back
and
they
have
done
leading
before,
like
what's
the
process
for
reintegrating
them
into
the
release
team
right,
so
they
should
have
a
they
should
have
a
halo
or
you
know
some
sort
of
respected
status
right
in
consideration
if
we're
looking
for
people
outside
of
the
release
name.
So
that's
kind
of
what
the
issue
is
to
codify
that
process.
A
D
No
I
know
I
I
personally
haven't
touched
this
in
recent
days.
Essentially,
what
we
need
to
do
is
we
keep
CI
up
for
for
a
little
bit
for
the
last
supported
release.
We
need
to
determine
like
what
are
the
reasons
that
we
would
continue
to
release.
Are
they
critical
Seavey's
like
what's
like
what
are
the
things
that
would
cause
us
to
sell
release
on
a
quote-unquote,
non-supported
release
branch,
okay,.
E
A
We
are
I
just
CPR
boilerplate
and
labels
to
improve
release
notes.
Is
there
any?
There
was
a
lot
of
work
on
that
in
early
September.
What's
happening,
I.
D
I
think
the
majority
of
the
stuff
that
we
wanted
to
merge
got
merged
there.
The
remaining
pieces
are
there's
a
discussion
on
primary
sake
that
you're
hovering
over
as
well
as
a
deprecation
note,
the
deprecation
note
so
again,
I'm
I'm
I'm,
heavily
in
favor
of,
like
you,
said
not
having
so
much
information
in
the
and
the
PR
template
that
it
makes
heart
it
harder
for
a
new
contributor
to
get
involved
or
understand
the
pieces
that
they
need
to
lay
down
so
I'm.
D
A
D
A
E
A
Very
cool:
can
you
kind
of
leave
a
comment
and
update,
so
we
can.
E
A
E
I
D
A
Again
next
question
are
all
those
three
issues
on
the
release
tracking
board.
A
A
A
And
I'll
talk
to
Jeff
about
this
he's
been
out
for
the
last
few
weeks,
so
let's
just
follow
up
with
him
a
sink
or
next
week
cool
to
do.
Try
splitting
splitting
release
schedule
out
of
release
neat
playbook,
I've
sort
of
been
poking
around
at
that
in
my
head.
There's
not
gonna
need
visible
work
on
it
and
we
have
this
issue.
We
already
talked
about
it.
That's
in
the
to
do.
A
D
A
D
I
would
say,
let
me
let
me
let
me
do
this.
I
obey
ceccolini,
see
on
the
116a
I
swear,
there's
a
connected
issue.
I
want
to
connect
all
the
issues,
so
it's
easier
for
people
to
see.
This
is
gonna
kind
of
heart
be
harder
to
do
for
people
who
don't
have
edit
access
to
edit
the
description
for
this.
So
let
me
take
this
on.
I
A
And
also
ping
me,
please
DM
me
and
keep
me
in
the
loop
and
just
kind
of
like
if
you
want
to
discuss
or
if
you
want
to
just
kind
of
hang
out
and
do
this
together
sometime
this
week,
yeah.
B
A
D
A
A
Very
cool
thanks
so
much
everybody
and
I
will
see
you
next
week
same
time
same
place.