►
From YouTube: Keptn Refinement Meeting - May 2, 2023
Description
Meeting notes: https://docs.google.com/document/d/10Fig1eYFZ9iQFSYWkz0c4eTwzgJiPtQI5IsczbvLsuE/edit
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
A
Let's
start
with
the
first
one
in
the
list,
which
is
from
Florian
about
improving
the
error
message
that
we
provide
in
this
class.
This
was
also
notice
during
kubecon,
while
we
were
presenting
the
klt
in
the
booth
and
it's
a
great
thing
to
polish
So.
Currently,
the
problem
is
here
when
we
report
an
evaluation
that
failed
in
the
trace.
We
don't
say
why
we
are
missing
what
was
the
target
for
this
value
and
we
just
have
to
improve
the
event
in
the
span.
Basically,.
A
A
Yeah,
okay,
so
we
can
maybe
have
it
even
for
0.8
perfect.
Thank
you
flow.
Then,
following
up,
we
have
a
ticket
from
Meg
more
an
epic
they're,
not
tickets,
where
the
goal
is
to
improve
the
documentation,
in
particular
the
getting
started
guide
with
three
different
topics:
the
one
that
we
highlight
during
our
coupon
talks.
C
C
The
deadline
is
to
have
them
done
by
the
middle
of
this
week,
which
is
not
going
to
happen,
but
I
have
a
good
draft,
we're
off
to
a
good
start
and
I
just
wanted
to
give
people
a
heads
up
that
we'll
have
to
Giovanni
will
have
to
figure
out
release
issues
ETC,
but
we're
might
as
well
get
them
up
and
I
just
wanted
everybody
to
know
that
this
was
going
on
and
it's
intensive
and
Etc
yeah.
A
C
C
C
I've
got
I'm,
calling
them
pre-alphas
right
now,
but
it's
not
going
to
take
me
real
long
to
get
them
into
shape.
From
here
now,
I've
got
I
had
to
get
some
clarification
from
Andy
and
I
had
to
wait
until
a
few
hours
ago
to
do
that,
but
so
we're
now
in
we're
in
good
shape
and
it's
not
as
terrible
task
as
I
had
thought.
It
was
going
to
be.
B
A
C
C
One
concern
is
that
I've
got
all
these
outstanding
PR's.
It
means
we're
going
to
have
a
lot
of
because
I
made
like
stub
pages.
C
So
we
have
a
lot
of
pages
that
don't
have
content
in
them,
because
the
content
is
over
here,
buried
in
PRS
that
the
the
content,
the
file
is
ready,
but
the
pr
is
a
mess
and
we
have
tons
of
extra
files
in
them.
Andre
just
figured
it
out
and
my
only
way
out,
I'm
going
to
have
to
copy
all
the
files
off
to
another
place,
blow
away
my
fork
and
then
recreate
all
the
PRS.
So
that's
not
going
to
happen
in
the
next
few
hours.
A
Oh
no
worries
okie
dokie,
so
maybe
a
heads
up
since
we
are
talking
about
the
release,
you
can
see
that
we
have
quite
a
lot
of
bug,
faces
and
dependency
bumps
and
other
stuff
and
a
lot
of
documentation.
So
thank
you
a
lot
to
put
more
effort
in
the
documentation.
A
If
you
have
three
Cycles
today
go
over
this
BR
test
it
out
the
07.1
and
make
sure
that
we
don't
have
any
last
moment
bugs
please
and
then,
if
you
test
everything
and
it's
fine
review,
it
approve
the
pr
IDE
and
with
that
I
think
we
are
done
with
the
tickets.
I
forgot
to
remove
the
labels.
Usually
it's
more!
It's
determines
that
perfect
and
yes,
we
don't
have
any
more
tickets,
so
say
thank
you
all
and
have
a
great
rest
of
your
day.