►
From YouTube: Flatcar Container Linux release planning 2021-09-28
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).
C
A
A
But
on
the
pro
side,
there's
only
two
links
that
you
need
to
remember
for
the
future,
because
this
is
our
recurring
meeting
and
we
have
one
link
for
the
planning
and
one
for
the
community
meeting
each
and
that's
it
and,
having
said
that
I'll
hand
over
to
scion
for
the
release
planning.
E
No,
this
is
still
the
old
hardware,
but
it's
showing
me
that
host
has
disabled.
The
screen
share
like
sharing
off
screen.
E
B
E
Okay,
I
I
s,
so
it
shows
me
that
host
disabled
participant
screen
sharing.
So
maybe
you
need
to
turn
I'll.
E
So
my
screen
should
be
visible.
I
guess
welcome
everyone
to
the
release
team
meeting.
This
is
the
september
month
by
weekly,
call
monthly
call,
I
should
say
so
we
are
having.
So
before
we
go
ahead.
We
usually
go
through
a
round
of
introductions,
and
then
we
discuss
this
current
state
of
releases
and
the
release
planning
and
then
followed
by
q,
a
and
discussion
so
quickly,
starting
off
with
the
oops
quickly,
starting
off
with
the
introduction
so
hi,
I'm
cyan.
E
I
primarily
look
after
the
releases
and
work
around
the
packaging
that
happens
on
around
in
flat
car.
Okay,
so
I
hand
over
the
mic
to
dongsu.
F
Hi,
my
name
is
don,
so
I
have
been
working
on
flag
cars
for
several
years
and
I
mainly
take
care
of
security
updates
recently
and
matthew.
B
D
C
Hi,
I
am
here
at
the
open
source
contributor.
I
am
I'm
currently
working
on
the
integrating
flat
fleet,
lock
client
to
the
locksmith,
with
matthew
yeah.
That's
me
and
hello.
A
Hi,
I'm
hilo,
I'm
the
manager
of
the
team
that
helps
maintaining
flat
car,
although
we
absolutely
welcome
open
source
contributors
like
aniruddha.
E
Do
we
have
anyone
else?
I
think
that's
it.
E
Okay,
so
let's
move
ahead:
okay,
wait!
One!
Okay,
so
quickly
jump
to
the
state
of
the
current
release,
so
we
released
yesterday
the
alpha,
stable
and
the
lts
version.
So
we
have
a
minor
release
for
maintenance
release
for
stable
and
nps
and
then
a
major
release
for
alpha,
but
we
have
a
regression
down.
So
would
you
like
to
take
this.
F
Yes,
so
usually
the
kernel
releases
of
stable
corner
releases
with
point
releases
like
67:
they
those
should
not
have
any
bulk,
but
in
this
rare
cases
we
hit
another
rare
cases
of
melanox
driver
so
coupled
with
bonding
drivers
in
the
linux
corner,
so
that
resulted
in
network
unreachability
in
case
if
users
are
using
c3
small
instances
or
other
large
instances
in
on
packet
packet,
slash
economics
method.
F
So
we
started
this
issue
just
several
hours
ago,
and
so
thanks
for
all
folks
who
have
made
debugging
the
issue
so
right
now
we
stopped
on
our
updating
server
to
not
update
to
the
latest
releases.
Alpha
345
and
stable
29,
2905
2.2.4.
F
And
from
now
on,
it
should
be
okay,
but
unfortunately,
last
night
many
servers
already
downloaded
the
new
body
releases,
so
it
should
be.
It
could
be
an
issue
in
in
the
excuse
near
future,
so
we
should
be
preparing
fixed
releases
soon.
Also,
we
should
revert
the
same
link
to
a
current
same
link
on
the
flat
card.
Origin
server.
E
Okay,
so
thanks
thanks
dongsu
for
the
update,
so,
okay,
so
after
the
meeting,
we'll
revert
back
to
the
alpha
and
stable
to
the
previous,
siblings
and
peter
was
not
affected,
but
because
it
was
released
a
couple
of
days
back
and
it
does
not
have
the
affected
kernel
and
yeah.
So
that
gives
the
current
state
of
releases.
We
are
preparing
next
week
for
the
next
set
of
releases,
so
we
can
quickly
jump
okay,
so
yeah.
So
this
is
one
announcement.
E
Seagroves
v2
has
landed
in
beta
now,
so
it's
a
good
time
to
start
changing
before
it
lands
into
stable
and
if
you
are
already
so,
it
is
a
good
time
to
like
start,
have
tests
around
in
your
infrastructure.
And
if
you
have
issues
please
file
them
so
that
it
gets
a
better
visibility
in
the
team
and
we
can
file
them
as
soon
as
possible.
E
F
E
Now
is
the
screen
visible,
yeah
yeah,
yes,
okay,
so
is
william
around
no.
E
No
okay,
so
so
before
we
start
up
so
in
in
last,
from
the
last
release,
we
have
started
to
look
one
release
ahead,
so
the
planning
for
the
18th
october
releases
here
as
well,
but
before
jumping
on
to
that
one
I'll.
Let's
discuss
on
what's
the
state
of
the
next
release,
which
would
be
probably
which
would
be
pushed
out
around
4th
of
october.
E
So
the
next
release
we
are
having
a
few
of
the
packages
that
are
getting
updated,
which
is
this
list,
has
not
changed
a
lot,
but
we
have
a
few
packages
that
are
still
in
pending.
We
know
orco
provo
wanted
to
pick
a
couple
of,
so
we
might
need
to
bring
him
that
we
would
start
the
chili's
around
friday.
E
So
if,
if
he
wants
to
sum
it
up
here,
it
could
be
good
if
he
can
do
it
before
that,
but
we
have
ideally
call
get
polka,
legit,
crypt,
util,
linus
and
them
which
are
kind
of
not
yet
started,
and
then
we
have
systemd
which
are
almost
towards
the
finish
line,
and
then
we
have
two
packages
which
are
already
merged.
So
so
one
thing
I
was
thinking
like
how
is
the?
E
E
Because,
right
now
I
am
currently
working
on
pushing
system
d
and
with
the
other
things
I
might
pick
up
like
one
package
more
so
do
other
folks
like
don
so
matthew.
Do
you
think
you
can
pick
one
package
yeah.
B
E
Yeah,
so
we
just
got
an
update
on
poor
kid
that
it's
almost
ready,
so
hopefully
we
can
release
that
next
week.
So,
okay,
so
I'll
keep
it
as
it
is.
If
not,
we
will
move
the
packages
the
pending
packages
to
the
next
release,
and
as
of
now
we
have
did
a
bunch
of
package
updates
in
work
for
the
python
3
upgrade.
E
So
we
have
a
lot
of
packages
in
there
and
yeah
those
are
mostly
going
in
along
with
the
systemd
which
should
be
merged
by
this
week
and
yeah.
So
one
pressing
question
I
wanted
to
ask
like
we
haven't
done
stable
release
in
like
from
july,
so
do
you
think
I
have
put
in
like
for
the
18th
of
october
release,
I
put
in
like
a
major
alpha
and
a
major
beta.
So
do
you
think
we
should
do
a
major
stable
as
well.
B
E
No
worries
so
yeah,
so
it's
the
same
thought
so,
rather
than
accumulating
all
the
releases
and
then
pushing
out
a
big,
stable
release,
it
would
be
better
to
divide
this
chunk
because
we
would
again
have
the
few
of
the
like
the
system,
d
upgrade
and
stuff
that
would
be
coming
in
in
the
next
one.
So
it
would
be
good
to
push
the
small
and
then
a
few
other
packages,
so
it
would
be
good
to
divide
it
into
two
smaller
staple
rather
than
having
a
big
one.
A
Yeah,
I
agree,
I
think
we've
been
waiting
for
a
while
with
a
new,
stable
release
now
hoping
that
arm64
and
system
b249
get
in
in
time,
but
I
mean
it's
a
it's
actually
very
good
idea
to
to
to
stagger
those
and
to
wrap
up
this
table
right
now,
so
everybody
can
deal
with
the
c
groups,
v2
fallout
and
then
in
maybe
two
months
later,
wrap
up
everything
in
the
in
a
stable
that
then
ships,
the
latest
system
d
and
full
arm
64
support
that
makes
sense
right
yeah.
A
I
have
a
quick
and
a
quick
annotation
to
the
openvm
tools
that
is
planned
for
for
next
for
the
next
release.
That
one
usually
is
a
very
low
hanging
fruit.
So
if
there
are
any
pickers
that
just
want
to
bump
this,
I'm
gonna
try
their
hands.
We
almost
never
run
into
issues
of
upgrading,
open,
vm
tools.
As
far
as
I
recall,
just
just
saying,.
E
Sure
yeah,
so
what
we
can
try
is
that
we
can
try
to
get
them
because
most
of
them
are
from
portuguese.
So
we
can
try
to
just
update
and
trigger,
build
and
see
how
things
looks
and
if
not
they
can.
We
can
always
we
can
throw
them
into
the
next
one,
but
yeah.
E
So
anything
else
which
folks
would
be
so
we
have
a
one
thing
which
I
just
talked
with
right
before
this
meeting.
So
we
had
like
this
placeholder
thing,
so
a
community
member
actually
created
a
toolbox
pr,
so
I'll
just
update
that
after
the
meeting.
E
Yeah,
so
we
are
good
I'll,
just
quickly
move
to
the
next
one.
Just
next
week.
E
Sorry
yeah,
so
yeah
so
feel
free
to
join
in.
As
we
mentioned,
there
are
a
few
packages
that
needs
update
and
they
are
pretty,
they
should
are
pretty
straightforward,
so
feel
free
to
join.
E
And
if
you
are
facing
issue,
we
are
very
active
on
the
matrix
channel,
which
is
bridge
to
irc,
so
feel
free
to
join
there
and
yeah
and
like
if,
even
if
you
just
want
to
talk
about
the
about
the
community
and
stuff,
feel
free
to
join
in
and
share
your
opinions
there,
and
we
will
see
you
folks
in
the
next
community
call
any
question
before
we
part.