►
From YouTube: Package weekly retro 2022-05-19
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
Hey
everyone:
this
is
the
weekly
package.
Retro
today
is
may
19th,
so
we'll
start
off
with
what
went
not
so
well
and
how
we
can
do
it
better.
A
I
was
working
on
many
things
in
many
different
directions,
so
I
wasn't
able
to
jump
into
the
15-1
work
as
soon
as
I
had
planned
on
initially
michelle
says
we
have
a
big
contribution
for
the
harbor
registry
and
unfortunately,
we
don't
have
capacity
to
review
now.
The
question
is
how
to
prioritize
between
all
the
big
contributions
that
we
also
have
pending.
B
So
this
week
we
have
bad
luck
around
the
merge
deployment
and
ongoing
incidents
for
the
for
a
couple
of
rails.
Mrs,
so
we
end
up
having
to
wait
more
than
one
full
day
for
them
to
arrive,
and
then
they
arrive
at
exactly
the
same
time.
So
we
couldn't
really
tell
them
apart,
which
one
causes
the
truck
put
to
go
up,
that
much
yeah.
That
was
it
really.
C
Yeah
I
felt
torn
between
the
migration,
like
focusing
all
the
energy
on
that,
and
I
guess
some
offline
garbage
collection
stuff.
That's
coming
in
it's
it's
very
hard
to
prioritize
that,
especially
with
the
time
it
takes
in
this
and
the
things
like
that
I'll
read
from
michelle
who's,
not
here,
she
has
seen
several
u.s
community
contributions
in
the
week
and
rahul
has
been
very
active
in
reviewing
them.
C
She
also
feels,
like
she
learned
to
turn
this
week
and
thanks
everyone
for
your
patience
and
explaining
things
to
her.
Also
also
she's,
changing
the
weekly
update
to
3p
people
process
product
and
it
took
her
about
half
today
to
do.
A
A
There's
a
bug
that
was
identified
with
being
cure
this
week
and
there's
one
of
the
stranger
bugs
that
I've
ever
investigated,
where,
like
the
logic
within
postgres,
was
miscalculating
how
to
correctly
perform
a
query.
So
it's
kind
of
fun
to
find
a
solution
and
dig
into
that
and
see
it
work
and
also
resolve
infor
related
concern
that
had
come
up.