►
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).
B
This
is
still
in
the
inbox.
This
is
from
jamie,
where
someone
should
respond
on
it,
for
the
jason
and.
A
B
C
B
A
Oh
sorry,
or
is
it
oh
give
me
just
a
second.
B
A
A
B
So
we
just
want
to
go
because
it's
it's
if
you
are
familiar
with
the
the
bosh
code,
because
this
is
for
the
agent
where
we
basically
remove
all
the
deprecated
registry
apis.
C
B
From
the
agent,
so
nothing
should
break
that's
basically
what
yeah
it's
basically
what
it
should
do,
shouldn't
break
anything
so
yeah.
C
But
yeah
do
we
know,
is
it
what
we
right
now
is
assume
a
complete
change
already
or
do
we
know
there
are
still
parts
missing.
B
B
B
And
and
on
jeremy.
C
B
A
C
B
A
B
So
I
know
that
ruben
was
migrating
to
the
newer
newer
nets
service
so
that
we
are
using
upstream.
Yes,.
C
A
A
C
It's
about
the
changes
in
arguments
regarding
keyword,
arguments.
I
guess.
A
A
A
C
The
question
was
a
little
bit
about,
like
should,
should
this
become
a
template
for
similar
changes,
where
you
would
always
say
like
if
we
introduce
something
into
the
api
and
see
like
command,
but
we
might
add
information
when
it's
failing
that
the
director
version
is
not
correct
or
whether
it's
just
overkill
for
this
one
and
some
other
change
has
a
pleasure
to
think
about
such
as
such
a
point.
But
one
open
topic
from
my
perspective
was
to
at
least
add
it
to
the
docs
and
the
the
required
director
version.
Ncli
version.
B
Yeah,
so
that's
in
this
issue,
yeah
this
whole
conversation
about
it.
B
C
Story
now
and
yeah.
A
A
B
No,
it's
just
on
the
comments,
so
it
just
seems:
okay,
I'm
okay
with
merging
clutch
comments.
A
B
B
B
Okay,
that
was
it,
we
don't
have
anything
else.
What's
this.
B
C
B
We'll
see
where
I
could
have
could
not
be
used.
A
A
A
Have
a
short
talk
about
these
golang
version?
Collisions
you
see,
which
we
identified
on
all
landscapes
didn't
create
an
issue
for
that
right
now,
but
it
seemed
that
if
you
are
depending
on
bosch
packages
and
consuming
the
golden
release
from
there,
for
example,
in
your
release,
and
then
you
get
another
job
in
our
example
distributed
via
runtime
config.
That
is
as
well,
depending
on
the
same
golan
release
that
these
versions
used
inside
the
jobs
or
yeah
the
jobs,
reference,
different
golang
release
versions
and
then
cannot
be
deployed.
B
C
Yeah,
that's
exactly
the
problem,
so
if
you
have,
for
example,
the
vendor
package
1.17,
it
doesn't
contain
the
patch
level
right.
So
theoretically,
you
could
easily
bump.
But
when
you
call
ok,
2
releases,
which
both
use
this
package
but
have
a
different
patch
level
under
the
hood,
then
it
clashes
so.
C
For
example,
if
you
co-locate
by
a
runtime
config
bosch
dns
so
right
now
it's
not
happening
it's,
but
it
could
happen
that
at
some
point
in
time,
boston
s
runs
with
118,
3
or
4
whatever
and
some
other
deployment
users
also
the
118
package,
but
has
not
yet
updated.
For
example,
then
you
would
get
a
fingerprint
error
yeah,
let's
so,
if
it's
not
super
well
known
yet,
let's
create
that
issue.
First
matthias
and
then
maybe
have
a
discussion
when
reuben
is
back
or
maybe
joseph.
B
When
we
wanted
to
roll
back,
then
we
had
this
issues
with
the
fingerprint.