►
From YouTube: Flatcar Container Linux release planning 2022-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).
A
I
think
mike
might
have
been
pressing
the
wrong
button.
It's
it's
a
weird
button
design
with
the
approval
when
the
stream,
when
the
when
the
call
is
being
live,
streamed,
it
happened.
It
happened
to
me
as
well.
I
I
clicked
the
leave
button,
because
that
seemed
to
be
the
right
thing
from
the
interface
design.
A
No
criticism,
though,
hey
welcome
back
mike.
I.
C
D
Okay,
so
let
me
continue
with
the
meeting
so
yeah
welcome
to
everyone
who
joined
this
meeting.
This
is
black
car
relief
planning,
meeting
and
siam
started
creating
the
agenda,
but
he
could
not
make
it
unfortunately,
can
I
now
share
my
screen
for
that.
D
B
D
So
this
is
the
agenda
created
by
kion
today
and
yeah.
We
can
skip
the
introduction
at
the
moment
and
news
about
flag
car
releases
is
first
of
all.
Last
week
we
did
a
series
of
forward
release
releases
in
on
mostly
all
channels,
lts
2022,
table
beta
and
alpha.
D
However,
we
could
not
make
it
with
the
fps
2021,
the
old
channel
2605
37,
because
of
separate
ci
issues
anyways.
That
releases
went
well
relatively
well
until
the
last
week.
D
However,
as
always
when
the
stable
major
version
has
changed,
I
mean
that
the
whole
big
changes
between
the
what
the
old,
stable
version
and
the
new
stable
version
became
live
in
many
most
users
work
workflows.
So
there
are
several
ongoing
issues
reported
in
the
recent
state,
for
example
the
network
reachability
issued
for
systemd
issues
and
so
on.
So
we
are
working
on
it.
D
Yeah,
jeremy
and
our
team
also
did
a
good
overview
over
the
ongoing
issues
regarding
systemd
250.
D
Please
have
a
look
and
yeah.
Hopefully
we
could
address
the
critical
issue
in
this
week
and
we
could
finish
roll
out
the
new
point
abilities,
including
the
stable
and
ideas
yeah,
but
it
could
be
next
week
if
we
do
not
manage
to
get
things
done
and
everything
and.
D
C
I
have
a
quick
question
so
with
these
fixes
is
this:
what's
the
general
release
process,
especially
around
the
dhcp
one,
does
this
go
through
the
whole
pipeline
again,
or
does
this
you
know?
Do
you
issue
hot
fixes,
batches?
What
what's
the
normal
release
cycle
like.
D
In
this
case,
this
is
the
bulk
or
regression,
so
we
should
be
able
to
have
fixed
release
so
lts
table
beta
alpha
so
pointless,
for
example,
stable,
32,
27
2.1.
That
should
be
okay.
A
In
general
for
bug
fixes,
it
runs
that
way
and
if
you
check
the
previous
stable
releases,
you'll
actually
see
patch
level
releases
for
most
of
the
stable
series.
A
It
just
happens
that
every
now
and
then
either
we
have
like
patch
level
bumps
of
packages
that
we
ingest
like
the
kernel,
or
we
have
bugs
that
we
fix,
and
then
in
this
case,
for
the
for
the
case
at
hand,
it
will
be
32
27
to
1
and
it's
relatively
certain
that
there
will
be
a
2-2
and
maybe
a
2-3,
even
because
they
will
have
a
pretty
long
long
lifetime
of
multiple
months.
D
The
next
topic
is,
as
I
mentioned,
we
did
not
release
the
old
channel,
which
is
2021
and
2605.31
because
of
the
ci
issue,
and
today
I
had
a
look
into
the
ci
failures
and
the
issue
is
actually
not
in
the
actual
code
itself,
but
in
our
hci
pipeline.
So
for
some
reason,
certain
cuba
dm
test
should
be
kept
for
this
new,
our
old
channel,
but
somehow
it's
not
good
and
yeah.
He
would
try
to
test
the
cube
adm.
D
You
know
california
flannel
test
and
it's
very
unfortunately,
so
I
think
we
can
mark
the
details
in
the
release,
notes
and
continue
with
the
religions
in
this
week.
So
is
there
any
opinion.
C
D
D
And
let
me
open
the
release
pad
planning
board
our
regular
release
planning
board
here.
So
the
next
alpha
is
planned
on
29th
august,
and
this.
D
This
is
just
a
preliminary
release
number.
So
if
we
do
a
half
pixels
in
this
way
and
in
between
this
period,
then
this
number
could
be
also
different.
D
Have
been
struggling
with
upgrading
pin,
so
let
me
have
a
look
into
that
in
this
week,
also
being
youtube
somehow
interesting
and
it
see,
I
failed
without
any
failure
messages,
it's
kind
of
material
and
we
need
to
debug
it
and
another
one
there
because
of
some
security
issues.
We
need
to
update
git
to
235.4.
D
D
Several
security
issues
and
need
to
be
addressed
in
the
next
version.
Also,
we
need
to
update
a
corner
to
the
new
point
of
release
to
be
able
to
address
the
corners
spectral,
active
execution,
replay
issue
and
zion
has
been
trying
to
update
the
certainty
to
a
newer
version.
However,
is
kind
of
dangerously
at
the
moment
because
of
this
md
250
version.
If
they've
had
a
lot
of
issues,
somehow
be
careful
about
that.
D
And
there
are
many
packages
to
be
updated
in
the
backlog,
so
if
you
are
interested
in
in
that
work
then
feel
free
to
jump
in.
C
Yeah
I
had
a
question.
I
posted
the
get
issue
in
chat
issue
735,
it's
about
a
amazon
cloud
watch
agent
package
request
for
it
I'm
just
curious
what
the
the
general
process
and
like
what
happens
with
these
types
of
package
requests.
Are
these
sort
of
things
the
sort
of
thing
that
gets
packaged
into
flat
car?
C
You
know,
since
this
is
an
amazon
specific
agent,
is
this
something
that
is
considered
on
the
cloud
provider
to
provide
a
package,
for
I
just
wasn't
sure
where
the,
where
the
line
of
you
know
responsibility
fell
for
this
kind
of
stuff.
C
A
Well,
actually,
it's
a
it's
a
perfect
spot
to
to
ask
here,
so
I
see
that
jeremy
did
a
quick
dive
on
that.
We
have,
he
even
found
an
e-build
that
we
could
ingest
and
integrate,
so
vendors
in
general
are
handled
in
a
very
specific
way
in
flat
car.
You
have
like
the
core
image
that
is
the
the
slash
usr
partition
where
all
of
the
operating
system
binaries
are
and
then
for
each
of
the
vendor
images
you
have
add-ons
and
those
land
in
a
separate
partition.
A
So
this
is
not
part
of
the
of
the
of
the
core
flag
competition
and
unfortunately,
even
it
doesn't
even
get
updated.
Currently
we're
working
on
that.
It's
it's
on
the
on
the
roadmap.
A
So
once
you
provision
your
vendor
image,
the
oem
partition
is
never
touched
again
but,
as
I
said
in
the
future,
it
will
change
so
the
way
this
works
is
when
the
the
final
image
is
produced
and
a
base
image
has
been
built
already.
A
Then
the
the
whole
disk
layout
will
be
created
with
all
of
the
respective
partitions
and
then
in
the
oem
partition,
which
is
a
fixed
slot,
a
fixed
size.
All
of
the
respective
oem
tools
get
installed
so
for
the
aws
image.
These
are
different
tools,
then,
for
the
azure
image,
different
tools
for
the
qemo
image
and
so
on
and
so
on-
and
this
is
the
main
item
that
jeremy
is
raising
here
and
that
is:
does
it
fit
with
all
with
all
its
dependencies?
Does
it
fit
into
that
partition?
A
Do
we
need
to
change
the
partition
size
for
that
or
do
we
need
to
do
any
like
deeper
changes
to
the
way
flat
car
builds
if
it
if
the
evil
can
just
be
ingested,
and
basically
just
added
to
the
dependencies
of
the
aws
image
of
the
aws
vendor,
then
it
should
be
relatively
straightforward.
So
this
is
currently
sitting
and
waiting
for
an
engineer
to
to
be
picked
up.
A
Since
this
brings
me
into
some
of
the
more
interesting
things
on
the
flat
car
road
map,
so
we're
moving
away
from
the
whole
oem
partition
concept
in
the
future.
A
There's
a
great
new
feature
in
systemd
that
is
called
susex,
where
you
can
basically
have
a
layered,
composable
file
system
image,
and
that
is
also
read
only
which
is
kind
of
the
philosophy
in
flag
car
we're
looking
into
using
that
for
oem
tools
in
the
future
and
adding
oem
tools
updates,
while
we're
at
it
it's
a
few
months,
it's
a
few
months
out,
but
it's
definitely
one
of
the
bigger
chunks
that
we
want
to
tackle
next.
A
This
is
this
is
not
a
kind
of
a
roadblock
for
the
for
the
aws
thing
that
we're
looking
at
it's
just
a
like
kind
of
an
outlook
in
the
future.
But
if
anyone
wants
to
pick
up
the
aws
issue
and
add
that
specific
agent
to
flatcar
giving
the
restraints
that
jeremy
called
out
on
the
tickets,
that
is
absolutely
welcome.
Work.
B
Yeah
also,
I
wanted
to
to
add
a
quick
note
on
this
release.
It's
the
first
time
we
have
unstable
the
new
ignition
v3
support.
So
if
you
want
to
test
actually
it's
already
tested
in
alpha
beta,
but
it's
the
first
lensing
unstable,
so
feel
free
to
play
with
it.
A
Yeah,
so
if,
if
you
force
when
I
use
the
new
ignition
features
that
come
like
with
the
new
language
version,
here's
the
opportunity
ignition
version,
two
will
still
work.
This
is
something
we
do.
This
is
something
fedora
core
has
decided
not
to
do.
We
have
a
few
patches
on
top
of
our
upstream,
which
comes
from
fedora
core
s,
so
we
have
backwards
compatibility
to
the
old
ignition
version.