►
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
I
think
that's
we
we've
got
customer
and
I
managed
to
get
update
releases
moved
over,
so
that
is
ready
to
go
as
new
releases
come
in
now
and
we've
converted
windows
to
just
be
a
regular
bubble
environment
instead
of
using
an
internal,
tooling
system
that
vmware
has
so
that
should
be
ready
to
move
over
now.
B
There
we
go
yeah,
I
I
think
that
was
the
last.
The
last
blocker
well
obviously,
we'd
have
to
move
it
over
and
see,
but
right,
yeah.
A
It's
okay,
speaking
of
that,
we're
still
seeing
issues
with
specific
work,
particularly
with
upgrades
it
seems,
but
it
seems
to
be
issues
with
compiled
cappy
releases.
A
We
think
it
was
isolated
to
a
particular
version
of
the
bionic
stem
cell,
because
we've
recompiled
everything
with
the
latest
verbic
stem
cell,
and
that
seems
to
solve
the
problem.
But
we
don't
really
understand
why
the
problem
is
happening
and
the
capri
team
doesn't
understand
why
the
problem's
happening.
A
C
Yeah,
so
we
saw
this
same
problem
at
sap
on
early
cloud
infrastructures
that
are
not
connected
to
the
internet
or
that
have
a
flaky
connection
to
the
internet.
So.
C
It
might
have
something
to
do
with
the
release
not
being
fully
self-contained
or
so,
and
I
think
this
was
also
what
that's
from
the
copy
team
changed,
that
they
updated
the
the
ruby
release
in
the
in
the
car
release.
So
the
bundling
stuff
but
yeah.
When,
when
you
say
it's
still
happening,
then
it
might
not
be
the
same.
A
Well,
so
so
the
thing
that
we're
seeing
that's
still
happening
is
the
upgrade
that
tries
to
upgrade
from
the
latest
release
is
stuck
on
the
latest
release.
So
it's
still
happening
with
the
older
stem
cell.
It's
not
happening
to
the
best
of
our
knowledge
with
the
newer
stem
cell,
but
we're
trying
to
decide
how
best
to
unblock
ourselves
whether
we
can
just
like
for
ci.
We
could
just
say
okay
well,
for
now,
don't
use
compiled
releases
and
that
will
allow
the
upgrade
to
go
through,
because
you
know
it
works
with
the
source
release.
A
The
problem
then
comes
that
I'm
sure
there
are
a
lot
of
users
that
are
using
compiled
releases
have
installed
this.
This
release,
another
effort
to
run
into
this
problem,
potentially
on
upgrade
or
have
already
run
into
this
problem,
and
I'm
not
sure
what
the
best
course
of
action
is
there
in
terms
of
unblocking
them,
because
they
obviously
can't
be
as
destructive
as
we
can
with
the
cia
environment.
B
C
B
A
A
A
After
that,
I
think
the
next
that
there
are
two
next
tracks
of
work,
that
we
need
to
focus
on.
One
is
switching
to
a
default
jammy
stem
cell
and
the
other
is
starting
to
move
the
ci
environments
into
the
working
group.
Tcp
project.
B
Yeah,
I
think
johan
already
outlined
the
plan
for
jammy
right.
It
was
we.
B
It
sounds
like
we're
pretty
much
ready
to
do
it.
He
said
six
days
ago,
we've
added
this
story
to
the
backlog
for
our
next
sprint,
starting
today,
so
I
sounds
like
sap
will
be
driving
that
or
at
least
the
folks
in
the
other
folks
in
the
working
group.
B
I
think
we
can
do
to
facilitate
that
is
maybe
get
the
update
releases
pipeline
unpaused,
although
before
we
unpause
that
maybe
we
should
cut
a
bionic
release
because
that'll
be
as
soon
as
we
unpause
it.
There's
going
to
be
a
barrage
of
updates,
I
imagine
blocking
off
our
pipeline
for
some
some
time.
C
A
B
B
Let
me
see,
I'm
not
looking
at
the
agenda,
so
if
there
is
something
on
the
agenda,
we
can
go
there,
but
I
had
some
other
stuff.
I
wanted
to
chat
about
no.
A
There's
there's
nothing
agenda-wise
so.
B
I
think
I
wanted
to
make
a
quick
proposal.
I
guess
it's
just
us
three,
so
it's
might
have
to
repeat
it
at
some
point,
but
we
currently
a
lot
of
users
use
the
cats
branch
that
is
tied
to
a
specific
cf
deployment
release
in
their
testing.
A
B
And
then
they
would
start
using
cats
v21.00
right
and
the
mechanism
for
making
that
branch
right
now
means
that
the
uses
it
uses
like
cats,
develop
cfd
develop,
so
there's
a
somewhat
high
chance
that
that
pipeline
is
actually
broken
whenever
we
cut
a
cfd
release
and
there's
been
three
times
in
the
last
four.
Whatever
months,
where
we've
cut
a
release,
cat's
pipeline
has
been
broken.
B
So
it
would
be
nice
to
change
the
mechanism
for
cutting
that
branch
to
be
somewhat
more
independent
from
whether
the
cat's
pipeline
is
currently
green
like
if
it.
If
we
cut
the
release,
maybe
we
have
an
element
of
the
cat's
pipeline.
That's
like
okay
grab.
The
latest
cf
release
grab
the
latest
grab,
whatever
we've
got
on
grab
the
latest
version
of
cats
and
like
at
least
cut
this
pipeline,
and
then
the
next
version
develop
goes
through.
We
can
update
that
branch
or
even
do
it
off
the
cfd
pipeline.
B
When
we
cut
a
release,
we
also
cut
whatever
version
of
cats,
we're
using
with
the
branch
cut
a
new
branch
off
of
whatever
version
of
cats
we
were
using
in
the
cfd
pipeline.
I
think
it's
release
candidate.
B
Yeah
that
would
be
at
least
we'd
have
the
branch
you
know
and
then,
if
the
cat's
pipeline
runs,
it
can
update
that
branch
with
whatever
develop.
Is
the
latest
developed
that
passes
that
it's
fine?
We
already
have
the
mechanism
in
the
cat's
pipeline
for
that
just
be
nice
to
get
ahead
of.
As
soon
as
we
cut
the
release,
we
also
cut
that
branch
so
that
people
who
have
that
test.
I.
A
Mean
at
that
point,
is
there
any?
Is
there
really
any
benefit
to
moving
the
branch
updating
the
branch
yeah,
and
maybe
we
just
stopped
doing
that
all
together.
B
A
A
B
B
I
could
make
an
issue
or
something
for
that
to
track
that,
and
then
we
don't
test
windows
stuff
for
cats
or
smoke
tests,
except
in
the
cfd
pipeline
is
the
other
thing
I
wanted
to
say.
B
Like
we
have
no
other
than
unit
tests,
which
are
argue
like
not
even
sure,
if
they're
being
run,
because
I
don't
know
if
we
have
the
windows
prefix,
that
like
makes
them
not
run
in
a
linux,
vm
the
we
definitely
don't,
run
cats
windows
except
in
cfd-
and
we
don't
run
ca
windows
smoke
tests
except
in
the
cfd
pipeline,
which
is
sort
of
strange.
A
A
I
mean
presumably
for
cats.
We'd
just
include
windows
as
a
suite
and
run
it
as
part
of
the
single
job.
True,
so
if
I
slow
it
down
a
bit,
it
would
slow
it
down
a
bit.
B
No,
I
mean
no
one's
complaining
so
far
about
this,
but
yeah
sort
of
weird
that
we
could
theoretically
cut
a
cat's
release
without
having
seen
it
test
any
of
the
windows
stuff.
A
B
Updated
them
fairly
recently
greg
reactivated
the
dotnet
app.
A
A
A
B
That's
pretty
much
all
I
had,
except
for
I
can
make
an
issue
for
that
as
well,
except
for
philip.
What
what's
the
deal
with
the
naming
convention
where
we
put
cf
at
the
beginning
of
all
of
our
and
all
of
the
environment,
urls.
B
Yes,
the
most
recent
cedric,
the
one,
the
the
most
recent
environment
we
created,
which
is
the
windows
one
which
we
created
in-
and
you
know
this,
which
was
an
sap
vmware
kind
of
collaboration
into
the
working
groups,
gcp
account
the
sap
folks
added
a
naming
convention
that
I've
never
seen
before,
which
was
like
a
monas
and
an
example.
B
It
was
like
cf,
not
cedric,
dot,
arb
working
group,
dot,
cf
dot
com-
I
just
sent
it
in
zoom,
so
that's
like
that's
not
the
actual
url,
but
that
cf
at
the
beginning
is
not
an
addition
that
I've
seen
before,
and
I
think
aftab
or
sven
told
me
that
that
was
the
regula,
the
normal
sap
way
of
designating
a
cf
environment.
C
C
B
C
A
Okay,
the
only
other
thing
I
can
think
of
is
just
that.
The
bosch
team
are,
I
think,
going
to
move
forward
with
their
part
of
the
work
to
make
the
terraform
templates
available
so
that
we
can
start
to
replace
bubble.
A
There's
nothing
that
we
need
to
do
at
this
point,
but
that
is
is
starting
to
to
gain
momentum,
so
that
will
be
coming
at
some
point
soon.
A
Correct
bubble
will
be,
will
be
archived
at
that
point
once
we
have
a
working
replacement
for
ourselves
and
in
the
the
concourse
tasks.
A
It's
so
outdated
in
terms
of
versions
of
things
like
terraform,
that
it
includes
and
there's
nobody
left,
that
has
a
deep
enough
understanding
of
of
its
architecture
to
be
able
to
maintain
it
properly,
and
so,
at
this
point,
we're
trying
to
find
the
right
solution
for
creating
environments
that
is
maintaining
is
more
easily
maintainable
by
the
different
working
groups,
so
that
we
can
support
what
we
need
to.
A
Unfortunately,
it
won't
be
a
nice
single
tool
that
does
everything
but
yeah
without
a
dedicated
team,
supporting
it
there's
just
no
way
to
to
keep
that
going.
A
That's
a
good
question.
I
need
to
find
the
I
I'm
assuming
there
will
be
a
github
issue
somewhere
for
the
bosch
team.
I
need
to
find
that
I
have
our
internal
vmware
tracking
ticket,
but
I
need
to
find
the
the
corresponding
open
source
issue
that
they're
working
from.
So
I
will
ask
ruben
for
that
and
I
publicized
that
once
I
found
it.