►
From YouTube: Kubernetes Release Team Meeting (APAC) (1.25)
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
I
was,
I
would
start,
the
recording,
yeah
hello.
Everyone
welcome
to
the
1.25
release
team
meeting
today
is
july
friday
july.
The
22nd.
A
A
So
I
just
opened.
The
meeting
notes
looks
like
there's
not
too
much
going
on.
Is
there
any
anything
for
the
open
discussions?
I
can
see.
There's
one
comment
that
we
have
soon
already
mid
retrospective.
So
if
you
have
any
ideas
how
to
improve
the
release,
team
progress
process
or
anything
regarding
the
release
team,
this
would
be
a
good
good
time
to
just
add
your
thoughts,
so
we
can
discuss
it
and
improve
this
team
and
everything
anything
else.
A
A
Okay,
so
maybe
she
will
join
a
bit
later
or
he
I
don't
know.
Actually
I
think
she
so,
let's
jump
ahead
looks
like
nobody
from
tier
signal
joined,
which
is
fine,
wait.
How
can
I
I
think,
let
me
quickly
go
to
the
last
one.
A
Last
time
also
nobody
joined,
we
had
a
couple.
There
were
a
couple
of
problems
with
grink
gringo,
which
is
a
library
for
running
tests,
and
I
think
most
of
the
problems
have
been
resolved,
but
there
are
still
a
few
flags
and
failures.
A
C
Nothing
has
changed
compared
to
last
two
meetings.
We
have
still
the
blocking
issue
for
the
release.
Next
release,
which
is
the
combined
his
publishing
boat,
is
broken
so
but
yeah
still,
we
are
looking
at
the
issue
we
are
following
this.
There
are
new
pr's
and
issues.
Yeah
came
in
through
our
pipelines,
so
I
updated
our
github
project
board
yeah,
because
hipaa
she's
on
vacation,
so
I
pinged
the
team
to
pick
up
the
new
issues
and
prs
yeah.
Everything
is
tracked
from
our
side
yeah.
That's
it.
A
A
Looks
good
going
to
the
docks
seems
like
nobody
from
dogs
joined.
Looking
at
the
last
updates
very
quickly,
dogs
was
green.
A
A
B
Yeah,
so
my
update
is
the
next
week
is
their
first
release.
Retro
for
125.,
also
mid-cycle
shadow
surveys
will
go
out
soon
as
well.
I'll
need
to
get
them
reviewed.
One
thing
I
wanted
to
make
a
note
and
that
it
looks
like
we're
going
to
use,
go
119.
put
this
pr
in
the
chat.
I
just
saw
this
and
kk
and
there's
note
there.
It
says
for
125:
kubernetes
will
be
using
golem
119.
B
This
pr
will
update
to
119
rc2,
as
ga
is
not
yet
available.
It
looks
like
119
will
go.
Ga
in
the
first
week
of
august
looks
like
so
that's
the
pr2
to
use
rc2
and
in
test.
Infra
looks
like
the
there's
already
been
some
prs
to
use
rc2
already
so
yeah.
I
just
want
to
make
it
make
that
a
note
I
know
dims
was
on
the
wednesday
call
and
wanted
to
bring
that
topic
up
so
just
folks
yeah.
B
A
B
A
A
D
Google
meet
room,
I
got
an
invite
for
the
google
mid
link,
so
I
was
waiting
there.
It
was
the
last
minute
decision
of
of
who
is
going
to
go
for
these
and
for
updating
the
announcements.
So
this
was
my
first
time
here,
so
I
kind
of
waited
in
the
google
metro,
but.
D
I
think
we
have
gone
through
the
update
of
the
kp's
announcements
right.
There's
no
need
for
me
to
update,
give
an
update,
or
are
we
good.
D
We
are,
we
are
just
going
to
complete
the
reach
out.
First,
our
first
reach
out
for
the
code
freeze
in
the
upcoming
week.
Also
we
got
the
admins
permission
for
the
btec
group
github
project
yesterday,
because
priyanka
took
announcements
sync
up
yesterday
and
she
told
us
about
what
we
will
be
working
on.
We
will
be
moving
off
of
the
google
excel
sheet,
so
yeah
we
we
will
be
trying
some
of
the.
D
A
But
the
transition
is
still
work
in
progress
right
because
I
saw
a
couple
of
like,
like
updates
to
the
pull
request.
D
Yeah,
so
we
will
be
trying
out.
Firstly,
so
let's
see
how
it
goes
we
are,
I
think
we
are
trying
to
con
conduct
the
1.26
release
on
the
github
beta
project
board.
Yesterday
she
said
priyanka
said
that
we
will
be
moving
towards
github
project
board
in
the
next
release
cycle.
B
This
it's
actually
going
to
be
done
in
peril.
So
we
talked
about
this
in
the
where
there
was
enhancement.
Sub
project
meeting
looks
like
126
once
the
github
beta
projects
beta
will
be
used
and
the
spreadsheet
just
to
make
sure
that
there's
there's
no
gaps
and
there's
there's
feature
parity
between
the
two,
so
one
we
will
yeah.
It
is
true
that
we
will
be
using
the
project's
beta
for
126,
but
it'll
also
be
done
in
peril.
B
So
I
believe
it's
and
I
don't
know
how
long,
how
many
releases
that
will
be
once
it's
complete.
It
might
need
another
release
to
to
figure
out
to
add
more
feature.
Parity.
C
D
B
Versus
the
spreadsheet,
because
there
are
some
scripts
in
the
spreadsheet
as
well
and
still
figuring
out
also
how
to
how
sig
leads
could
opt-in
with
using
github's
project
beta
as
well?
So
that's
still
kind
of
in
the
works.
B
Yep
yeah
there's
no
wrestling
guide
to
like
create
columns.
If
you
create
that
you
can
create
the
project
complete
with
an
api,
we
can't
do
a
lot
of
customizations
yet.
A
So
but
I
think
that's
it
or
somebody
else
joined
in
the
meantime.
I
don't
know
actually
how
how
you
received
an
invite
for
google
me
yeah.
B
I
just
changed
it
by
the
way
I
just
removed
it.
So
there's
not
it's
not
confusing.
Whenever
you
create
a
a
calendar,
invite
it
defaults
to
create
a
google
meets
yeah
yeah
link
as
well,
so
you
have
to
manually,
remove
it.
So
I've
removed
it
for
this
in
the
following
meetings
as
well,
so
that
that
should
be
resolved.