►
From YouTube: Flatcar Release Planning | 2021-08-23
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
B
B
B
C
C
C
D
D
D
D
D
D
I
think
we
are,
we
can
start
the
meeting.
C
E
D
The
slides,
okay,
yes,
cool,
so
welcome
everyone
to
the
flat
car
release
team
meeting.
This
is
a
bi-weekly
call
where
we
will
be
planning
to.
This
is
where
you
can
talk
with
the
release
team,
for
any
shows
that
you
have
with
flat
car
or
any
new
features
you
want
to
get
into
shipped
into
flat.
Car
or
one
of
the
main
agenda
that
would
be
we'll
be
taking
in
this
release
meeting
would
be
the
release
priming
as
well.
D
So
let's
get
ahead
with
the
meeting,
so
the
agenda
would
be
in
the
beginning,
we'll
have
a
round
of
introductions
and
then
we'll
talk
about.
The
current
state
of
releases
then
followed
by
the
release
planning
and
then
you
there
will
be
open
flow,
so
if
they
would
it's
open
to
q
and
a
and
discussion.
D
So
let's
start
with
the
round
of
introduction,
so
hi,
I'm
cyan.
I
work
I
work
with
the
flat
car
release
team
and
have
been
primarily
looking
into
the
releases
and
yeah
so
happy
to
have
you
all
here.
Next
matthew.
C
E
Hi,
I'm
jeremy.
I
work
for
microsoft
on
flat
car
right
now.
I
recently
wrapped
up
the
c
group.
V2
upgrade
work
now
just
some
general
mantle
related
development,
william.
B
Hey
folks,
another
microsoft,
kinfolk
person
here
on
the
flat
card
team,
mostly
working
on
arm64
stuff
right
now,
aniruda
yourself.
F
G
Yeah,
hey
everyone
hi,
my
name
is
ryan.
I
work
as
an
srv
at
infracloud.
I
contribute
to
like
I'm
a
beginner
contributor
in
kubernetes
and
I'm
exploring
flat
car
events
and
going
through
issues
saying.
D
Good
we,
I
guess
we
have,
we
had
the
introduction
from
everyone.
Thank
you.
Thank
you
folks
for
the
introduction.
So,
okay,
I
guess,
wait
interesting,
okay,
yeah,
so
jumping
into
the
release
planning.
So
let's
go
ahead
into
the
current
setup,
current
state
of
the
current
release
before
going
ahead
and
talking
about
more
into
what
happened
in
the
current
release,
I
would
like
to
give
the
stage
to
talk
about
a
few
words
about
the
c
groups.
V2
changes
that
that
landed
so
jeremy.
E
Sure,
I
can
say
a
couple
words,
so
something
that
landed
in
the
2969
release
alpha
currently,
is
that
we
enabled
c
group
v2
by
default
for
the
whole
os.
E
E
Important
to
know
that
this
doesn't
break
existing
kubernetes
deployments
existing
nodes
during
an
update,
so
we
we
implemented
a
kind
of
a
freeze,
config
procedure,
migration
during
during
an
upgrade
right
now.
This
affects
only
only
fresh
nodes,
so
deployed
with
the
with
the
current
alpha
image
and
yeah.
We
encourage
folks
to
test
it,
there's
documentation
if
you're
affected
by
the
by
the
change.
You
will
get
a
warning
after
upgrading,
there's
a
mailing
list
post
coming
up
and
a
blog
post
coming
up
detailing
how
this
affects
users
yeah.
E
So
we
we
encourage
everyone
to
test
and
and
report
issues.
We
already
have
have
the
first
issues
popping
up
and
we
will
get
them
resolved
quickly.
D
Sorry
for
the
typo
that
have
on
the
slide,
I
really
want
to
test
the
changes
in
deployment
and
file
issues,
but
this
gestures
here
is
to
test
them
test
the
changes
early
and
find
the
issues,
and,
as
jeremy
mentioned,
we
had
our
first
issues
and
that
should
be
the
fix
should
be
out
there
in
the
next
releases
so
yeah
and
other
than
that
we
had
a
release.
D
Last
week,
it's
a
we
had
a
release
for
all
the
branches
like
lts
had
a
patch
level,
with
my
other
linux
upgrades
and
and
other
than
that,
like
even
the
beta
and
stable,
had
batteries
upgrade
with
minor
issue,
basically
like
updates
to
packages
and
few
issues.
But
then
a
major
alpha
went
out
the
door
which
has
a
lot
of
changes
in
there
so
including
the
second
v2
and
the
docker
change,
so
folks
go
ahead
and
test
those
now
quickly.
D
D
Can
you
see
my
screen
the
running
board?
Okay,.
C
D
Cool
so
this
cycle,
like
we
have
under
the
like,
who
had
a
couple
of
issues
package
upgrades
in
the
last
one
which
went
into
alpha,
and
this
time
also
has
been
working
on
issue,
but
other
than
that.
The
team
has
also
been
working
on
a
couple
of
packages
and
issues
that
has
to
be
like
the
fix
that
jeremy
just
talked
about.
D
So
this
release
we
have,
we
are
planning
to
have
it
relatively
small,
given
it's
like,
we
have
a
week
there
and
we
are
planning
to
start
the
trip
builds
by
friday
so
that
we
have
them
out
by
monday.
Does
it
sound
good?
D
I
see
not
so
yeah,
yes,
so,
okay,
so
jeremy.
I
wanted
to
know
that,
since
you
have
already
migrated
the
like,
you
have
the
c
group
suite
and
the
docker
changes
in
so
shall
we
mike
move
this
ticket
or
close
this
ticket.
E
I
I
would
definitely
move
it.
I
wasn't
sure
if
we
were
going
to
do
the
moving
together
during
one
of
these
release
meetings
or
whether
I
should
do
it.
So
that's
why
I
left
them
there,
but
yeah
these.
The
the
first
two
are
definitely
already
released
on
in
the
in
the
release
on
the
16th.
D
Okay,
we
can
definitely
move
them,
so
we
can
move
them
to
this
too,
so
yeah.
So
as
soon
as
you're
done
like
feel
free,
like
you
are
not
blocked
on
the
this
meeting,
you
can
feel
free
to
move
them
whenever
you're
done
with
the
issue
other
than
that
like
we
are
also
planning.
So
talking
about
the
plan
changes.
D
So
we
have
a
few
of
the
packages
which
we
are
planning
to
update
like
series
gillipsy
go
nettle,
polkadot
ip
tables,
linux
firmware
and
ws
messaging,
so
few
of
them
already
have
prs.
If
I
recall
correctly,
we'll
be
updating
those,
but
if
anyone
is
looking
to
contribute
like
the
first
package
is
a
relatively
simpler
one,
so
you
can,
if
you're
looking
to
contribute,
that's
a
simple
package
to
upgrade,
so
you
can
pick
that
up
other
than
that.
D
Like
iq
tables
has
been
in
there
for
some
time,
but
we
have
had
some
progress
there,
so
hopefully
we
will
be
updating
it
in
the
in
the
next
release
other
than
that,
like
the
dhcp
v6
issue
seems
to
be
also
fixed,
so
we
might
have
we'll
have
a
pr
for
that.
Also
in
the
next
one
matthew
I
wanted
to
know
like
we
have
this
locksmith
d
issue
in
here,
so.
C
Yeah,
it's
it's
on
hold
because
we
need
to
upgrade
to
etc
free
in
order
to
close
this
issue.
So
it's
quite
related
to
this
upgrade.
C
D
Okay,
just
on
this
lines
like
do
you
think
we
can
create
a
on
hold
column
as
well
like
if
we
are
not
actively
working
or
should
we
have
just
dracula
in
progress
if.
C
D
D
Okay,
so
that's
something
we
can
look
so
that
in
progress
can
be
relatively
smaller,
like
even
the
bin
utils
one
is
kind
of
an
on
hold
for
the
upstream
changes,
so
so
we
can
add
those
other
than
that
do
folks.
So
this
is
given.
We
don't
have
much
time,
but
we
I
see
that
this
should
be
sufficient
for
the
next
few
days
and
for
the
next
release
to
given
the
last
one
was
a
major
one.
So
do
you
have
any
other
issues
that
you
have
been
working
on?
D
That
should
be
on
this
board.
D
E
Yeah,
kai
kai
had
a
fix
or
has
a
fix
for
an
issue
related
to
the
butterfest
switch
for
the
oem
partition.
E
I
was
about
to
add
a
card
for
that,
but
if
you
could
it's
it's
related
to
to
parsing
the
the
label
field.
If
someone
mounts
the
oem
partition
during
ignition.
E
C
Yeah,
we
can
also
add
the
new
issue
about
the
container
d
configure
it's
on
the
in
the
flat
car
repository.
D
D
D
Yeah,
I
think,
like
even
like
dongsu
and
kai
is
also
like.
Probably
thomas
is
probably
not
dead.
This
weekend,
kai
is
also
half
yeah.
D
E
D
I
think
this
should
be
good
anything
else
that
we
need
to
add.
Do
you
think
that
should
be
added
here.
D
Another
thing
that
I
was
thinking
was:
should
we
have
a
section
for
like
few
issues
again
happen
in
our
plant,
but
it
have
been
like
long
like
issues
which
have
been
running
for
multiple
releases
like
so.
How
should
we
tackle
like
pool
kit
has
been
there
for
some
time,
and
william
has
been
working
will
be
working
on,
has
been
working
on
it.
So.
H
Yeah,
that's
a
good
call
actually
and
just
pushing
them
from
release
date.
Release
date
is
probably
just
too
much
manual
work.
I
mean
I
get
that
some
of
those
aren't
really
good
estimatable
in
that
there
are
a
number
of
unknowns
when
upgrading
parts.
So
maybe
we
want
to
have
a
backlog
column
where
we
put
those
just
to
signify
that
it's
being
worked
on,
but
we
don't
have
a
clear
end
date.
D
For
it,
I
think
in
my
I
something
I
was
thinking
was
like
we
can
have
a
column
we
put
it
that
put
in
in
there
and
during
the
release
call
we
can
give
a
short
update
if
we
have
like
if
we,
if
there's
some
update
there
so
that's
way.
The
community
is
also
updated
on
what's
happening
on
those.
D
D
Okay,
so
okay,
then
we
will
add,
then
two
columns
on
hold
and
long
term
so
that
that
that
makes
sense
so
that
in.
D
That
is
also
so
in
progress
essentially,
for
me
would
be
like
if
you
could
finish
up
by
the
next
release
or
next
to
release
max.
D
So
I
think
we
can
add
it
in
progress,
and
sometimes
you
cannot
estimate
so
maybe
in
progress.
We
understand
that
we
cannot
complete,
then
we
move
it
to
long
term
or
on
hold
based
on
how
it
goes
so
yeah
cool.
I
think
we
are
good
here.
I'll
just
add
those
new
columns
after
this
meeting
so
and
update
on
the
channel.
D
Stop
sure:
okay,
no,
this
one,
okay,
so
yeah
so
welcome
to
contribute
like
we
have
a
few
contributors
now
and
I
see
ryan
has
joined.
This
call
so
ryan
feel
free
to
jump,
join
our
irc
channel
and.
D
Cool,
so
if
you
have
any
questions
like
you
can
like
set
up
the
developer
environment
and
after
that,
if
you
have
questions,
feel.
G
F
I
A
Oh
hi,
I'm
dania,
I'm
working
at
yeah
microsoft
and
it's
my
first
time
joining.
This
call
quite
excited.
D
D
So
see
you
all
on
like
feel
free
to
test,
if
you
have
any
issues,
feel
free
to
reach
out
on
the
communication
channels
and
yeah
the
there
are
issues
out
there
on
the
flat
card
issue
tracker.
If
you
face
issues,
feel
free
to
open
new
issues
as
well
and
yeah.
Before
closing,
do
we
have
any
questions
or
there's
something
to
discuss
here?
D
I
think
we
are
good,
then
cool
thanks.
Everyone
for
joining
have
a
great
rest
of
the
day
and
bye.