►
From YouTube: CAPI v1.5.1&v1.4.6 patch releasing meeting (29-08-2023)
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
A
A
We'll
be
following
the
release:
tasks,
documents
as
usual
and
yeah.
Let's
get
started,
and
also
one
more
note
and
this
meeting
is
recorded
and
later
will
be
uploaded
to
the
YouTube
channel
and
also
one
more
note.
We
follow
cncf
code
of
contact,
so
that
boils
down
to
basically
being
respectful
to
each
other
and
yeah.
Let's
get
started,
then
I'll
start
with.
A
C
A
A
A
A
Sorry
this
one
we
could
security
scan
that
run
yesterday
and
it
is
green
and
there
is
also
create
release.
Sorry,
not
this
one
I
think
this
one
weekly
release
test,
which
also
runs
three
hours
ago
and
that
screen
and
we
can
consider,
was
often
as
a
green
and
yeah.
We
are
now
with
the
first
item
next
to
the
cons
team.
A
D
Yeah
exactly
so,
they
were.
There
were
a
couple
things.
We
changed
the
area
for
for
one
of
the
PRS
that
was
already
that
was
already
in
this
change
log,
and
also
there
was
one
Blackboard
I
think
last
night
to
both
one
four
and
one
five
and
I
believe
also
some
dog
changes,
so
I
regenerated
and
I
added.
Whatever
was
the
diff.
A
Oh
thanks,
I'm
sharing
the
PRS
in
the
chat.
Please
take
a
look
things.
We
have
to
review
it
collectively
and
yeah
and
merge
it
and
this
time
I
think
everyone
is
aware
just
reminding
that
we'll
be
using
a
new
GitHub
automation
that,
like
for
the
first
time,
and
that
should
help
us
a
lot,
hopefully
with
pushing
a
tag,
triggering
jobs
and
so
on
and
so
forth.
But
for
that
we
have
the
first
merge
these
two
PRS
that
killer
opened.
A
E
A
A
A
E
F
A
G
E
So
if
it's
a
a
better
release
or
a
release,
candidates,
so
actually
they're
different,
so
better
release,
we
cut
the
release
tag
or
we
create
the
release
tag
from
the
main
branch.
There's
no
release
Branch,
yet
so
for
a
better
release.
It
just
uses
the
main
brush
to
create
and
push
the
tag
for
a
RC
candidate.
It
creates
a
release
Branch
if
there
isn't
one
already.
E
A
E
A
A
A
H
A
H
I
E
You
want
me
to
take
that
for
a
cat
sure,
so
the
release
artifacts
are
are
part
of
the
GitHub
action
in
order
to
create
a
draft
release.
So
once
the
release
artifacts
are
generated,
then
it
will
create
a
draft
release.
Those
artifacts
as
a
GitHub
release
artifacts.
So
that's
independent
of
the
project
in
parallel
we're
running
a
project
which
was
triggered
by
the
tag
getting
pushed,
and
that
is
pushing
the
container
images
to
the
staging
registry.
E
H
E
E
A
E
D
E
E
A
E
A
H
A
G
E
A
A
E
A
E
Yeah
yeah,
that's
good
I,
don't
know
what
this
gray
bar
is
here,
but
it
looks
like
it
was
there
before
and
other
release.
Notes
too,
so
probably
it's
normal
yeah
looks
good
and
then
we
have
the
assets.
So
this
is,
you
were
asking
earlier
about
the
artifacts
that
we're
generating.
So
those
are
the
artifacts
that
were
generated
they're
part
of
the
release
as
assets.
E
A
G
A
A
E
So
I
think,
since
they
moved
to
the
community
registry
everything's
taking
way
longer,
it
used
to
be
faster
and
there
were
some
improvements
to
make
it
a
bit
better.
But
it's
still
lower
overall,
because
I
think
when
they
first
merged
the
community
registry.
It
was
like
at
one
hour,
two
percent
images
and
now
it's
down
to
30
minutes,
but
still
and
cluster
API
is
pushing
like
three
different
images.
E
C
E
A
E
Yes,
but
I
think
for
image
pushes
jobs.
It's
like
a
standard,
because
it
it
does
things
in
the
like,
like
this
cluster
or
the
cluster
it
runs
in,
has
like
privileges,
so
you
can't
you're
not
allowed
to
modify
the
job
itself.
I
think
so.
You're
supposed
to
just
use
the
template
and
the
configuration
that
happens
on
the
project
side
is
mostly
done
in
this,
like
Cloud,
build
dot,
yaml
file,
that's
in
the
project,
so
in
Cappy
in
the
Cappy
repo
I
didn't
find
the
docs
for
this
I.
E
A
A
F
A
A
A
I
E
F
E
E
F
G
E
E
A
A
A
E
F
A
A
A
E
A
A
A
A
A
H
H
F
E
A
B
A
H
G
A
A
D
F
G
B
E
E
D
A
E
E
F
E
F
B
F
A
Yeah
to
do
that,
we
need
two
things:
we
have
to
open
a
PR
to
The,
Homebrew
Rebel
and
their
update
cluster
Capital
tag
and
revision
and,
as
explained
here
we'll
be
doing
or
we'll
be
opening
a
PR
only
for
latest
stack.
So,
for
example,
right
now
we
are
tagging
1.4.6
and
105.1,
and
actually
we
should
be
opening
a
PR
only
for
1.5.1,
which
is
not
there
yet.
A
So
we
should
hold
off
until
it's
there,
but
here
it
explains
already
everything
what
what
what
we
need
so
basically
tag
which
would
be
1.5.1
and
then
the
revision
where
it's
a
like
comment,
hash
of
the
attack,
but
that's
not
there
yet
because
python
one
is
not
there.
So
I
think
we
have
to
just
wait
if
I'm
not
mistaken,.