►
From YouTube: Flatcar Release Planning 2022-09-27
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
Hey
folks
welcome
to
the
release
planning
meeting
on
our
New
Jersey
server
we
switched
over
from
Zoom.
We
hope
this
makes
the
meeting
more
accessible
and
you'll
also
be
able
to
view
the
stream
and
a
recording
of
the
stream
right
in
the
metric
panel.
B
Okay,
this
is
our
release,
planning
meeting
notes,
so
I
think
so.
Everyone
here
is
already
in
the
car
team
and
no
need
to
do
the
introduction,
and
so
there
are
multiple
agendas.
So
the
first
one
is
how
about
how
do
we
do
the
future
releases
so
for
us
so
far
we
have
been
doing
so
once
for
all
releases
release
channels
so,
for
example,
stable
LPS
and
data
and
Alpha
and
all
in
the
same
day.
B
Now
we
are
planning
to
do
that
in
a
separate
way,
because
there
is
no
time
for
ordinary
users
to
deal
with
potential
regressions
when
the
stable
releases
have
Chrono
regulation.
So,
for
example,
we
have
an
in
progress
issue
with.
B
The
current
stable
release
and
30
to
27.2.2,
so
this
is
a
strange
issue
and
it
it's
about
the
randomly
process,
the
hang
on
iO
related
operations
and
we
are
still
working
on
investigation
so
before
releasing
the
new
cornered
0.5
F
1570
to
the
stable.
So
we
first
released
that
corner
into
the
five
data
and
after
that,
in
one
or
one
week
or
two
weeks,
we
get
back
a
corner
included
in
this
table
or
FTS.
That's
the
plan.
Is
it
true.
B
B
Okay,
so
open
our
release
boards.
So
this
is
our
release
board.
This
is
also
an
open
board,
so
anyone
could
have
a
look
in
anytime
and
the
current
release
in
this
week
would
be
only
about
verifying
data
channel.
So.
B
B
B
B
And
the
next
topic
is
about
how
what
kind
of
packages
we
updated
for
the
next
new
Alpha
version
and
yeah
there
are
many
packages
have
been
updated
in
the
last
few
weeks,
and
I
would
like
to
highlight
several
security
issues
like
goal
118
and
expat.
Library
2.9
and
Philip
I've
already
want
to
talk
to
R3
yeah.
Those
have
been
relatively
critical
issues
and
we
have
been
dating
the
packages
yeah
thanks
for
that.
Just
wanted.
B
B
Okay,
then,
the
our.
B
Stop
sharing
and
also
Outlet
tilo
talk
about
the
new
pipeline.
A
Yeah
cool
thanks,
so
we've
been
working
in
the
in
the
engine
room
under
the
hood
for
for
some
time
on
operationalizing
a
new
CI
pipeline
that
will
improve
the
the
build
experience
a
lot.
This
doesn't
affect
you
when
you're
a
user,
but
it
will
help
us
and
the
team
to
do
some
more
heavy
lifting
in
the
future.
A
The
new
CI
pipeline
is
based
on
the
container
SDK,
while
the
previous
pipeline
was
based
on
the
Legacy
cork
SDK,
the
new
pipeline
is
meant
to
be
stateless
insofar
as
that
you
shouldn't
need
any
parameterization
to
reproduce
any
of
the
builds
that
we've
been
doing.
So
the
idea
is
that
you
check
out
the
scripts
repo
which
has
all
of
the
e-build
repos
as
GitHub
modules
and
basically
with
a
single
check
out
and
with
the
call
of
a
build
script
without
any
options,
you'll
be
able
to
do
to
reproduce
the
build.
A
This
has
been
done
for
our
night
least
for
quite
some
time
now,
and
we
think
we
can
move
the
whole
thing
into
production.
So
that's
that's!
What's
going
to
happen,
the
old
pipeline
will
be
phased
out
iteratively
after
that
and
we'll
we'll
focus
on
the
new
pipeline
entirely.
This
will
the
builds.
This
will
make
the
builds
a
lot
more
reproducible
and
we're
really
looking
forward
on
basically
building
on
that
Foundation
and
using
this
new
freedom
to
do
some
some
crazy
in
the
future.
B
Okay,
thanks
and
the
next
item
is
about
but
yeah.
We,
as
we
already
mentioned
that
next
release
would
be
four
weeks
later
and
but
they
are
stable
would
be
in
two
weeks
and
there
is
a
plan
to
move
back
to
two
weeks.
Cadence.
So
cyan
can
you
say.
C
Something
about
them
sure
yeah,
so
so
next
release
would
happen
on
25th
October.
We
are
working
on
the
new
pipeline,
so
we
would.
We
might
get
some
hiccups,
so
I
guess
those
things
would
Iron
Out
by
24th
of
October
and
with
this
iteration
with
the
new
IL,
with
the
new
pipeline
in
place,
the
load
will
come
down,
which
happens,
usually
happen
during
the
previous.
C
So
it
would
be
a
good
time
to
move
back
to
the
two
weeks,
okay
days
again,
because
we
have
worked
a
bit
on
the
automation
side.
So
a
lot
of
things
have
automated
in
the
last
few
weeks,
so
we'll
move
back
to
the
curtains
of
releasing
tractor
in
every
two
weeks.
Yeah
and
I'll
just
go
on
to
the
next
point.
C
So
right
now
the
planning
was
primarily
targeted
towards
the
next
release,
which
is
which
we
are
right
now
in
progress
and
the
planning
for
the
next
one
would
start
on
the
next
Community
call
so
that
we
start
falling
into
that
two
weeks.
We
are
planning
students
again
and
we'll
do
all
those
two
releases
planning
again
like
how
we
used
to
do
it
again.
We
are
basically
going
back
to
planning
like
we
used
to
do
at
earlier.
Then
we
had
two
weeks.
D
Yeah,
so
we
would
Branch
the
new
Alpha
and
creates
a
new
Beta
release
this
evening
or
yes,.
B
D
Yeah
I
have
some
Maybe
not
really
last
Memphis
fixes
but
communities
to
adding
something
to
download
from
the
mirror
server,
and
not
only
from
bin
cache
and
yeah.
So
maybe
that
would
be
coming
in
and
I
also
found
that
we
don't
have
something
to
make
sure
that
we
use
the
latest
container
image
available.
D
For
example,
if
we
build
the
release
now
and
then
we
have
some
fixes
and
we
would
rebuild,
maybe
it
uses
a
stale
image
depending
on
which
worker
it's
scheduled
on.
So
that's
something
that
I
didn't
test
yet
so
I
wouldn't
merge
it
now,
but
yeah.
Maybe
we
could
have
a
look
out
if
we
have
a
rebuilds
release.
Maybe
that
could
be
back
ported.