►
From YouTube: 2022 09 09 Platform SIG
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
Yes,
because,
yes,
we
removed
coal
a
few
weeks
ago,
of
course,
we'll
talk
about
java,
11,
java,
17
and
devops
world,
which
is
in
a
few
weeks.
From
now
mark.
It
looks
like
there
is
an
open
action
item
on
your
side.
B
A
Of
course,
no
hurry
no
worry
now
fold
the
preview
suffix
removal
from
gdk17
agent
images.
We
had
opened
three
pull
requests
which
have
been
no
polarquest
issues.
Sorry
and
somebody
that
came
out
of
the
blue
made
three
pull
requests
that
were
merged.
A
Yes,
a
new
contributor
woohoo,
that's
something
nice
thanks
a
lot,
whoever
you
maybe
I
forgot
the
name
on
the
computer.
Unfortunately,
anyway,
thanks
a
lot
now
yeah
container
repository
management
for
jenkins
agent
mark.
Could
you
tell
us
a
few
things
about
that?
Yeah.
B
So
the
the
struggle
here
is
that,
right
now
we
have,
we
have
many.
We
have
multiple
repositories
and
with
multiple
multiple
repositories
that
are
managing
multiple
container
images.
So
there
is
a
multiple
repositories
and
multiple
images
from
those
repositories
and,
with
the
multiple
contain
multiple
repositories,
it's
quite
difficult
to
do.
A
release
process
that
is
clean,
simple
and
comprehensible,
so
releases
are,
are
unnecessarily
complicated.
A
That
a
few
weeks,
a
month
ago,
when
I
tried
to
add
the
arm,
64
architecture
for
a
few
docker
images
and
frankly,
we
missed
some
things.
There
were
some
versions
missing
and
it
made
a
mess.
Yes,
I
totally
agree
it
is
too
complicated.
B
Right,
well,
and
and
and
the
stacking
and
the
layering
is,
is,
is
another
piece
now
we
probably
cannot
get
rid
of
any
of
the
layers
or
any
of
the
any
of
the
conceptual
blocks,
because
people
depend
upon
them
in
some
way
or
other.
However,
one
of
the
proposals
is
from
damien
du
portal
is
to
combine
the
repositories
into
a
single
repository
that
could
then
be
used
to
deliver
to
multiple
destinations.
B
However,
we've
got
to
do
more,
more
designing
and
more
planning
work
to
to
accomplish
it,
because
what
we
cannot
do
is
we
cannot
just
drop
support
for
the
existing
container
images
right.
They
people
expect
them
to
continue.
Simplifying
the
release
process
is
not
justification
to
drop
or
to
rename
labels.
We've
got
to
be
sure.
We
retain
compatibility,
of
course,
and
that
that's
really
it
then
there's
one
more
topic,
which
is
this
separate
repository
for
jenkins
agents
with
tools
installed
and
that
which.
A
B
Good
point
so
so
that
one
let's
talk
to
it
later,
then
it
just
it
is:
they
are
not
actively
maintained
and
many
of
the
agents.
Many
many
of
the
container
images
are
still
using
java
java
8.
B
A
B
A
Yes,
so
that
we
have
a
list
of
priorities
if
we
have
to
update
them.
B
A
A
B
Yeah,
so
I
think
it'll
be
a
topic
for
discussion
at
at
the
contributor
summit.
A
B
Yeah,
so
let's,
let's
just
plan
on
it,
I
don't
know
that
we
should
put
it
on
the
agenda,
but
rather
over
the
lunch
table
or
just
sitting
around,
we
can
talk
through
because
we'll
have
damian
there,
we'll
have
kim
jacom
there
I'll
be
there
bruno
you'll,
be
there.
We've
got
the
right
players
to
be
part
of
that
discussion.
A
Next
topic
is
docker
container
deprecation
for
the
bluish
and
container
we've
seen
lots
of
efforts
from
kevin,
for
example,
regarding
the
blue
ocean,
putting
message
just
about
everywhere.
Saying:
oh,
you
know
it
deprecated,
you
maybe
shouldn't
count
on
it,
but
that's
not
the
case
yet
for
the
darker
container.
B
Yeah
and
and
this
deprecation
really
it
there's
some
software
needed
here
right.
We
can
certainly
change
the
text
on
the
docker
hub
page.
The
challenge
is
most
people.
Don't
read
that
page
once
they've
got
the
container
working
they,
they
will
never
look
at
it
again
and
if
they
did
look
at
it
they
may
not
recognize
whatever
change
we
make.
So
then
the
question
is:
do
we
put
it
in
an
lts
change?
Log?
Do
we
add
it
to
jenkins.io
pages
and
then
the
bigger
question?
B
Do
we
do
something
like
a
jenkins
administrative
monitor
that
said
that
pops
up
and
says
you
are?
You
gives
you
a
warning
in
the
top
right
hand,
corner
of
the
jenkins
controller
and
when
they
click
it,
pops
up
a
nice
little
dialog
that
says
you
are
running
a
container
that
is
deprecated.
Please
make
plan
your
switch
to
this
other
container.
A
B
Actually,
I
think
these
are
something
that
we
can
handle
here
that
okay,
because
it's
all
part
of
what
I'd
call
the
platform
side.
So
for
me,
these
are
the
biggest
challenges
this
one.
It
means
someone
has
to
write
the
administrative
monitor
it's
a
little
bit
of
java
code
and
then
test
it
that
it
works
end
to
end
and
that
and
the
whatever
file
we're
using
to
make
the
decision
shall
we
show
it
is
only
in
the
blue
ocean
container
and
not
in
other
containers,
etc.
B
A
So
we
should
give
ourselves
a
task
to
have
a
look
at
that
java
code
zone,
I'm
okay,
to
contribute
to
that.
Even
if
I
don't
know
where
to
start,
but.
B
Yes,
well
so,
and
I'm
not
sure,
I'm
not
sure,
I'm
ready
to
put
an
action
item
yet
as
much
as
knowing
that,
let's
keep
let's
discuss
it
and
begin
the
ideas
of
hey
here
are
the
kinds
of
things
we
think
should
be
done.
Maybe
maybe
the
answer
here
is-
and
maybe
this
is
a
valid
action
item-
is
create
an
issue
in
the
jenkins
packaging
repository
or
the
docker
see.
The
challenge
is
which
one,
maybe
it
will
create
an
issue
that
proposes
this?
B
A
Next
subject,
now
is
the
request
for
specific
tools
in
the
darker
images,
because,
yes,
we
had
some
tools
earlier
in
the
versions
go
for
example,
and
you
told
me
the
other
day
that
we
previously
all
also
had
some
other
tools
that
were
removed
from
images.
But
yes,
sometimes
we
have
to
do
some
cleanup
and
coal
is
not
strictly
necessary
in
our
docker
images.
So,
yes,
it's
gone.
A
We
feel
sorry
for
the
users
who
heavily
depend
on
it
that
the
way
it
is
from
what
I
understood
for
more
advanced
jenkins
users
is
yes,
these
image
are
there,
but
for
you
to
augment
them
to
change
them,
to
add
the
tool
that
you
need,
and
you
should
not
rely
on
them
to
do
everything
and
to
be
bundled
with
all
the
tools
that
you
need.
You
should
just
extend
these
images.
Am
I
right
mark.
B
That
that's
correct
and-
and
it's
it's
a
general
case
problem-
if
we,
if,
if
we
get
into
the
mode
of
oh,
we'll,
deliver
the
tools
you
need,
we
now
become
responsible
for
the
care
and
maintenance
of
those
tools
and
delivering
versions
of
those
tools
and
making
sure
that
when
a
security
issue
arises
in
those
tools
that
we
we
resolve,
that
security
issue,
it's
part
of
what
makes
it
so
challenging
to
have
these
images
like
were
mentioned
earlier,
with
separate
tools
in
them
right.
Well,
it's
got.
B
Yeah,
so
so
the
intent
is,
we
want
users
to
extend
from
our
base
image.
Now.
One
of
the
concerns
expressed
by
a
voice
in
that
in
that
thread
was
hey,
that's
complicated
and,
and
the
answer
is
yes,
it
is
container.
Management
is
non-trivial,
but
but
the
alternative
is
also
non-trivial
and
the
jenkins
project
just
doesn't
have
enough
people
to
maintain
everybody's
tooling
images.
A
I
could
maybe
add
a
reference
to
that
if
I
find
it
in
the
thread
to
help
the
users-
and
we
should
have
a
prepared
answer
for
all
the
users
who
will
face
the
same
kind
of
issues.
B
B
I
don't
know
that
there's
a
tutorial
that
shows
how
to
do
it,
but
I
do
know
that
it's
there
and-
and
actually
this
is
a
candidate
for
somebody
who
could
ask
at
devops
world
in
the
ask
me
anything
sex
session
with
damian
de
portal
and
air
veil
or
and
ever
that
hey.
How
are
you
managing
your
doctor
images
and
why.
B
B
B
B
Great,
that's
it
for
java
11
for
me
yeah.
What
about
java
17
then
so,
and
there
it's
ongoing,
and
there
have
been
a
few
recent
reports
that
are
working
through,
but
in
general
working
quite
well
seems
to
be
working
quite
well.
The
the
jenkins
infrastructure
team
is
planning
to
put
one
or
more
of
their
machines.
A
Great-
and
it
is
what
it
is,
but
it's
still
working
for
me
on
a
daily
basis,
but
I
have
nothing
complicated,
but
I'm
happy
to
work
with
java
17.
Nonetheless,
cool
next
subject
is
devops
world.
In
orlando,
we
will
have
a
contributor
summit
presentation.
I
think
it's
on
the
tuesday.
Yes,
yes,
it
is,
and
some
people
from
aws
will
tell
us
about
how
to
use
ec2
instances
of
mac
os
to
be
able
to
build
easier,
more
easily
ios
and
mac
os
applications.
A
I
guess
it
won't
be
a
long
presentation,
but
I'm
sure
they
will
be
around
the
rest
of
the
day
so
that
we
can
discuss
with
them
in
their
books,
for
example,
or
I
think
that
for
the
contributor
summit
we
also
have
next
to
that,
a
booth
at
jenkins,
io
booth,
and
that
we
also
have
a
place
where
we
can
give
some
quick
talks
and
so
on.
A
So
maybe
they
could
also
interact
with
our
users
there,
but
anyway,
that's
a
good
thing
to
have
news
about
instances
of
macos
in
ec2,
because
my
experience
is
that
it
was
kind
of
difficult
and
pricey,
and
I
read
a
few
things
here
and
there
that
said
that
now
it's
easier
and
maybe
cheaper.
So
I
want
to
know
more
about
that
great.