►
From YouTube: Flatcar Container Linux release planning 2022-2-22
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).
B
C
Sorry,
you
can
go
ahead.
You
should
be
able
to
share
now.
D
A
The
screen
is
visible,
yes,
so
hello,
everyone
welcome
to
the
february
flightcard
release
team
meeting
and
so
quickly
going
over
with
the
introductions.
Let's
see
if
we
have
any
new
participants,
I
don't
see
any
new
participants
peter.
Would
you
like
to
give
an
introduction.
E
Peter
pugliat
from
ampere
computing
I
work
in
developer
advocacy
I'm
here
to,
I
guess,
find
out
more.
What's
in
what's
gonna
happen,
today's
meeting.
A
Cool
thanks
for
joining.
So,
let's
move
on
to
the
next
section.
So
we
have
so
the
agenda
is
we'll.
Have
some
news
we'll
discuss
the
state
of
the
current
release
that
we
are
ongoing,
then
the
release
planning
and
the
and
then
we'll
finally
close
off
with
the
discussion
or
q
a
so
welcome
everyone?
We
already
did
the
introduction
okay
produce
planning
so
jeremy.
Would
you
like
to
take
this
line.
B
Sure
so
hi
everyone,
as
cyan
said
I
would
be
presenting
this
slide
so
so
in
the
last
community
call.
I
believe
tito
talked
a
bit
about
the
state
of
c
groups
on
falcor.
B
So,
as
you
may
recall,
slackcard
switched
to
c
group,
sweet
2
in
I
think
november
and
since
then,
we've
been
monitoring
how
that
has
been
received
by
the
community.
So
we've
had
bug
reports
of
issues
that
popped
up.
Since
then,
we've
had
feedback
from
various
user
groups
of
how
this
impacts
them
and
in
cases
in
which
secret
suite
does
not
work
for
them.
B
So
we
are
currently
working
on
on
a
way
to
to
ease
the
lives
of
people
who
would
like
to
stay
on
on
seagroves
v1
and
on
the
on
the
sigru's
front.
We
have
three
three
items
of
news.
One
is
that
container
d1.60
has
been
released
just
last
week,
which
includes
a
pr
that
we
submitted
to
fix
a
resource
leak
that
I
had
on
c
group's
v2,
so
container
d
switch
to
using
inodify
notifications
for
our
out
of
memory
conditions
and
on
secret
c2
systems.
B
It
has
been
leaking
these
instances
every
time
a
container
crash
restarts,
so
that
should
be
fixed,
and
this
container
d
version
will
be
making
its
way
through
through
to
all
of
the
flat
card
channels.
Kai
talked
about
a
script
that
he
created
for
people
who
can
who
wish
to
take
our
amis.
So
this
one
is
aws,
specific
and
post-process
them
to
make
them
boots
up
with
c
groups.
V1,
and
I
am
working
on
a
way
to
to
run
time,
switch
to
sigru
c1
on
first
boot.
B
So
there
will
be
a
flag
file
that
you
can
create
through
ignition,
and
the
node
will
will
will
start
its
life
as
a
legacy
group
node.
So
there
will
be
no
reboot
required
to
to
switch,
and
we
hope
that
this
way
we
we
cover
all
use
cases
and
people
can
continue
running
what
works
best
for
them
so
expect
that,
in
in
in
a
release
coming
soon,
thanks
zion,
you
can
take
over
again.
B
Sorry,
just
one
thing:
I
linked
some
some
content
from
the
agenda
in
the
flat
in
the
github
discussions
page,
so
there's
a
there's,
a
blog
post
about
the
container,
the
issue
that
has
gone
live
today
and
I
also
linked
to
kai's
paragraph
in
the
documentation
talking
about
the
ami
generation
script
and
the
the
the
runtime
c
group
switch
will
also
be
documented
on
our
switching
to
unified
c
groups
page,
which
also
contains
instructions
for
for
returning
to
legacy
cc.
Group.
A
Thank
you,
yeah,
thanks
for
the
update
moving
ahead,
so
just
just
give
a
state
of
the
release,
we'll
be
doing
alpha
major
version
and
beta
major
version
next
week
and
the
maintenance
release
for
the
staple
and
the
fts
channels,
and
we
will
be
discussing
through
how
things
look
when
we
are
discussing
our
planning
board
so
quickly.
Okay,
so
just
to
give
an
update
on
fourth
of
march,
we
are
planning
documentation
writing
day.
A
So
the
agenda
would
be
very
similar
to
on
how
we
did
it
with
the
bug
smashing,
but
here
we'll
be
focusing
on
the
documentation
and
we'll
be
looking
through
the
sections
which
needs
more
clarity
and
building
more
docs.
For
so
that
users
community
can
make
use
of
flat
card
in
a
more
better
manner.
Yeah
so
cube,
so
keep
that
date
sandy
it's
fourth
of
march,
which
is
coming
soon
yeah
and
it
would
be
happening
on
the.
D
A
A
A
So,
just
to
give
a
small
just
to
explain
how
things
work,
so
we
have
five
columns.
Primarily,
we
have
the
two
loop
to
do
plan.
We
have
the
long
term
locked
in
progress
and
ready
to
review
and
then
ready
to
release
the
ready
to
release,
has
the
items
which
are
already
in
the
main
channel
or
are
into
their
respective
channels
release
channels.
Reddit
reviews
are
the
ones
other
pr's
which
are
open
to
review,
and
anybody
can
do
the
review
of
the
of
those
pr's.
A
And
then
we
have
the
in
progress
where
we
list
all
the
issues
and
the
pr's
which
are
currently
in
works,
and
then
the
long
term
items
would
be
the
ones
which
we
are
primarily
looking
into
long-term
solving
and
we'll
be
giving
a
regular
update
on
those
items.
And
then
we
have
the
package
update.
We,
prime
usually
in
the
to-do
plant.
We
usually
list
the
issues.
We
prime
want
to
look
and
look
into
in
the
next
release
and
then
the
packages
that
we
are
planning
to
look
into.
A
So
as
of
now,
we
have
the
list
you
can
see.
We
have
a
bunch
of
packages
that
are
getting.
Will
be
which
will
be
released
in
the
next
release
set
of
releases,
a
bunch
of
them
are
in
progress
and
we
have
a
couple
of
backlogs.
So
if
you,
if
folks,
want
to
look
into
it,
if
you
are
open
to
contributing
this,
these
are
the
packages
that
you
can
start
looking
into.
A
A
And
on
the
so
any
issue,
any
of
any
issues
that
you
want
to
like
team,
we
want
to
get
included
in
the
release,
planning
that
we're
missing
something
you
would
like
to
add.
D
A
Yes,
so
I
was
looking
into
it
and
we
did
hit
some
issues
with
the
with
the
with
the
e-classes.
So
I'll
probably
need
to
look
into
it
again,
but
that's
why
I,
since
I
was
it,
was
there
for
some
time,
so
I
put
it
back
into
backlog
because
I
there
is
some
in
progress
code,
but
it's
not
actively
looked
into
so
but
yeah.
A
We
did
hit
some
issues
there
and
right
now
the
thing
that
I'm
looking
into
there's
a
field
built
in
jenkins,
where
you
could
see
like
the
grid
setup
and
the
util
linux
that
has
that
is
broke.
So
that's
of
focus
right
now
for
me.
So
yes,
if
you
want
to
look
into
system
video,
you
could
but
yeah.
That
was
the
issue
which,
which
is
why
I
moved
it
from
in
progress
to
backlog.
A
A
And
for
the
for
the
14th
march
release
we
see
we
did
have
a
bunch
of
packages
updated
to
the
backlog.
So
if
you
folks,
you
want
to
contribute,
you
could
also
look
into
the
backlog
and
I
would
like,
if
folks
start,
to
look
more
actively
big
because,
as
you
see
like
most
of
the
backlog
from
the
from
the
next
release,
which
eventually
move
into
like
our
14th
march,
so
that
would
actually
make
a
huge
lot
of
packages.
So
we
probably
need
to
again
cut
it
down.
A
A
Oh,
no
anybody
else
who
knows
the
update
for
the
blocked
items
for
the
ip
root
and
the
linux
5.16
hourly
planning.
B
I
I
don't
know
what
crazy
mere
state
is,
but
I
think
it
would
be
a
bit
early
to
to
to
ship
these
updates.
A
F
F
C
I
think
we're
good
with
510,
given
that
is
that's
an
lts
release
and
it's
been
reasonably
soaked
in
in
stable
by
now.
I
think
the
thing
that
we
still
missing
stable
that
we
need
to
bring
in
is
the
the
c
groups
v1
option
for
deployment.
Otherwise
I
think
we'll
shy
away
a
lot
of
folks
from
from
the
new
lts,
but
as
soon
as
we
have
that,
I
think
we
are
good
to
wrap
things
up.
A
Okay,
okay,
so
I
guess
in
that
case
one
thing
I
just
wanted
to
know
like
jeremy:
how
are
things
looking
on
like
with
the
c
groups
thing?
So
are
we
planning
to
get
it
merged
by
next
week
because
we
would
be
starting
the
bids
on
friday.
F
Yeah,
I
think
by
next
week
is
realistic,
and
but
the
question
is
whether
we
directly
put
it
in
stable
or
like
yeah,
I'm
a
bit
hesitating
to
say
that
goes
straight
to
stable,
and
I
think
a
back
port
at
some
later
point
would
be
the
nicer
approach.
If
we
have
it
in
beta
and
if
it
is
for
one
release
cycle.
C
B
C
Really
well
sometimes
the
folks
who
reported
that
back
to
us
aren't
currently
using
the
new
stable,
because
they
can't
pick
with
that
option.
They
can
start
evaluating
the
news
table
right
and,
if
you
don't
impact
existing
users
of
the
current
stable,
I
think
we're
very
good
to
go
in
in
this
case.
That
thing
would
need
to
stabilize
and
stable
and
we
will
we
will.
We
would
need
to
iterate
on
the
input
that
we're
getting.
I
don't
think
they'll
switch
to
beta
and
have
a
look,
those
folks
that
reported
this.
This
issue
to
us.
C
And
if
we
need
more
time
to
spend
on
testing
or
on
development,
I
think
it's
perfectly
okay
to
push
back
the
overall
release,
a
little
like
just
judging
from
the
feedback
that
we
got.
A
And
we
can
totally
move
the
releases
in
that
case
to
probably
sometime
next
week.
We
still
have
that
anyway,.
A
A
I
take
that
as
a
no,
so
let's
move
back
to
the
slides,
so
yeah
so
again,
as
you
saw
that
there
are
a
lot
of
work
that
is
ongoing
and
that
needs
to
be
done
so
folks.
If
you
would
like
to
join,
we
have
the
regular
matrix
channel
where
you
can
join
us
embrace
to
the
irc
and
we
also
have
our
mailing
list.
You
could
also
find
our
issues
on
the
flat
card
linux,
flat
car
repo,
and
then
we
are
having
the
community
called
next
next
month.
A
So
do
join
for
spotlights
and
more
introduction,
more
talks
on
flat,
car
and
other
than
that
yeah.
So
do
keep
spreading
the
word
about
flat
card
and.
C
So
if
you
want
to
take
on
and
upgrade
one
of
those
packages
that
are
in
the
queue
for
being
upgraded,
it's
pretty
straightforward.
We
have
a
number
of
talks
and
recordings
online
on
how
to
do
that,
and
we're
absolutely
here
for
supporting
you
if
you
just
want
to
take
it
on
and
you're
unsure
what
to
do
just
speak
up
in.
A
Metrics,
I
was
actually
thinking
one
thing
that
if
we
could
now
that
we
have
bunch
of
talks,
but
they
are
in
different
conferences
if
we
could
just
put
them
into
a
simple
single
place
into
a
repo,
maybe
the
same
flat
card
repo
with
docs
folder
and
with
the
slides
and
the
or
just
or
read
me
with
with
the
description
to
linking
to
the
videos.
C
A
No,
so
thank
you
all
for
joining
have
a
great
rest
of
the
evening
and
see
you
in
the
community
call
bye
thanks,
sayon.