►
From YouTube: Release Management APAC Sync - 2020-06-01
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
A
B
A
C
A
B
I
guess
from
last
week
and
running
into
this
week,
is
being
the
security
issue
that
I
was
working
on
about
the
stealing
the
someone's
cookies
buy
a
domain.
That's
like
a
long
conversation
I,
don't
know
if
you,
if
you
read
it,
but
on
the
MRI
that
were
like
a
few
concerns.
Basically
and
backwards-compatibility
like
with
this
fix.
It
would
break
things
alright,
so
well,
I've
had
a
suggestion
in
it.
I'm
gonna
go
back
to
it.
B
B
Yeah
and
other
than
that
I've
been
working
on
my
assignations
for
the
free
milestone,
improving
the
lab
kit,
improving
the
pages
linter
configuration
as
well.
That's
going
well,
there's
another
mi
there
for
review
and
I
think
that's
pretty
much
it
from
what
I'm
doing
right
now.
My
plan
is
to
try
to
finish
the
security
issue
as
soon
as
I
can,
because
it's
a
bit
yeah.
B
A
A
B
A
B
A
C
Well,
I'm
different.
The
last
time
we
talked,
we
caused
my
initial
most
requests
on
the
secret
syntactical.
The
discussion,
and
the
good
thing
is
that
we
now
have
a
plan.
It
looks
like
everyone
agree,
so
I
just
need
to
implement
it,
which
is
happening
faster
than
my
original
was
request,
because
I
still
have
all
that
much
that
I
can't
around
hard
work.
C
So
I'm
going
to
push
even
like
one
of
the
Mercer
quizzes
assigned
for
the
do,
I
need
to
pink
jeju,
samdasoo
and
because
it's
being
for
a
couple
of
days
and
I
got
some
feedback
on
the
other
cameo,
so
I
still
hope.
We
may
manage
to
actually
not
be
delayed
over
like
in
terms
of
releases
but
we'll
see
because
it's
too
heavy
to
go
through
review
like
so.
C
No,
that's
I
was
about
to
say
just
unless
you
have
something
else
for
me
that
you
want
me
to
look
at
that.
That's
my
plan
and
I
haven't
heard
anything
from
the
from
Thomas
and
the
runner
team
out.
Yet
I'll
get
back
to
them
cost
because
we
changed
the
syntax.
We
may
now
change
the
actual
structure
of
the
response
returned
from
the
API
to
the
runner
and
I'll
check
with
him.
Is
it
fine
cause?
We
can
actually
make
the
normal
ever
syntax.
We
can
still
keep
told
dot,
Delta
API
response
trouble.
C
C
A
A
A
Some
future
looking
priorities
and
we
all
talked
about
and
our
team
not
and
are
not
on
our
team
meeting
tomorrow,
but
the
team
meeting
next
week.
Just
we
have
a
bunch
of
features
in
13.3
and
13
at
4:00
and
13.5
that
are
around
supporting
just
group
level,
actions
for
release
and
that
being
a
part
of
the
CI
CD
workflow
I
also
hope
to
prioritize
our
object.
Storage
work
Jaime
so
that
we
can
get
that
research
completed
and
start
making
some
effort
toward
that
so
cause.
Hopefully
it's
like
in
13.4.
A
C
C
I
think
I
still
have
in
my
to-do
list
that
issue
I
think
you
asked
me
to
look
at
some.
Take
a
bow
or
just
research
on
see
like
see
our
variables
in
secret
and
how
we
can
like
improve
the
situation
there.
So
I
hope
I
at
least
get
like
couple
of
hours
to
think
about
it
in
and
post
something.
So
it
may
I've
changed
what
we're
gonna
do
in
the.
C
Releases
cause
it's
very
confusing
kaemark,
even
even
for
that
that
people
indeed
laughs,
we
constantly
talk
about
variables
as
secrets,
while
they're
like
actually
moving.
That
makes
them
secret
other
than
the
way
people
use
it
so
yeah.
We
should
try
to
improve
that
situation
and
I,
don't
think,
like
the
other
confusion
is
that
people
think
that
the
vote
is
the
ultimate
solution
that
will
solve
this
Wow
vehicles.
You
need
to
have
voted
to
start
using
it
and
we're
not
gonna
provide
both
anytime
soon,
if
ever
so,
we'll
try
to.
C
A
A
A
C
About
white
people
have
that
much
concern
like
who
can
see
them
in
the
UI
when,
eventually,
everyone
who
can
run
CI
pipeline
can
see
them
cause
at
the
end.
They
are
provided
to
the
job
so
like.
If
you
do
some
stuff,
you
can
like
find
find
those
secrets,
so
I
guess
the
the
level
of
Defense
there
is
that
it
goes
to
code
review
or
in
protected
environment
and
stuff
like
this,
but
there
are
I,
look
at
it
and
I
probably
have
question
cause.
C
B
C
B
A
A
We
have
to
build
a
generic
package
registry
first
before
we
can
extend
the
release
CLI
to
then
call
from
the
storage
that
we
create
so
I
would
say,
as
far
as
like
the
dogfooding
stuff,
typically
I've,
seen
it
take
a
couple
of
months
for
our
internal
organization
to
mobilize
and
consume
features
that
we
built.
So
we
made
everyone
aware
of
this
at
the
second
week
of
April,
I,
think
and
then
I
checked
in
in
May.
A
A
B
A
I
put
the
milestone
of
extend
the
release
node
for
animal
steps
in
13.2,
because
13.1
was
our
free
milestone,
but
Sean
just
moved
that
issue
into
13.1.
So
we
should
be
able
to
shift
that
which
means
that
me
that
should
mean
that
we
could
get
to
version
1
for
the
release
COI
in
13.2
I'm,
just
not
quite
sure,
on
the
go
side
like
your
site,
Jaime.
What
what
scope?
A
You
would
need
me
to
prioritize
so
right,
if
you
want
to
ping
me
on
specific
issues,
I
can
pull
them
in
appropriately
and
we
can
plan
them
again
like
this
is
where
I'm
kind
of
abstracted,
because
you're
the
Technical
Architect
of
the
release
CLI,
but
the
feature
functionality
that
the
customers
are
going
to
be
exposed
to
are
generating
a
release
from
the
mo
file.
So
if
there's
things
that
you
need
to
work
on
that
are
gonna
help
enable
that
13.3
goal
of
allowing
our
customers
generate
a
release
from
the
mo
file.
B
Yeah
I'll
go
I'll,
go
over
the
issues
under
release
Ala
itself,
but
it's
pretty
much
adding
support
to
uploading
files
yeah,
which
is,
if
we
go
with
the
assets
with
the
current
functionality,
it's
just
adding
assets
that
there
should
be
not
too
hot
and
maybe
a
few
more
improvement
so
that
we
have
in
the
list.
My
only
concern
is
the
review
cycle
again.
How
is
that
going
to
affect
if
we're,
depending
on
on
the
running
team
crowds.
C
C
B
A
Mean
I'm
gonna
I
just
realized
three
days
ago,
Shawn
made
a
comment
and
I
saw
that
you
liked
it
on
that
issue
that
I
have
scheduled
for
13.3
you,
given
our
time
zones
you'll
be
meeting
at
like
1:00
in
the
morning.
My
time
so
I
likely
will
not
be
making
that
meeting.
I've
tried
to
make
a
2
a.m.
with
craz
and
I
failed
miserably.
I
just
didn't
wake
up
so.
A
If
you
do
have
a
meeting
with
them,
please
please
just
feel
empowered
to
go
connect
with
him
and,
let
me
know
send
me
the
recording,
so
I
can
review
and
just
make
sure
I
have
all
the
scope
that
you
guys
need
the
the
customer
use
cases.
The
information
that
you
all
need,
but
I'm
gonna
come
in
on
this
issue
that
he
commented
on
that
you,
like
I'm,
just
making
sure
that
we
get
everybody
on
the
same
page.
A
That
you'll
just
link
me
all
the
issues
that
are
relevant
to
schedule,
pre
13.3,
and
if
we
need
a
bump
out
this
assets
1
to
13
at
4:00,
to
accommodate
more
research.
We
can
totally
do
that.
But
also,
let
me
know
if
you
want
a
technical
evaluation
in
the
same
milestone
for
13.2
or
something
to
prepare
for
this.
Just
keep
me
posted
on
what
you
need:
okay,
yeah.
B
A
And
you
always
always
fill
in
power
to
meet
without
me,
and,
let
me
know
like
hey:
this
is
how
things
have
to
be
totally
once
you
all
do
know
as
fast
as
possible,
and
we
can
always
create
quality
shoes
for
addressing
edge
and
fringe
use
cases
that
aren't
necessarily
completely
addressed
in
your
initial
permutation.
Whatever
you
all
end
up,
doing
we're
all
flexible
here.
Okay,
all.
A
A
Okay,
perfect
awesome.
Well
let
me
know
if
you
need
anything
Jaime
I'm,
not
sure
if
you
saw
my
comment
that
I
made
to
sit
in
the
CEO
Channel
about
a
major
customer
saying
that
they
aren't
evaluating
one
of
our
biggest
competitors
anymore
and
I
want
to
let
you
know
that
it's
because
this
whole
Yambol
generation
of
releases
that
the
fact
that
we're
going
to
be
able
to
support
that
functionality
and
many
other
pieces
of
our
vision.
But
that
was
the
one
that
really
made
that
customer
feel
super
supportive.