►
From YouTube: Flatcar Container Linux release planning
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
So
I
hope
my
screen
is
visible,
so
welcome
everyone.
I.
A
B
This
everyone
is
here
I'll,
just
check
the
participants.
B
Yes,
cool
so
welcome.
Welcome
everyone
to
the
23rd
november,
ready
flat
card
release
team
meeting
the
agenda
of
the
meeting
would
be
as
usual.
We
welcome
the
we
do
a
welcome
round
of
welcome
and
then
we
state
the
give
a
state
of
the
current
release
for
going
out.
We
do
the
release
planning
and
then
we
do
a
q
a
and
discussion
in
case
you
have
any
questions
going
ahead,
so
hi
everyone,
I'm
cyan.
C
D
F
E
From
the
flightcard
team
at
microsoft-
mostly,
I
don't
know
debugging
and
quality
insurance,
maybe
yeah,
okay,
who's
next
matthew.
A
Yes,
hi
everyone
thanks
guy,
he
is
mature
from
france
working
in
the
flat
car
team
maintainers,
and
I
work
mainly
on
etsy,
linux,
related
stuff,
ignition
and
yeah,
providing
some
cool
tests
for
the
us
dongsu.
B
That
goes
everyone
so
moving
ahead,
oh
yeah,
so
state
of
the
current
release.
So
we
did
a
release
on
ninth
november,
which
was
the
during
the
I
guess
it
was
just
after
the
community
call,
so
the
status
of
it.
We
have.
B
We
actually
promoted
the
a
new
stable,
so
we
have
c
groups
into
stable
and
then
we
also
promoted
beta,
and
then
we
will
have
more
updates
about
like
the
22nd,
the
19th
of
november,
we
in
the
release
planning
so
quickly.
Moving
on
to
the
release
planning
board.
B
Can
you
see
this
release
planning
mode,
yeah,
so
yeah?
So
we
did.
We
have
a
release
in
progress
so
down
so
matthew.
Can
you
just
give
a
status
on
that
like
how
how
it
looks.
A
Yes,
we
got
some
issues
with
arm64
on
equinix
metal,
but
that
most
of
the
tests
are
blue
or
green
depend
of
your
opinion,
so
yeah
it's
it's
good
shape
so
dongsu.
If
you
want
to
add
something
to
that.
F
E
B
So
right
now
we
had
a
plan
for
a
29
number
release.
Do
you
think
like
we
would
be
going
ahead
with
that
release
or
we'll
be
continuing
with
the
current
one.
B
B
So
we
have
the
29
number
planned
so
given
we
are
almost
like
towards
like
it's
tuesday,
so
it
would
effectively
buy
if
you
re
trigger
the
test
and
also
it
might
take
a
while.
So
do
you
think
we
can
aim
for
the
29th
number
at
least
do
we
want
to
do
that?
Please.
B
So
effectively
so
effectively,
we
are
right
now
doing
the
20.
Second,
this
release
right.
So,
okay,
so
we
would
be,
in
that
case,
marching
I'll,
remove
this
board
I'll
move
this
here
I'll
remove
this
one.
B
Okay,
let
this
column
okay,
so
the
next
question
would
be
like
for
the
13th
release.
B
We
have
like
a
good
set
of
changes
that
needs
to
be
that
is
going
for
the
22nd
one
like
these
are
the
changes
that
are
going
27th,
one
which
is
effectively
the
the
currently
they
are
preparing,
and
then
we
have
the
29th
which
is
getting
merged
into
the
13th
one,
so
I'll,
just
edit.
This
note
copy
this
cut.
This
actually.
E
G
B
A
C
Both
is
fine.
I
take
it
that
even
with
the
stable
that
went
out
previously
like
two
weeks
ago,
there
are
only
minor
bumps
and
we're
addressing
those
so
and
given
that
3033
is
kind
of,
let's
call
it
a
service
patch
release
for
for
the
current
stable.
So
it
brings
a
few
changes,
but
it's
not
as
massive
as
the
current
major
release
and
because
it's
a
nice
wrap
up
of
the
year,
because
that
would
make
arms
stable.
C
It
would
be
pretty
awesome
if
you
could
wrap
it
up.
I
mean
we
could
always
aim
high
and
then
step
back
if
things
look
not
good
enough,
if
you
can't
meet
the
quality
bar
exactly.
B
Yeah,
so
in
that
scenario
like
we,
let's
aim
for
a
stable
release
and
let's
keep
it
the
last
one
of
the
year
and
if
we
miss
if
in
case,
if
there
are
any
issues
and
if
we
miss
in
that
case,
we
do
it
after
people
return
from
vacations
cool.
So
that
would
be
then
three
zero,
three
theta
two
dot
zero,
and
this
would
be
three
zero:
six,
six
dot,
one
dot,
zero.
B
Cool
other
than
that,
regarding
the
issue
on
the
updating
the
os
release
file,
do
you
have
any
update
matthew
on
that?
Are
you
working
on
that.
A
No,
I
don't
work
on
this
issue
yet,
but
it
should
be
pretty
straightforward,
just
need
to
add
a
couple
of
values
into
os
release
file,
so
we
just
need
to
find
the
magic
where
these
things
happen,
but
I
recall
that
hilo
shared
that
previously
when
he
worked
on
the
sdk
container.
So
we
just
need
to
identify
the
very
right
point
where
we
can
put
the
cpe
into
this
file,
but
yeah
not
started
working
on
it.
B
Okay,
cool
and
just
to
update,
give
an
update
on
the
open,
sss
thing,
so
I
did
look
into
it
last
week
there
are
some
hiccups
like
it's.
The
go
has
a
partial
support
for
the
for
the
rsa
and
then
on
the
sgr
and
aws
side.
We,
the
keys,
supported
keys,
are
not
really
the
same,
so
we
need
to
come
around
with
come
around
with
hacks
and
mantels
to
support
the
whole
infrastructure
temporarily.
B
If
you
want
to
update
open
sss
without
that
all
the
all
the
tests
would
fail
and
like
the
boxes
would
be
weak,
you
cannot
test
into
the
boxes
as
as
open
accessory
pointed
brings
breaking
changes,
and
we
again,
I
forgot
to
merge
the
ipv6
changes
given
I'm
leaving
in
in
like
from
day
after
tomorrow.
So
in
case
I
forget
to
merge
this,
I
would
ask
like
dongsu,
mathew
kai.
You
can
probably
merge
this
type,
v6,
vrs
and
yeah.
B
So
talking
of
the
plan
changes
so
yeah,
so
we
still
have
these
packages
to
be
worked
on,
tries
primarily
and
thanks
anybody
for
doing
the
great
job
and
also
to
our
crew
provo.
So
yeah,
that's
all!
I
guess
we
look
good
and.
B
D
That
needs
to
be
added.
I
have
a
question.
What
about
that
db
package?
This
package
was
in
the
chorus
overlay.
I
tried
to
upgrade
down
to
side,
it
needs
to
be
removed,
and
I
was
quite
not
sure
what
to
do
actually
with
the
package.
B
I
guess
it
can
be
just
the
package
can
be
dropped
directly.
I
guess
what
dongle
said,
if
I
recall
correctly
was
like
the
package
is
not
getting
used
anywhere.
D
F
So
if
we
choose
to
update
gcc
to
10,
then
it
might
involve
a
lot
of
other
updates.
So
should
we
do
that,
for
this
release
or
weight
and
just
minor
point
we'll
use
9.4.
C
I
think
it
feels
safer
to
go
for
9.4.
At
that
point,
I
remember
that
I've
tried
updating
to
gcc
10
quite
some
while
ago
in
the
course
of
updating
the
c,
and
I
mean
that
was
some
time
back
and
we
upgraded
quite
a
number
of
packages.
But
the
challenge
here
is
that
gcc
10
turns
is,
has
a
stricter
interpretation
of
inline
and
of
extern
qualifiers
in
see
source
files,
and
that
would
require
all
of
the
packages
to
actually
honor
that
new
and
stricter
interpretation.
C
So
we
could,
we
could
have
a
lot
of
fun
with
older
packages
here.
I
think
9.4
looks
like
a
lower
risk
item.
C
B
And
just
to
like,
in
case
like
when
you
are
preparing
the
release,
like,
I
guess,
given
the
changes
we
brought
to
systemd
with
the
group
and
group
with
the
group
and
stuff,
so
I'm
guessing
like
there
might
might
be
issues
if
there's
some
inconsistent
inconsistency.
So
do
keep
a
look
out
on
that
as
well.
It's
basically
given
we
brought
systemd
very
close
to
the
gentle
upstream,
so
yeah
the
changes
might
create
issues.
In
that
case,
we
might
don't
need
to
look
into
that.
A
Maybe
we
can
try
to
ship
the
fix
to
for
etcd
we
we
got
like
against
today
on
matrix,
so
we
can
try
to
to
to
find
a
quick
fix
and
to
ship
it
in
the
next
release
and
also
for
the
torx
ac
linux
things
to
me.
It
was
fixed,
but
it
seems
not
because
the
patch
is
not
correctly
applied,
so
I'm
still
investigating
on
it.
So
maybe
when
we
can
bring
these
two
two
fixes
into
the
next
release
too,.
B
Cool
yeah,
so
it
would
be
better
like
it
would
be
good
if
you
can
just
add
the
added
in
the
board
and
then.
F
B
Cool,
if
not,
then.
C
Good,
I
have
a
minor
item,
at
least
technologically
it's
a
minor
one,
but
I
think
it's
worth
tracking
on
the
board,
so
we
have
prs
from
you
scion
to
chorus
overlay,
voltage,
stable
and
the
scripts
repo
that
introduced
some
change
for
changelog
generation
sooner
as
those
are
in
the
sooner
those
are
in
the
less
work
we
have
later
on
when,
when
creating
changelogs,
all
three,
I
think
are
still
open
would
be
awesome
if
you
could
put
them
on
this
board
and
and
track
them
for
a
future
release.
C
Just
you
know
for
peace
of
mind
that,
from
that
point
onwards,
we
have
changelog
generation
automated.
B
Yeah,
that's
that's
a
good
point,
thanks
hilo,
so
I'll
I'll
include
it
I'll
get
it
like.
I
got
very
good
feedback
from
kai
everyone
in
the
team,
actually
so
I'll
address
to
them
and
try
to
get
in
march
by
tomorrow,
given
that
we
have
almost
done
with
our
slides
and
stuff
today,
so
yeah.
So
thanks
again
for
folks
who
are
joining
in,
I
know
aniruddha
has
already
probably
knows
the
step,
but
any
folks
who
are
like
placing
it
later
or
like
joining
in
via
youtube.
B
We
are
do
join
in.
We
are
very
active
on
irc
matrix
and
our
email
list.
If
you
have
any
issues,
are,
are
trying
out
flat
car
or
have
looking
into
the
contribute,
just
join
in
and
ask
your
questions
or
paying
us
for
any
issues.
B
If
you
want
to
work
on
and
then
you
can
find
a
more
elaborative
guide
on
the
meetings
that
we
do
on
our
flat
card
buck
tracker
and
then,
if
you
have
any
feedback
again
feel
free
to
join
into
our
communication
channels,
to
let
us
know
about
the
feedback
and
yeah
and
we
will
be
again
meeting
in
the
next
community
community
meeting,
which
is
in
two
weeks
so
see
you
see
you
then,
before
we
leave
any
questions
before
we
leave.