►
From YouTube: OCI Weekly Discussion - 2023-07-06
B
Really
need
a
haircut,
and
this
was
Within
Reach.
C
D
No
worries,
I
think
we're
I
think
we're
getting
all
those
things
resolved.
I've
been
talking
to
ROM
in
slack
about
getting
zot
for
that
other
PR.
So.
C
Even
without
a
conformance
test
on
the
other
stuff,
I'm,
okay,
I
hesitate
to
say,
merge,
as
is
because
I
haven't
gone
through
the
whole
spec
yet,
but
the
conformance
itself
with
those
changes
in
there.
Those
were
my
big
concerns,
and
so
even
without
new
test
on
the
index
with
the
subject
in
there
it's
still
conformist.
We
still
have
something
we're
testing
for
so
it's
better.
Nothing
so
I
wouldn't
be
upset
about
merging
it,
as
is
right
now
as
an
RC.
A
C
We
just
I'm
I'm,
saying
things,
merge,
I,
shouldn't,
say,
merge
tag,
so
I
wouldn't
be
upset
about
tagging,
an
RC
without
merging.
What
is
this
436
custom
interrupts.
C
D
D
Right
can
we
can
we
just
do
the
actual
release
on
image
spec?
Is
there
any
I
was
reading
through
the
the
process
and
I
thought
that
there
was
supposed
to
be
a
certain
number
of
RCs
or,
like
a
certain
amount
of
time,
between
our
season
release
and
that's
only
for
majors,
and
it
feels
like
it's
a
major,
but
it's
actually
a
minor,
and
so
we
can
do
really
whatever
we
want.
C
So
that
I
say
no
I've
got
a
bunch
of
open
PR
sitting
out
there
for
that
one
and
I
think
we
want
to
I'd
like
to
see
us
get
distribution,
spec
and
sync
and
update
with
whatever
we've
got
an
image.
Spec
tested
and
whatnot
that'll,
be
my
preference.
I
want
to
see.
People
actually
use
this
for
a
little
bit
before
we
cut
out
ga.
C
I
guess
nothing
I
didn't
do
anything
in
the
Milestone
itself.
For
this
one,
I've
I
just
have
a
bunch
of
little
cleanup
things.
I
threw
in
there
last
week,
a
bunch
of
them
got
merged.
People
have
been
really
good
about
getting
stuff
immersion.
There
I'd
love
to
get
a
mark
down
later.
In
this
thing
before
we
get
a
release
and
that
just
requires
a
bunch
of
markdown.
D
F
Sorry,
yes,
so
if
I
understand
Brandon's
plan,
so
what
he's
saying
is:
do
the
opposite
release
first,
announce
let
the
Registries
Implement
RC
use
it
for
a
little
while
and
then
cut
the
gr
release.
Is
that
the
plan.
G
C
E
E
I
don't
know
what's
in
progress,
thank
you,
I
I,
I,
that's
kind
of
what
I
was
going
to
ask
is:
what
does
that
look
like?
We
have
internal
testing
going
on
and
I
think
are
relatively
happy
with
where
we're
at
we're
not
going
to
be
launching
this
publicly
until
it's
G8
and
I.
Think
there's
probably
other
registries
that
were
in
that
position.
C
For
me,
an
ideal
world
would
be
to
hear
a
thumbs
up
from
groups
like
yourself,
Google
Docker
Hub,
just
even
if
you
haven't
released
it
just
to
say
thumbs
up,
looks
good,
plus
I'd
like
to
see
distribution
itself
have
something
out
there.
Looking
functional
and
I'd
love
to
see
oras,
maybe
Scorpio
some
other
tools
like
that
crane
able
to
work
with
this
stuff
as
well.
D
D
C
D
I,
don't
I
I
mean
correct
me
if
I'm
wrong
I,
don't
think
the
reason
why
the
big
changes
were
made
was
because
someone
implemented
it.
It
was
more
of
philosophical
right,
like
am
I
wrong.
D
So
I've
said
enough,
so
I'll
stop
talking,
but
I
will
use
this
opportunity
to
share
with
everyone
here
that
I
have
a
child
impending
and
will
be
off
for
some
time
so
part
of
why
I've
been
pushing
is
for,
like
my
personal,
like
oh
please,
if
this
could
just
be
done
before
that
time
happens.
So
I,
don't
know
if
that
I
don't
know.
If
that
changes
anyone's
opinion.
D
For
my
personal
situation
but,
like
you
know,
I,
have
a
vote
on
one
of
the
one
of
the
releases
and
like
like
I'm,
not
sure
I
will
be
able
to
vote.
D
You
went
too
far,
no,
but
yeah
I,
just
you
know
just
to
share
like
not
only
do
I
I
do
think
it
should
be
released
now
because
it's
been
over
a
year
but
like
yeah,
that's
that's
just
given
the
full
disclosure
there
and
if
there's
a
way
for
me
to
like
proxy,
my
vote
to
someone
like
Jason
or
something
I
will
do
that.
But
yes
I
would
love
to
get
something
out
in
the
next
two
or
three
weeks.
F
If
I
can
say
something
here,
so
yeah
so
I
think,
let's
announce
an
Aussie
release
and
let
all
the
client
and
registry
tools
catch
up.
F
And
the
message
out
there
should
be
that
we
don't
expect
any
major
changes
until
GA
and
set
a
timeline,
maybe
30
days,
90
days
and
say
this
is
when
we'll
announce
the
ga.
That's
that's
I,
think
reasonable.
D
I
think
that's
reasonable,
I'm
talking
again
I
think
that's
reasonable,
but
we've
tried
to
do
that
in
the
past
and
didn't
do
that
but
yeah.
It
feels
like
it
I.
You
know
not
to
call
anyone
out
it.
H
So,
just
to
kind
of
get
out
of
this
issue
for
Emit
spec,
there's
no
issue
in
the
Milestone
there's
some
procedural
stuff
that
we
need
to
do
if
things
like,
linting
and
and
stuff
that
can
be
added
on
are
not
a
Blocker.
H
We
even
do
it
post
1.1,
because
technically
that's
not
affecting
implementations
or
or
it's
like
a
spec
cleanup,
but
if
you
can
get
them
in
quickly,
that's
fine,
but
at
least
having
them
in
the
Milestone,
so
that
we
give
clarity
as
to
why
we
are
not
cutting
a
ga
might
be
the
first
thing
that
we
can
do
for
image
back
for
distribution.
H
D
Your
would
you
vote
in
favor
of
that
if
it
were
cut.
C
I
believe
so
I
have
not
finished
looking
all
the
way
through
the
whole
spec
yet
again,
but
I
everything
I
think
that
was
a
concern.
There's
nothing
there
that
I
know
of
right.
Now.
That's
blocking
me
from
saying
yes,.
B
B
If
you'd,
like
it's
open
source,
I'm
I'm
happy
to
help.
D
Yeah
I
think
yeah
I
kind
of
think.
We
should
have
an
internal
implementation,
so
we
can
make
the
changes
in
Step,
but
I
think
we
can
wait
for
Zach.
D
Okay,
yeah
I
mean
it's
really.
We
just
need
a
container.
We
need
a
container
image
so
whatever
it
takes
to
get
like
a
release
out,
it
looks
like
you're
just
pushing
on
release.
H
I
think
the
folks
are
implementing
the
index.
Subject.
Graph.
Copyright
now
so
maybe
give
them
a
week
was
what
I
was
thinking.
Sorry
I
didn't
see
any
hands
up,
but
did
I
speak
over
anybody
nope
all
right?
Another
follow-up
was
there
was
a
message
in
the
chat
saying
that
do
we
do
a
release
in
90
days?
H
That's
approximately
three
months
time.
So
is
there
a
timeline
that
makes
people
happy
or
gets
people
upset
or
what
what's
the?
What's?
The
general
thinking
I
would
just
like
to
kind
of
like
get
some
feedback.
E
Sooner
than
90
days
ago,
I
don't
think
we're
getting
to
a
point
where
we're
making
the
the
changes
we
made
between
the
first
few,
our
seats
were
kind
of
substitute
I.
Don't
think,
there's
been
a
lot
of
discussion
of
making
more
of
those
kinds
of
changes,
so
this
feels
like
we're
sort
of
at
a
place
where
it's
you
know.
Some
people
would
like
to
see
conformance
tests.
Some
people
would
like
to
see
more
client
implementations,
but
we're
not
saying
hey
like
we
need
to
change
this
field,
so
I
think.
E
H
So
can
we
set
a
period
for
like
a
customer
comments
for
maybe
I
don't
know
somewhere
in
between
I'm,
okay,
even
one
month
to
six
weeks,
whatever
people
feel
like
and
CR
Azure
or
Docker?
Hub
can
say
that,
like
within
this
time,
if
you
haven't
given
any
comment,
we're
going
to
cut
a
piece
and
like
six
weeks
is
that
reasonable.
H
I'm
sure
people
want
it
shorter,
but
something
along
the
lines
where
people
can
come
back
from
vacation
also
right
so.
C
H
My
opinion
is
as
long
as
the
implementers
are
approving
it.
They
are
expected
to
support
it
right.
So
if
they
don't
release
this
implementation
is
up
to
them.
Maybe
they
decide
to
keep
it
fully
private,
but
as
long
as
we
have
feedback
from
people
who
are
implementing
it,
that
might
be
the
only
thing
I'm
holding
it
against.
H
If
you
don't
get
any
feedback
even
then,
we
should
just
decide
to
call
it
a
day
like
we've
done
our
work
here
and
give
people
at
least
some
amount
of
time
to
give
feedback
right
like
hold
at
least
if
they
at
least
say
hold
it's
okay,
but
if
they're
not
participating,
I,
don't
think
holding
the
rest
of
the
community
waiting
for
the
release
seems
to
be
the
right
thing
again:
I'm
not
going
to
use
Josh's
baby
as
an
example,
but
at
least
let's,
let's
make
sure
we
can
make
some
progress
here.
C
C
A
But
we
are
getting,
you
know,
pull
requests
into
containerdy,
for
example
for
Wazi.
You
know
wasm
implementations
with
orifice
that
sort
of
thing.
Interestingly
enough.
D
C
I'm
really
hoping
I
didn't
mess
up
anything
with
all
the
Ginkgo
dependencies
there,
because
that
was
a
bit
of
a
spaghetti
mess
to
try
to
sort
through
all
the
ginkgo
changes.
A
F
A
Yeah,
thanks
for
doing
the
work
I'll
hold
up
on
my
review
until
you
've
made
a
statement
in
this
new
PR.
C
Or
the
Milestone
I,
don't
think
so
other
than
implementations
outside
the
Milestone
thing
of
stuff
it'll
be
nice
to
get
the
markdown
lender
in
there
and
to
do
that
I'm
holding
off
I'm,
making
a
mega
PR
for
the
three
other
preceding
PRS.
That
was
doing
a
bunch
of
markdown
lint
kind
of
changes
in
there
individually
to
files
for
folks
get
a
chance
to
review
that
and
then
once
once,
people
can
review
that
I'll
do
1090
I'll!
Basically
update
that
with
cleaning
up
all
that
went
on
everything.
That's.
H
Okay,
left:
what
do
you?
What
are
you?
What
are
your
thoughts
on?
Maybe
if
you
create
an
issue
for
anybody
to
comment
on
for
implementation
per
se
like
I
would
like
to
have
the
at
least
I
can
ask
for
the
oras
folks
to
comment
on
that
right
and
maybe
reach
out
to
the
ACR
folks,
also
to
say:
okay,
they
don't
have
a
problem
when
they
are
ready.
H
I
know
that
they're
kind
of
working
on
it
right
now,
but
they're
not
ready
yet
so
yeah,
because
there's
nothing
tracking
I
mean
on
the
calls.
We
can
state
that
and
that
might
be
okay,
but
somebody
you
have
to
go
and
write
the
notes
back
at
least
have
an
open
issue.
Looking
for
feedback,
for
you
know,
implementations
to
cut
GA,
then
others
can
comment
on
that
issue.