►
From YouTube: Flatcar Container Linux release planning 2022-08-23
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
A
Yeah
so
I'll
just
go
with
a,
we
have
a
small
idea,
so
we
can
do
a
round
of
introduction,
so
hi,
I'm
san.
I
work
with
the
flat
card
team.
I
primarily
look
into
the
releases
part
of
things
and
other
than
that.
I've
been
working
on
a
couple
of
the
package
upgrade
these
days
over
to
dongsu.
C
Hi,
my
name
is
christine,
I'm
also
a
part
of
the
flat
car
team.
At
microsoft,
we
will
be
working
on
keeping
the
flat
car
up
to
date
as
much
as
possible.
Yeah.
D
I'm
the
engineering
manager
of
the
flat
card
team,
so
I'm
trying
to
help
my
folks
to
succeed,
also
I'm
standing
for
danielle
today.
So
I
was
one
pressing
the
go
live
button,
so
we
have
youtube
stream
and
youtube
recording
over
to
mike
hi.
I'm.
A
Thank
you!
So
that's!
I
guess
every
one
of
us
yeah
so
I'll
go
ahead
and
share
my
screen
to
start
off
with
the
release
planning.
Sorry,
I
forgot
to
make
the
slides
going
after
two
iterations
and
I
forgot
that
we
had
slides
so
I'll.
Try
to
jump
on
to
the
release
planning
board.
A
A
So
I
hope
we
could
start
off
the
release
bills
on
friday
so
that
we
can
get
the
release
out,
probably
on
monday
or
tuesday,
and
talking
off
the
how
it
goes
so
we
have
like
fame
going
in.
We
have,
as
usual,
the
updates
for
the
continuity
and
the
series
that
he
was
going
in
and
the
latest
version
of
gurus.
A
A
A
C
Not
really
because
what
what
actually
happened
is
that
village
became
stable,
so
all
I
did
is
I
updated
that
delivered
you
built
to
remove
the
keywords,
but
you
will.
We
will
still
need
to
put
up
new
other
keywords
for
the
r3
okay.
So
it's
still,
it's
still
not
updated.
In
my
my
request.
A
C
A
Yes,
so
it
has
the
pass,
so
I
have
created
the
branch
and
test
it
and
update.
Similarly,
with
the
intel
microcode
working
on
the
shadow
one
and
the
system,
d251
is
getting
a
bit
delayed,
we'll
try
to
get
it
by
the
next
release,
but
I
don't
think
we
can
watch
this
in
the
current
one.
A
B
C
A
Yeah,
so
this
is
primarily
like,
so
this
is
a
donkey
updated
and
we
usually
update
it
manually
and
we
take
over
so
brand
items
are
the
ones
we
are
planning
over
to
head
on
next
and
then
we
just
assign
the
tag
on
who
is
working
on
which
package
and
then
backlog
are
the
ones.
We
probably
would
look
into
the
next
set
of
releases
so
yeah.
So
that's
how
it
goes,
and
then
we
have
the
triage,
which
is.
C
A
A
Okay,
so
yeah,
so
this
is
how
it
looks.
So
we
should
be
good
for
this
week's
by
friday
and
from
the
pr
side
we
had
a
couple
of
openstack
videos
getting
merged
where.
B
A
A
Okay,
so
matthew
is
not
on
this
call,
but
he
particularly
mentioned
about
this
issue,
which
would
be
landing
in
the
next
one
in
the
next
release.
So
this
got
more
so
he
updated
on
the
on
the
on
the
matrix
channel,
so
anything
other
than
that
that
folks,
you
want
to
point
out
for
the
next
release
or
like.
If
things
goes
right,
we
probably
would
start
the
builds
on
friday.
Anything
that
would
not
get
much
by
friday.
You
think
any
work.
B
So,
two
weeks
ago
we
updated
image
sub
key
image,
update
sub
key
and
right
yeah.
Probably
we
need
to
release
also
fts
2021
or
okay.
A
I'll
check
the
option.
The
current
one
is
27
2091.
A
Yeah,
so
for
the
next
we
we
should
plan
for
the
august,
the
26th
of
september.
So
we
have,
we
would
have
a
new
alpha.
We
would
do
a
new
beta
and
I'm
not
sure
if
we
should
do
a
news
table.
Do
you
think
we
should
push
a
new
stable
because
we
would
be
like
four
weeks
in
so.
Do
you
think
we
should
cut
out
it
spend
some
time?
D
D
If
we
wait
one
more
release
and
cut
the
stable
in
october,
we
might
have,
we
might
have
a
chance
for
systemd
251,
going
stable
right.
B
D
Yeah
but
since
it's
not
in
the
current
round
of
releases
like
a
future
major
new
beta
in
in.
A
Yeah,
so
the
thing
is
that,
with
four
weeks
we
earlier
had
a
cadence
of
two
weeks.
Now
it's
four,
so
I
think,
like
the
distance,
has
increased
a
bit,
so
maybe
we
should
go
of
one
stable.
It's
been
some
time.
We
have
that's.
A
It's
july
to
october,
so
I
mean
july
talked
about
it.
So
if
you
jump.
D
That's
yeah,
that's
true:
what's
the
progress
and
the
missing
pieces
of
the
of
the
new
ci
pipeline,
do
we
have
a
good
idea
when
we
could
start
using
it
for
automated
builds,
so
we
can
reduce
the
the
manual
effort
for
releases.
C
So,
on
my
side,
sorry
for
cutting
it
on
my
side,
it's
there's
still
no
support
for
building
the
old,
lps
and
then
pipeline,
which
is.
A
C
B
Yeah,
the
dev
container
test
is
one
issue
here
in
the
like,
planned
to-do
list
I
see
and
the
other
one
is
publishing
the
sdk
container
like
automatically
to
the
container
registry.
D
C
Yeah,
but
still
like
the
work
on
releasing
or
supporting
two
lts
in
power
hours,
you
need
it
because
at
some
point
you
are
going
to
have
lts,
2022
and
lts
2023.
So
some
drama.
D
Yeah,
I
think
that's
that
that
sounds
good.
D
Okay,
give
us
a
month
to
iron
out
the
last
sprinkles,
so
the
the
fully
automating
sdk,
publishing
and
and
syncing
from
from
the
build
cache
to
the
origin
servers
should
be
relatively
low
hanging
fruits.
So
I
would
say
few
days.
D
I
mean
thinking
about
it,
but
you
have
a
decay
container,
actually
yeah,
I'm
I'm
not
trying
to
feature
creep,
but
thinking
about
it
now
having
the
sdk
container
around,
we
could
even
go
as
far
as
invest
investigating
the
the
overall
concept
of
the
death
container
and
whether
it
can
be
replaced.
A
Another
thing
I
wanted
to
mention
dog
super
you
can
probably
suggest,
should
we
move
to
m9.
B
A
Should
we
update
right
now
we
are
on
we
made
so
should
we
update
to
cam
nine.
B
Okay,
yeah,
okay,.
A
Then
then,
then
look
into
the
pr
for
updating
to
m9
because
they
are
having
a
lot
of
bunch
of
cvs
that
gets
fixed
there.
So.
A
Anything
any
else,
any
anything
else
to
add
any
any
more
questions.
A
D
A
D
Mentioned
it,
this
is
great
work
and
I
think
giving
it
visibility
would
be
what
people
said.
A
Okay,
I'll
then
add
it
to
the
add
it
to
the
9
26
of
september
board
column
yeah.
Well,
thanks
anything
else,
any
any
points
that
you
would
like
to
share.
A
If
nothing,
then
we
can
probably
end
the
meeting
here.
Thank
you
all
for
joining
have
a
great
rest
of
the
day
and
see
ya
bye.