►
From YouTube: SIG Release Bi-Weekly Meeting for 20220809
Description
SIG Release Bi-Weekly Meeting for 20220809
A
Hello
good
morning,
good
evening,
everyone
this
is
august
9th,
and
this
is
the
bi-weekly
release
sick
release
meeting.
I
will
be
your
host
today.
A
My
name
is
hello,
garcia
and
we
have
a
somewhat
light
agenda
today
and
I
I
will
be
hosting
today
so
before
we
start,
I
would
like
to
give
the
chance
to
anybody
who's
new
in
this
group
to
maybe
say
hi
and
and
if
you
want
to
share,
what's
what
your
interest
is
in
sick
release
or
what
your
goals
are
you
have
to
do
so
you
know
we
have
to
hear
you
out.
A
Okay.
So
let's
move
to
the
so
project
updates
and
the
first
item
I
see
in
the
agendas
in
release
engineer
for
mohamed.
I
don't
know
if
you
want
to
take
it
away.
B
Hi
there
so
I'm
working
on
the
gcr
ar
migration.
So
as
part
of
that,
we
need
to
speed
up
artifact
registry
registries
in
the
the
artifacts
production
project,
so
the
changes
have
been
improved
by
sickkids
in
first.
So
I
need
somebody
from
sick
release
to
say,
yeah,
we're
happy
with
all
these
new
registries
that
we're
gonna,
promote
images
too.
B
A
A
We
are
gonna
start
testing
promoting
images
not
just
to
the
usual
dual
container
registry
registries,
but
we
also
want
to
start
testing
the
promotion
of
images
from
the
staging
repositories
to
google
artifact
registry
and
the
change
that
mohamed
just
did
to
one
of
the
manifest
is
to
start
promoting
some
of
those
images
to
registries
in
the
new
artifact
registry
and
is:
is
it
only
the
the
change
for
the
for
the
manifest
or
is
there
other
guys.
B
The
change
is
both
certain
changes.
The
new
infrastructure
has
been
provisioned
and
then
the
other
changes
and
manifests
themselves.
A
A
Well,
the
so
we
have
to
take
into
account
the
time
it
takes
to
promote
the
images,
for
the
main
concern
would
be
the
kubernetes
releases
themselves,
so
the
smaller
projects
may
not
be
such
a
concern.
Currently,
we
are
promoting
around.
A
C
A
Yeah
well,
some
of
the
so
the
the
promotions
take
place
in
parallel.
So
and
not
everything
is
related
to
just
scoping
out
the
images.
So,
for
example,
some
of
that
time
involves
verifying
existing
signatures
from
the
origin
registries
and
some
of
the
time
involved
in
promoting
involves
copying,
signing
images
and
then
copying
those
signatures
to
the
target
producers.
A
And
that
said,
it
would
be
once
we
have
this
experimental
project
in
place.
It
would
be
a
good
idea
to
do
a
copy
of
the
whole
set
of
a
corner
release
to
the
experimental
project
and
then
try
to
promote
that
and
see
if
it
can
handle
especially
in
time-
and
I
think
I
I
think
you
we
are-
we
will
be
able
to
to
make
it
in
the
so.
A
The
promoter
has
a
it
used
to
have
a
time
limit
of
two
hours,
and
I
think,
if
I'm
not
mistaken,
someone
increased
that
to
three
hours,
but
we
should
definitely
test
it
with
the
with
the
what
the
test
for
the
projectors.
A
So
I
I'm
not
aware
of
the
technical
requirements
of
that,
so
it's
a
is
a
proxy.
Does
a
proxy
require
all
of
them
in
place?
I
remember
there
being
some
concerns
about
latency
right.
If
not
all
the
registers
were
in
place
or.
C
A
B
Yeah,
so
the
with
regards
to
technical
requirements,
we
benefit
from
having
as
many
regions
as
possible,
but
we
may
be
limited
by
how
long
the
promotions
take.
So
from
the
case
infrastructure's
perspective,
we
won't
have
artificial
in
all
the
regions
that's
available,
but
that
might
be
limited
by
the
number
of
registries.
You're
gonna
promote
too
so
today's
21.
If
there's
new
regions
that
turn
up
tomorrow,
we
might
want
to
turn
them
on,
but
we'll
have
to
see
how
how
long
the
promotion
takes.
B
A
simple
example:
so
if
google
opens
a
new
region
in
africa
because
there
isn't
one
right
now,
it
would
be
very
useful
to
have
a
have
a
registry
available
there.
That's
an
example.
A
B
B
A
B
A
And
then
we
can,
if,
if
there
are
any
concerns
of
which
regions
we
can
take
that
discussion
in
parallel.
So
it
shouldn't
be
one
change
after
the
other,
especially,
I
think
to
make
an
intelligent
decision
on
which
regions
to
support
or
not.
We
have
to
consider
how
much
time
it
takes
to
replicate
to
them,
but
we
will
only
know
once
we
merge
the
manifest
okay.
B
A
I'll
leave
this
here.
If
anybody
wants
to
take
a
look
to
the
pr
I'll
I'll
jump
in
to
review
after
we're
done
with
the
call.
D
Yep
hi
everyone
just
give
a
brief
update
from
the
release
team.
We
passed
the
code
phrase
last
week
and
have
received
11
exceptions
so
far
and
we
have
approved
six
of
them
and
currently
all
of
them
are
being
tracked.
D
We
currently
have
14
enhancement
tracked
for
this
current
release
and
the
16
feature
blocks
registered
and
all
those
are
under
track.
So
today
we
are
going
to
have
the
test
phrase
and
rc
lyric
card,
together
with
doc,
ready
to
review,
deadline
and
start
final
draft
of
release
notes.
That's
your
working
on
the
release,
notes,
team,
still
working
on
major
themes
and
we
will
try
to
have
a
blog
post
draft
ready
after
the
major
themes
are
ready.
Yeah,
that's
the
major
updates.
A
All
right,
so
if
there
aren't
any
any
more
questions
for
the
release
team,
I
don't
see
any
items
on
the
open
discussion
so
far
and
if
no
one
has
any
anything
that
wants
to
discuss
over
the
course,
then
maybe
we
can
got
it
shirt
today
and
give
everybody
some
minutes
back
today.
B
A
B
I
think
veronica
seconded
ending
the
meeting.
A
Let's
work
now
well
we'll
be
around
for
the
release
cup
and
if
anything
comes
up
I
will
be
in
the
channel
and
if
there's
nothing
else,
we
can
see
everybody
next
tuesday,
all
right.