►
From YouTube: Package quad planning 2021-11-23
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
Cool
and
then
prioritizing
and
planning
future
work
so
reviewing
the
triage
report,
I'm
not
too
familiar
with
the
idea
here.
If
anyone
else.
C
Yeah
so
michelle
is
michelle
is
mentioning
here,
a
flaky
test
which
is
regarding
a
conan
instant
package
test,
and
she
was
asking
if
to
take
some
time
to
work
on
this
in
the
future
milestones
and
then
quarantine
these
tests.
I
was
a
bit
confused
with
the
comment
on
an
issue
which
was
about
publish
and
install
content
packages
with
only
name
and
version
fix.
C
B
Yeah,
so
I'm
working
on
a
change
on
the
registry,
and
I
I
saw
that
the
whole
project
levels
back.
It's
all
going
time,
so
all
the
endpoints
of
the
project
level.
I
think,
if
I
recall
correctly,
it
has
to
do
something
with
uploads
or
test
ordering.
B
C
So
I
think
what
michel
means
here
is
like
to
schedule
fixing
those
issues
with
the
projects
level
endpoints
and
perhaps
try
to
schedule
that
for
the
for
the
upcoming
muscles,
I
think
that's
what
she
means.
A
I
think
we
should
get
them
scheduled.
Those
of
those
conan
tests
have
been
quarantined
for
many
months
now.
I
think
which
granted
we
haven't
had
much
changes
to
conan
recently,
so
there's
been
no
specific
reason
to
address
them,
but
now
that
we
are
making
more
changes.
B
B
For
additional
contacts,
so
the
whole
project
spec
is
parenting,
the
whole
spec
for
all
the
endpoints
and
in
addition,
the
upload
endpoints
are
quantized
and
those
endpoints
are
shared
between
the
project
level
and
the
instance
level.
So
the
whole
project
level
is
currently
and
skipped
and
on
the
instance
level,
only
the
upload
endpoints
are
skipped.
C
A
C
Have
the
next
item
yeah
just
to
probably
something
to
add
in
the
quad
planning
structure
the
the
keyway
failures
to
review,
because
some
of
them
are
actually
bugs
or
they
probably
need
just
some
investigation.
So
just
to
sort
of
talk
about
that,
and
if
we
can
schedule
the
efforts
we
have
a
few
of
them
already,
but
some
of
them
are
environment
related.
So
when
we
have
500
staging,
for
example,
but
some
others
are
being
addressed
at
the
moment
with
some
refactoring.
C
So
once
we
refactor
and
optimize
a
bit
our
tests,
they
are
supposed
to
go
away,
but
some
others,
like
I-
I
posted
here,
one
from
conan-
I'm
not
really
sure
about
that.
The
resolution
of
this
failure
and
probably
would
need
some
engineers
to
look
at
it.
C
Should
we
probably
consider
if
it's
to
close,
if
it's
to
continue
investigating
or
if
need
some
other
action.
A
I
can
revisit
it
looks
like
I
was
involved
in
some
investigation
previously
I'll
revisit
that
and
see
where
it
was
last
at
and
whether
or
not
we
can
continue
to
move
forward,
or
it
was
just
like
a
matter
of
scheduling
or
something
like
that
to
find
time
to
work
on
it
and
I'll
post.
An
update
in
that
specific
issue.
B
B
A
B
Makes
the
whole
development
around
qspx
more
difficult,
because
the
feedback
loop
is
run,
the
qa
spec
watch
it
fail
run
it
jdk,
stop
gdk
start
again,
wait
for
the
server
to
be
up
start
the
qa
spec
watch.
It
fail
start
over
again
and
it's
it's
too
random
to
be
usable.
So
it
would
be
better
if
we
can
have
like
a
stable
environment.
Staging
could
be
that
environment
and
we
just
like
take
the
modifications
on
the
qa
spec
and
run
them
against
that
environment.
C
I
yeah.
I
took
a
note
of
that
in
the
retrospective
and
basically
yesterday
I
left
a
note
on
the
on
the
weekly
meeting
about
giving
access
to
the
kiwi
votes,
because
that's
where
we
have
the
the
environment
variables.
I
was
a
bit
last
week.
I
was
a
bit
not
understanding
how
what's
the
procedure
in
quality,
when
someone
wants
to
enable
an
engineer
to
do
that,
apparently
there
isn't
one.
C
So
I
think
I
think
what
we're
gonna
do
is
that
we're
gonna
create
access
requests
for
for
the
interested
team
members
and
then
you
would
be
able
to
access
staging
and
then
run
this,
and
it
would
be
much
easier.
Also,
you
have
the
running
against
changi.
Imagine
that
you
are
actually
doing
some
code
changes
and
you
want
to
run
them
and
you
don't
want
to
run
them
in
the
jdk
you
still
would
have.
C
I'll
I'll
pick
you
helping
the
team
on
the
on
the
doc
on
the
access
request.
B
Yeah,
I
think
all
the
at
least
all
the
back-end
engineers
can
add
access
to
that
front-end
engineers
could
be
a
nice
bonus
too,
because
we
are
going
to
work
with
those
qa
specs
and
adding
more
examples
and
such,
and
we
can
even
be
that's
what
happened
to
me
last
week
I
was
in
qa
spec
incidents
and
like
we
need
to
work
on
them
quite
quickly
to
quickly
resolve
an
issue.
So
if
we
have
a
much
tighter
feedback,
hopefully
it
will
be
way
better.