►
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).
B
C
So
welcome
everyone
to
the
flat
car
content
linux
university
meeting.
This
is
in
this
meeting.
We
will
be
primarily
discussing
to
through
the
release
planning
stuff
and
if
you
have
any
other
questions,
also
feel
free
to
chime
in
at
the
end
and
ask
questions
or
any
discussion.
You
would
like
to
be
part
of
so
quickly.
So
the
agenda
for
the
meeting
is,
we
usually
start
with
the
round
of
introductions,
and
then
we
discuss
the
state
of
the
current
release
and
then
the
release
planning
and
finally,
the
discussion.
C
E
A
Oh
yeah,
so
I'm
no
problem,
I'm
a
regular
hi,
I'm
tilo!
I
manage
the
flat
card
team
at
microsoft
and
yeah.
C
Thanks
hilo
yeah,
so
quickly,
moving
on
to
the
release
planning.
So
before
we
move
on
like
we
just
completed
the
setup
release
and
it
the
alpha
has
a
lot
of
package
updates.
So
it
includes
bash,
systemd
and
other
a
bunch
of
updates,
which
it
also
fixes
a
lot
of
cvs,
and
we
have
so
alpha
was
the
major
release
and
then
we
had
beta,
stable
and
lts.
Oh
lts
version
is
wrong,
but
it
had
the
patch
releases.
C
So
just
to
update,
so
we
are
planning
as
we'll
go
into
the
release
planning
board,
but
just
to
update
that
we
will
be
updating
the
stable,
so
c
group
suite
2
would
be
landing
in
stable
next
week.
C
So
if
you
are
still
on,
if
you're
not
still
running
like
flat
on
your
beta,
so
it's
a
good
time
to
start
a
few
bit
instances
and
check
how
your
applications
are
running
and
if
you
have
issues
feel
free
to
ping
or
some
metrics
or
fight
issues
for
the
same
okay,
so
planning
board
I'll
share
the
planning
for
screen.
C
Okay,
so,
as
I
mentioned
so
with
the
with
the
current
release,
so
we
would
be
starting
up
the
release
end
of
this
week,
so
we
would
have
the
next
release
going
out
in
the
beginning
of
next
week,
so
that
would
be
that
would
include
a
major
alpha,
major
beta
and
major
stable
and
then
a
batteries
for
lds,
and
so
we
have
a
lot
of
packages
getting
updated
on
the
on
the
for
the
next
release
as
well.
C
So
the
packages
we
have
the
list
of
packages
in
here,
if
you
can
notice-
and
then
we
are
also
we've
probably
fixed-
we'll-
also
include
the
ipv6
changes
which
should
fix
this
two
issues:
the
pr
open
and.
C
So,
okay,
so
any
other
thing
that
you
folks
are
working
on,
which
is
not
mentioned
here
or
not
in
the
tracking
board.
C
So
log
property:
is
there
right
yeah?
So
it's
so
we
it's
in
progress
right,
so
you
we
have
been
tracking
it
in
the
in
the
package
board.
This
is
the
pr.
C
Yeah
yeah,
so
this
this
so
do
make
sure
we'll
start
off
the
builds
on
friday.
So
if
you
want
to
have
a
quicker
look
at
folks
or
if
you
want
to
get
it
merged
like
get
it.
B
C
Cool
for
the
next
one,
so
one
thing
I
noticed
that
we
have
actually
updated
quite
a
lot
of
packages
in
the
like
from
what
we
started
off
like
a
lot
of
packages
are
like
very
close
top
streams,
but
for
the
for
the
next
release,
like
on
the
15th,
the
one
which
we'll
be
doing
15th
of
november,
I
was
looking
through.
The
code
was
overlaid,
the
like
list
of
packages,
which
probably
needs
update,
and
I
accumulated
a
few.
These
are
just
like
picking
up.
C
I
did
not
go
through
them
in
depth,
so
that's
why
I
mentioned
triatch
and
update
so
tongsu.
Do
you
think
dongsukai
matthew?
Do
you
think,
like
any
of
these
packages
have
prior
blockers
that
needs
to
be
addressed?
E
C
Okay,
so
in
that
case
I
would
say
like
after
we
wrap
up
the
next
release,
we
can
then
start
looking
into
this
one.
These
are
like
the
last
few
packages
and
coreos,
which
I
think
needs
to
be
looked
into
and
get
updated
to
the
latest
with
the
upstream
and
then
we
can
probably
like
go
through
once
and
like
have
us,
create
a
tracker
and
see
which
are
like,
which
needs
another
set
of
update,
basically
a
new
role
of
updates,
but
this
is
a
good
news
that
we
have
like.
C
C
And
dongsu
added
this
to
which
I
think
is
possible
for
doing
for
the
for
the
15
number
release
and
other
than
that,
I'm
also
planning
like
I
kept
the
board
a
bit
empty
because
since
we
will
be
doing
a
stable
release,
so
I
expect
hiccups
and
people
filing
issues.
So
we
need
to
keep
a
space
for
that
one.
E
One
thing
I'm
wondering
about
is
gold,
so
today
I
realized
that
we
forgot
about
updating
goal
16.9
for
beta
and
probably
alpha,
and
so
currently
the
git
of
actions
do
not
automatically
update
in
case
of
gold
versions
diverging
from
the
main
branch.
So
it's
not
ideal,
but
probably
we
first
need
to
manually
update
and
after
that
we
should
think
about
how
we
start
to
ultimate
automate.
The
goal
of
updates
in
the
maintenance
branch.
C
Right
right,
yeah,
I
did
notice
you
creating
like
adding
that
to
the
note
for
the
last
for
the
next
week's
release
so
yeah.
We
need
to
look
into
that.
C
And
do
we
think,
like
you
can
do
w
get,
should
be
simple,
but
do
you
want
to
push
it
to
the
next
one,
or
is
this
good.
E
C
C
Okay,
so
I
think
this
looks
good
yeah,
so.
C
C
So
folks,
joining
in
early
watching
it
watching
the
recording
on
watching
the
recording
later
on
youtube,
if
you,
if
you
want
to
jump
into
and
contribute
to
flat
car,
feel
free
to
do
so,
we
are
active
on
matrix
and
also
on
the
flat
car
issue
tracker.
So
if
you
face
any
issues,
feel
free
to
ping
us
on
the
given
channels-
and
we
do
this-
call
the
release
team
call
monthly,
and
then
we
have
the
community
call
which
again
happens
monthly.
C
So
the
cadences
for
the
flat
course
is
around
bi-weekly,
so
feel
free
to
join
the
next
community
meeting
and
we
are
always
open
to
feedback,
and
we
would
like
to
have
your
feedback
on
the
same.
A
Other
than
it's
quite
a
reason
to
celebrate
to
have
most
of
chorus
overlay
updated,
I
mean
that's,
that's
pretty
awesome
great
work.
C
Yeah,
that's
actually
some
good
news,
like
so
yeah
kudos
to
the
team.
C
Cool
then
we
can
end
here
thanks
everyone
for
joining
and
have
a
great
rest
of
your
day
and
see
you
on
the
community
call
see
you
bye.