►
From YouTube: Flatcar Container Linux release planning 28th June 2022
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
Okay,
so
let's
zoom
in
a
bit
so
yeah,
so
we
just
did
a
new
release
with
alpha.
B
For
all
the
channels
alpha
beta,
stable,
the
older
lts,
as
well
as
the
newer
lts
things
are
pretty
smooth,
and
so,
with
the
new
release
out
last
week,
it's
good
to
target.
A
Newer
cadence
new
release
around
mid
of
july,
so
we
could
target
a
date
of
basically
the
11th
of
july.
So.
A
We
could
have
the
release
on
the
11th
of
july,
okay
going
forward.
So
one
thing
I
wanted
to
discuss
in
this
meeting
on
how
we
go
forward
because
we
folks
are
yeah,
so
we
folks
are
working
on
a
couple
of
like
issues
and
features,
so
I
was
wondering
like
what
would
be
a
good
path
forward
to
track
them
and
so
as
to
know
during
the
release
planning
like
how
things
are
progressing
any
thoughts
on
that.
A
Do
we
go
like
through
all
the
folks
and
get
a
status
update
on
which
issues
people
are
working
on
on.
B
Or
in
I
mean
yeah
so
upcoming
our
plan
primarily
like
so
what
we
see
blacklog
as
most
of
the
issues
that
are
there
in
the
flat
card
issue,
tracker
right
and
then,
as
we
move
forward,
we
put
it
into
planned
to
do
and
then,
when
we
start
working
on
them,
we
put
it
into
the.
A
In
progress
one
so
just
to
like
we
usually
technically,
we
should
target
the
plan
to
do.
But
if
you
see
the
plan
to
do
is
also
quite.
D
Huge,
so
I
was
just
wondering
like
if
we
should
start
targeting
like
issues
that
people
are
actively.
B
Working
on
so
that
folks
from
the
community
know
like
which
issues
are
worked
on
and
if
folks
need
help
or
if
folks.
A
I
think
we
can
use
the
team
load
dashboard
to
get
this
kind
of
information
all
right,
but
this
call
in
this
call
if
you
could,
because
this
call
is
the
like
the
placeholder
for
getting
the
updates
or
like
planning
the
next
release,
so
how
things
are
looking
so
that
we
start
to
interact
with
the
community
more.
What
do
you
think?
A
Because
in
the
earlier
so
with
the
previous
releases,
we
usually
give
a
tracking
like
we
usually
talk
about
how?
What
are
the
things
we
are
planning
for?
A
The
next
releases,
which
usually
covers
the
packages,
and
so
which
is
as
of
now
like
dogs
with
me,
are
working
on
a
couple
of
them
which
a
few
of
them
are
planned:
okay,
yeah,
a
few
of
them
are
planned
and
then,
but
we
could
talk
about
the
issues
that
we
are
working
on
or
we
are
planning
to
work
on
which
we
are
targeting
for
the
next
release.
A
Okay,
so
you
you
talk
about
the
package
updates,
not
issues
in
a
global
way
right
right
right,
so
I'm
talking,
if
you
can
talk
more
about
the
issues
or
like
how
things
looking
with
the
issues.
A
It's
primarily
it's
basically
like.
C
To
engage
more
folks
and
also
get
an
update
on
how
releases
look
so
that
we
can
look
back
to
the
if
someone
is
following
the
community.
A
This
community
calls
then
they
would
have
a
more
clear
picture
yeah.
So
maybe
it's
first
good
to
say
that
we
have
the
focus
right
now
on
the
build
automation,
and
that
means
we
are
setting
up
a
new
pipeline
to
build
the
releases
right
and
we
still
have
some
open
ends
there
that
we
need
to
wrap
up.
A
That's
why
we
have
so
many
plan
to
do
items
that
are
built,
yeah,
build
system
related
and
have
no
direct
yeah
feature
or
update
that
people
will
see
in
the
resulting
image,
but
it's
still
yeah
important
that
that's
why
we
are
working
on
this,
mostly
as
right
now
and
not
on
yeah
other
package
updates
and
so
on.
There
are
acute
drain.
Okay,
so
in
that
scenario
we
can
take
the
release
planning
as
like.
We
could
start
off
with
just
to
give
an
update.
C
On
the
things
that
we
are
working
on,
the
focus
items
that
are
getting
worked
on
and
how's
the
status
and
then
we
go
over
to.
A
The
package
updates
and
issues
if
some
issues
like
getting
worked
on
if
that
sounds
good,
this
is
primarily
for
the
future
cause.
Then
I'll,
prepare
a
bit
and
then
have
that
meeting
so
that
folks
participate
more
and
we
can
get
more
folks
on
board.
A
Sounds
good
yes,
cool,
okay,
so
yeah!
So,
as
kai
mentioned,
we
are
working
on
the
automation
pipelines,
so
these
don't
directly
affect
on
the
image,
but
they
do
make
the
pipeline,
which
we
use
to
release
flat
card
much
easier
and.
A
C
Part
but
yeah
that
if
you
are
looking
to
contribute,
these
are
the
issues
that
are
getting
worked
on
and
are
listed
in
the
planned.
A
To
do
section
so
feel
free
to
bring
us
on
the
matrix
channel
the
next
going
ahead.
As
I
talked,
we
would
have
the
releases
in
the
11th
of
july
mid
11th
of
july,
and
we
would
be
targeting
so
we
are
working
on
cso,
given
the
status.
Don's
is
working
on
the
glibc.
E
Update
and
it
includes
other
packages
as
well-
we
are
updating
the
vm
to
six
5066.
D
E
And
donkey
talked
a
bit
on
it
today,
so
I'm
trying
a
few
hacks
today
on
that
to
get
that
working
on
the
other
side
we
updated.
D
E
Pull
up
the
pull
the
gen
2
upstream
changes
into
so
that
would
get
the
new
update.
Sudo
is
also
clean
and
bend
notice
is
also
on,
like
all
tests
are
passing
so
I'll,
create
a.
A
A
Apps,
it
was
updated
in
me,
so
we
could
target
the
new
system
putting
on
the
new
systemd
into.
A
A
Actually,
it's
upgrade
so
I'll
try
to
debug
until
this
week
and
end
of
this
week,
and
if
still
there
is
some
remaining
issue,
then
I
will
just
merge
normal
packages
only
gdb
and
adcli
and
philipsie
next
releases
I'll.
Let
you
know
thanks
I'll
meet
you
bye.
A
So
I
would
expect
to
have
it
in
the
next
alpha.
It's
only
a
regular
update
of
s
linux
package.
We
are
currently
into
the
us,
but
it
needs
to
back
port
some
patches
into
the
tv
builds
but
yeah.
I
plan
to
do
that
for
the
next
for
the
next
release:
oh
yeah
yeah,
just
the
missing
parts
in
the
new
ci
pilot
build
pipeline
and
then
also
in
parallel.
A
F
F
Yeah,
I
have
a
quick
version
on
the
quick
question
on
the
on
the
timeline.
Does
it
make
sense
like
do
we
have
a
do?
We
have
a
reason
to
get
the
the
new
release
out
in
the
week
after
next,
because
they're
not
sure
we
just
discussed
to
kind
of
increase
the
gap
between
releases
to
a
month.
Is
there?
Is
there
any
pressing
update
that
needs
to
get
out.
C
That
gets
fixed
in
the
in
the
upcoming
ones.
So
that's
the
reason,
but
we
can
always
push
forward
into
for
four
to
the
four
weeks.
Basically
like
the
19th
18th
of
july.
E
Number
of
some
items
that
we
still
need
to
need
to
cover
sure
we
can
totally
then,
in
that
case,
push
it
to
18th
of
july
and
just
so
folks
know
that
we
to
the
folks
who
are
watching
it
later
we
are.
We
have
increased
the
cadence
to
four
weeks.
B
C
We
would
have
to
release
after
four
weeks,
so
that's
the
discussion,
yeah
dania,
anything
to
add,
or
we
can
probably
end
the
part.
E
Okay,
so
just
to
so
daniel,
we
are
having
the
box
smashing
day
on
8th
of
july
yeah
cool.
So
just
to
give
a
reminder
or
let
you
know
folks
that
we
are
having
bug
smashing
day
on
8th
of
july.
So
if
you,
if
you
folks,
are
around,
we
all
would
be
around.
C
On
the
matrix
channel
and
do
folks
feel
free
to
join
in.
D
Cool
yeah,
that's
all
for
this
week.
This
is
planning,
see
you
in
the
community
meeting.
I
got
one
more
thing.
I
get
one
more
thing.
Sorry
we
have
a.
We
have
a
few
connection
and
all
your
issues
on
on
my
end,
I'm
a
little
slower
today.
The
the
other
thing
we
were
considering
is
to
promote
the
beta
to
stable.
D
A
So
yeah
that's
correct,
so
we
would
promote
so
that
that
number
is
wrong,
but
I
was
planning
on
the
same
thing
because
around
the
timeline.
Speaking
of
the
timeline,
we
would
need
to
do
that
upgrade
because
it
has
been
some
time
now,
since
we
did
the
stable
upgrade
so
yeah,
so
I'll
update
those
version
in
there
yeah
thanks
for
pointing.
D
That
out
awesome
now
I
just
I
have
this
this
pr
in
the
in
the
current
radar
release
that's
sent
out,
which
is
the
the
arm
64.
D
The
arm
64
image-
and
I
just
got
news
from
from
mike
who's,
a
user
with
a
larger
cluster
and
they
tested.
A
A
Would
be
cool
if
that
could
be
lined
up
for
the
end
of
july,
release
sure
yeah,
so
I
think
it
makes
sense
to
do
both
beta
and
beta
and
the
upgrade
three
to.
A
Well,
thanks
everyone
from
joining,
see
you
everyone
in
the
next
community
meeting,
see
you
bye.