►
From YouTube: Flatcar Release Planning | 2021-07-26
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
B
B
B
B
B
A
C
D
All
right,
I
think
most
of
us
are
here:
let's
get
this
thing
started:
welcome
everybody
to
our
first
standalone
public
release
planning.
This
will
be
a
meeting
that
will
happen
in
a
two-week
cadence.
You
can
tune
in
and
give
your
input
to
either
the
upcoming
releases
or
what
should
be
included
further
down.
The
road
cyan
will
give
you
the
details.
D
There
are
two
announcements
that
I'd
like
to
cover
before
we
start
the
first
one
is
our
release
originally
intended
for
last
week
is
slightly
delayed,
we're
fighting
a
few
unrelated
internal
automation
issues
or
not.
We
expect
this
release
to
go
up
tomorrow
or
the
day
after
that
and
the
second
is:
we
have
a
survey
for
you
yay,
so
we're
going
to
publish
a
survey
tomorrow
on
the
emailing
list
on
metrics
and
on
twitter.
D
It's
unlikely,
you'll
miss
it
and
it
would
be
awesome
if
you
could
have
a
look
and
help
us
out
by
giving
us
your
feedback
on
how
flatcar
is
doing
that
said,
handing
off
to
scion
for
the
release,
planning.
A
Thanks
hilo,
so
so
the
agenda
of
the
meeting
would
be
this
is
this
is
the
first
time
we
are
doing
this
call
separately
from
the
community
call.
So
the
agenda
would
be
like
welcoming
the
participants,
but
for
the
first
call
we
can
go
around
with
the
round
of
introductions.
A
Then
we
would
give
a
state
of
the
current
release,
which
thilo
gave
a
brief
idea
about
the
current
release,
but
we'll
cover
a
bit
more
in
depth
and
then
the
main
part,
the
release
planning,
where
we
talk
through
the
board
and
discuss
through
the
issues
and
add
the
issues
in
the
public
github
planning
board,
and
then
finally,
we
will
end
up
with
a
q,
a
or
discussion.
If
you
have
any
points
to
add
or
anything,
you
would
like
to
discuss
in
this
meeting
so
before
we
start
so
welcome
everyone.
A
F
F
G
Yeah
hi
everyone
mature
working
the
flat
car
team
since
a
few
months
now
and
joining
the
zoom
call
through
my
cell
phone,
because
I
still
messing
with
zoom
on
my
computer.
H
I
Yeah
so
william,
calling
in
from
rotterdam
also
on
the
flatcar
team,
working
primarily
on
arm64,
related
matters
and
is
that
everyone
from
kinfolk
proper,
I
think
so.
J
Hi
I
am
aniruddha.
I
am
currently
working
on
the
locksmith
project
on
a
bug
with
matthew.
F
C
Sure
I'm
jim
perrin
I'm
one
of
the
program
managers
here
at
microsoft.
I
am
doing
this
one,
basically
as
a
community
member
previously
of
the
centos.
A
A
Okay,
so
thanks
everyone
and
welcome
again
so
moving
ahead
with
the
release
planning.
So,
as
hilo
mentioned,
that
we
usually
have
the
details
of
the
previous
release
or
the
release
on
ongoing
release
stuff
in
this
page.
But
for
the
current
release,
we
are
having
some
hiccups
and,
as
people
mentioned,
that
we
would
probably
have
a
release
by
tomorrow
or
day
after
tomorrow.
So
keep
it
out.
Look
out
for
the
releases
page
on
our
flat
car
website.
A
Okay,
so
moving
quickly,
moving
ahead
to
the
planning
board,
I'll,
stop,
sharing
and
share
the
planning
board
screen.
A
Okay,
so
I'll
just
give
a
brief
overview
about
folks
who
are
joining
in
new.
So
this
is
a
public
release.
Planning
get
a
board
and
there
are
a
couple
of
columns.
A
Primarily
there
is
a
pla
planned
column
which,
where
we'll
be
primarily
planning
the
items
that
we
would
like
to
work
on
the
next
release,
and
then
we
have
the
in
progress
where
we
pull
our
pull
the
issues
in
which
are
in
progress
and
are
close
to
getting
merged
and
probably
would
be
seen
in
the
next
release
cycle.
A
And
then
we
have
the
ready
to
review
which
the
the
folks
can
move
around
when
they
see
that
the
the
pr
is
or
the
issue
is
kind
of
done
or
is
open
for
review
by
the
flat
time
maintainers,
and
then
we
have
a
series
of
ready
to
release.
So
these
are
the
releases.
A
So,
whenever
the
reddit,
whenever
you're,
whenever
the
pr
or
the
issue,
is
complete,
it
moves
to
the
next
release
right
now,
if
you
see
it
is
covering
four
releases,
but
the
plan
is
that
after
every
release,
so
at
max
there
would
be
three
releases.
That
would
be
pop
three
release
columns
here.
So
once
this
meeting
is
over
I'll
remove
the
one
from
the
16
june
and
then
you'll,
we
will
be
having
only
the
from
the
20th
june
and.
A
A
In
the
current
ongoing
release,
we
are
planning
release
across
all
the
channels
and
for
the
next
one
I
so
during
the
kind
of
the
meeting
prep
phase,
I
planned
that
we
would
be
doing
alpha
release
and
then,
with
the
current
alpha
release,
we
are
having
a
bunch
of
fixes
that
kind
of
the
2942
release
is
a
kind
of
a
major
one.
So
it
would
be
good
that
we
update
it
to
beta
for
stabilization
and
then
for
the
stable
one.
A
It
will
primarily
be
even
like,
with
the
current
stable
we
are
having.
We
are
doing
a
major
release
so
for
the
next
for
the
next
stable
release,
it
would
be
one
a
minor
one
where
we
just
pull
in
the
kernel,
updated
kernel
versions.
Does
that
sound
good,
any
yep?
A
Okay,
and
so,
as
you
see
here,
that
the
next
release
would
be
happening
on.
Second
of
august,
which
is
in
a
week's
time,
and
given
the
already
we
have
been
working
on
the
current
release,
so
we
picked
up
a
couple
of.
I
picked
up
a
couple
of
two
planned
ones,
which
are
which
are
primarily
like
package
updates,
which
we
can
look,
and
there
are
a
couple
of
in
progress,
one.
So
keeping
everything
into
mind
that
we
I
kept
the
list
short
for
the
package
update.
A
So
primarily,
there
has
been
like
a
nvidia
drivers
update
and
then
we
have
live
archive,
expert
and
vinutels
and
then
bash
work
that
has
been
going
for
a
couple
of
releases,
so
that
is
also
included.
This
is
given
the
short
period.
A
I
think
it
would
be
better
to
have
a
like
a
set
of
packages
which
would
be
easier
to
like
update
in
a
week's
time
and
given
the
current
release
overload,
I
think
this
makes
a
good
choice
other
than
that,
if
you
folks
have
any
other
comments
or
any
packages
that
I,
which
should
be
added,
do
feel
free
to
speak
up.
A
Cool
so
another
thing
I
was
wondering
as
like:
we
have,
though
we
have
added
the
ssm
agent
work,
but
I'm
not
sure
if
we
could
complete
it
in
this
recycle.
Given
the
package
updates
we
have
already
pending
and
but
I
was
wondering
like
jeremy,
do
you
think
we
should
add
the
docker
update
work
into
the
in
progress.
H
H
Can
you
hear
me?
Yes?
Yes,
yes,
okay,
yeah!
Definitely,
I
would
add
it
to
the
in
progress.
The
way
it's
looking,
I
I
don't
know
you
said
the
next
release
would
be
next
week
right.
H
A
I
think
it's
a
good
idea
to
include
it
in
the
in
progress
one
so
that
we
have
a
good
state
of
what
is
going
on.
Definitely.
H
A
And
anirudh
matthew,
so
I
anirudh
had
submitted
a
pr,
and
so
that's
also
will
be
going
into
this
release
right.
It's
almost
almost
to
completion.
A
E
So
there's
this
kernel
size
problem.
We
have
the
kernel
together
with
the
integrand
file
system
and
they
are
approaching
the
maximum
size
of
fitting
twice
into
the
wood
partition,
and
I
started
a
build
of
trying
out
whether
we
can
change
the
compression
algorithm
and,
if
yeah,
if
that
is
already
helping
enough
or
what
other
things
are
open,
but
yeah,
it's
not
really
ready
yet.
So
that's
why
I
I'm
not
adding
it
to
the
column
but
yeah,
maybe
tomorrow
I
know
more.
A
Sure,
okay,
do
you
think
we
should
like?
I
think
you,
since
you're
already
working
on
the
issue,
like
maybe
create
an
issue
with
the
findings
that
you
posted
on
the
on
the
irc
channel
or
the
matrix
channel,
and
then
we
can
add
it
here.
A
Anything
else
that
that
needs
attention
given
the
short
cycle.
I
think
this
should
be
good.
A
A
If
not,
then
I'll,
then
quickly,
I
think
then
we
can
set.
Everyone
is
good
with
the
current
issues
that
we
are
working
on.
The
team
is
working
on
and
yeah
the
community
is
working
on.
So
I
think
we
are
good
to.
We
are
in
a
good
state
for
the
next
release.
Planning.
A
Okay,
so
I'll
go
back
quickly,
go
back
to
the.
A
A
Okay,
so
yeah,
so
as
as
we
have
been
always
talking
about
like
this
is
a
great
opportunity
to
if
you're
looking
for
contributing
to
flat
car.
There
have
been
a
good
number
like
a
like
a
rise
in
the
number
of
contribution
coming
out
out
from
the
community
like
the
next
release
would
include
a
few
patches
from
the
community
that
came
in
the
last
recycle
and
the
road
has
been
working
so
feel.
A
Free,
like
there
are
a
good
number
of
issues
we
have
recently
went
through
this
box
crop.
So
you
will
find
a
lot
of
issues
tagged
and
having
the
attack
so
feel
free
to
jump
in
and
do
join,
like
our
irc
matrix
or
the
email
list
to
know
more
about
or
no
no
more
about
the
project
or
just
like.
A
If
you
have
any
issues
or
if
you
want
to
contribute
or
do
feel
free
to
join
the
particular
matrix
channel,
and
we
have
a
good
documentation
around
like
on
a
flat
college
project
on
how
to
you
could
be
a
contributor
and
and
as
hilo
mentioned
about
the
sub
reform
that
would
be
going
out
us
throwing
out.
I
guess
soon
right.
A
Yeah
yeah
so
do
feel
free,
feel
free
to
join
like
fill
out
that
survey
form
and
then
again
this
is
the
release
planning
meeting
and
again
in
the
bye
weekly
cadence.
The
next
call
would
be
a
community
call,
there
would
be
would
be
having
spotlights
or
and
again
that
release
planning
during
in
the
community
calls
so
don't
forget
to
join
the
community.
Call
any
questions
from
from
folks.