►
From YouTube: Kubernetes 1.20 Release Team Meeting 20200928
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
Welcome
everyone
to
the
monday
september,
28th
kubernetes
120,
release
meeting
this
meeting
is
covered
by
the
kubernetes
code
of
conduct.
So
please
be
excellent
to
one
another,
and
this
meeting
is
recorded
so
don't
say
anything
that
you
wouldn't
want
to
live
on
the
internet.
We
will
go
ahead
and
get
started
with
enhancements.
Today.
A
B
Hi
everybody,
this
is
kirsten
and
hassan's
lead,
I'm
I'm
marking
the
current
status
of
green
because
I
think
we're
pretty
it's
a
pretty
normal
state
to
be
in
like
where
we
are
given
in
the
release
and
the
release
cycle
and
instead
of
tracking
the
alpha
beta,
stable
right.
Now,
I'm
just
giving
a
rundown
of
like
the
categories
that
we
have,
so
we
have
25
tracked
enhancements
31
at
risk
37
on
track.
So
that's
people
who
said
we're
not
going
to
be
in
this
release:
14
deferred
pending
50
and
unresponsive
12..
B
So
pending
are
people
who
haven't
responded
but
have
been
responsive
in
recent
past
release
cycles
and
then
unresponsive
or
people
who
haven't
responded
in
this
release
cycle
yet
and
haven't
responded
in
like
multiple
release
cycles
and
both
the
pending
and
the
responsive
have
received
two
pings
each
along
with
the
email
that
was
sent
to
everybody
else.
So
I
might
get
a
couple
out
of
the
pending,
but
I'd
be
surprised
about
those
so
yeah.
B
I
think
we're
doing
really
well
that
most
of
the
at-risk
are,
I
think,
looking
pretty
good
we're
going
to
obviously
lose
a
bunch
of
them,
though
they
won't
make
it.
C
B
Yeah,
I
think
we're
we're
in
good
shape
everybody's,
been
reviewing
their
assigned
at
wrist
and
track
and
had
sense.
That's
what
we've
been
focusing
on
to
really
review
the
enhancements
and
make
sure
that
they're
substantially
complete
and
correct
and
yeah.
It's
been
the
team's
been
really
great
so
far
and
we're
kind
of
killing
it
so
cool
again.
A
A
A
With
great
well
thank
you
kirsten
and
thank
you
to
your
shadows
for
the
the
great
effort
so
far
on
this
I
know
enhancements.
You
all
have
the
most
work
up
front.
So
thank
you
for
for
crushing
that
next,
let's
do
ci
signal
with
rob.
A
Trying
to
see
doesn't
look
like
he
is
on
any
of
the
cia
signal.
Shadows
want
to
jump
in
and
take
this
otherwise
rob
has
the
status
marked
as
yellow,
so
we
can
just
handle
that
offline,
rob.
F
Yep,
hey
cool,
we
are
green
things,
look
pretty
normal
for
us.
We've
had
an
orientation
with
shadows,
so
I'll
be
probably
handing
over
some
of
the
reporting
duties
to
shadow.
So
the
over
the
next
couple
released
meetings
so
yeah
we
are
green.
We
are
in
good
shape.
We've
also
started
the
back
triage
tracking
spreadsheet,
so
we'll
be
sorting
the
issues
between
shadows
and
me
as
well.
A
G
Hey
hi,
I'm
just
in
the
middle
of
that
dropping
in
the
dropping
in
the
report
into
the
agenda
and
we're
we're
basically
yellow
to
red
at
the
moment,
and
I
can
just
call
it
in
front
of
me
now
and
so
basically,
where
we're
at
in
master
blocking
and
we
have
eight
flaking
jobs,
and
we
have
a
lot
of
work
being
done
by
the
team
to
report
on
those
jobs
and
for
the
most
part
they
they're
they're
on
the
edge
of
flaking
and
I'll
update
the
agenda
with
with
those
flakes
and
and
where
we're
just
getting
to
is,
is
that
we
have
a
lot
of
issues
reported
and
we
just
need
to
ramp
up
on
chasing
down
for
root
cause
analysis
from
the
various
cigs
in
order
to
start
figuring
out.
G
What's
going
on
with
some
of
the
flakes
and
overall
and
the
other
overriding
issue
that
we
have
at
the
moment
is
the
aggregated
results
tool
which
is
also
known
as
the
triage
tool
is
undergoing
maintenance
at
the
moment.
So
we
don't
have
we
don't.
The
triage
tool
has
only
data
up
until
the
21st
of
this
month
and
I'm
in
conversation
with
grant
in
order
to
work
through
some
of
the
issues.
G
So
essentially,
what's
what's
happened
is
that
he
had
numerous
changes,
side,
swipe
the
triage
tool
and
he's
working
through
the
the
range
of
changes
that
happen
to
them.
G
It's
it's
a
combination
of
image,
updates
and,
and
what
upgrades
of
you
know
python
to
pipeline
all
sorts
of
stuff,
so
he's
working
on
that
and
I'm
doing
some
async
pairing
with
them
on
getting
to
the
bottom
of
that,
and
the
only
the
silver
lining
in
in
in
that
cloud
is
that
I'm
learning
a
little
bit
more
about
ci
so
and
so
working
through
that
with
him
will
kind
of
increase,
at
least
my
knowledge
and
hopefully
I'll.
Shall
shell
out
the
team.
A
Great,
thank
you
super
super
detailed
update.
Is
there
anything
that
we
can
help
you
with
anything
that
you
need
from
from
the
team?
I.
G
Might
reach
out
to
former
signal
members
to
you
know
basically
dan
and
alejandro,
to
have
a
look
at
some
of
the
issues
so
I'll
put
calls
I
might
put
calls
out
for
help
just
to
review
a
few
of
them
and
and
basically
I
kind
of
need
to
train
up
the
shadows
on
escalating
the
issues
and
and
and
delivering
them
to
the
the
welcome
arms
of
people
in
various
things
and
testing
offs
and
and
sick
testing.
A
Okay,
yeah
sounds
good
if
you
need
anything
specifically,
let's,
let's
just
go
ahead
and
open
issues
on
the
release
board,
so
we
can
track
those
okay,
yeah.
H
A
E
So
there's
one
test
that
started
failing
september
11th
and
it's
actually
the
cause
of
most
of
our
flakes
right.
E
Now,
it's
all
a
single
step
in
the
pipeline,
the
extract
test-
all
it's
doing-
is
curling
binaries
and
trying
to
untar
them
and
the
download
retries
three
times
and
fails
all
three
times
like
makes
it
to
like
200,
megabytes,
300
megabytes
and
then
just
fails
and
like
I've
spent
hours,
trying
to
dig
in
and
figure
out,
what's
going
on
and
all
I've
been
able
to
pull
out
is
like
there's
something
going
on
with
the
networking
it's
pulling
it
out
of
a
gcs
bucket,
so
we
might
need
to.
E
We
gave
we
gave
testing
ops
a
heads
up,
but
we
might
need
to
like
escalate
a
bit
more.
G
Yeah,
let's
certainly
put
push
up
with
them
and
just
say
to
them:
look
we
need
help
with
this
and-
and
it
is
essentially
yeah
so
so
so
myself
and
eddie
went
through
that
and
we
we
got
some
initial
feedback
that
was
just
kate's
flakiness,
but
to
us
that
smells
like
a
sort
of
a
infrastructure
list
you.
So
we
need
to
change
that
up
and
just
get
to
the
because
of
that.
A
Okay,
great:
let's,
let's
keep
sync
on
that
and
if
we
need
to
let's
make
a
tracking
issue
just
so,
we
can
follow
that
through
and
make
sure
we
don't
lose
it
and
get
to
a
point
where
ci
is:
is
super
unhappy
again:
yeah?
A
I
Sure,
hey
everyone!
We
are
green.
I
created
the
integration
branch
for
the
docs
last
week
and
we're
gonna
start
talking
the
prs
related
to
the
enhancement
starting
this
week,
so
we're
on
track.
J
A
K
I'm
coming
in
a
little
late,
but
I
finally
got
all
my
shadow
on
board
and
completed
so
this
week.
The
plan
is
to
meet
with
everybody,
we're
gonna
game
plan.
This
release
cycle
a
little
bit,
get
everybody
kind
of
comfortable.
K
We
always
kind
of
come
in
a
little
bit
later,
so
that's
just
like
for
being
in
comms,
and
but
one
thing
I
have
started
this
last
week
was
starting
to
track
what's
happening
in
enhancements,
start
to
really
look
for
potential
themes
and
preemptively
try
to
identify
areas
where
they
could
be
potential
feature
blogs,
so
at
least
get
it
mentally
in
our
head
and
hopefully
allow
us
to
be
in
front
of
it
instead
of
like
the
last
two
weeks
so
so
far,
everything's
green
now.
L
I
have
a
question:
have
you
gone
with
the
idea
of
having
the
like
internal
calendar
in
terms.
K
A
Ambulance
number
one:
yes,
all
right.
Moving
on
release
branch
management
with
marco.
M
A
A
Nope
all
right
moving
on,
I
think
lockheed
said
he
was
going
to
be
out
today
and
he
dumped
a
little
bit
of
an
update
in
here,
but
essentially
he
scheduled
a
shadow
orientation
for
thursday.
I
would
highly
encourage
everybody
to
come
to
that.
It's
a
great
place
to
ask
questions
about
the
just
the
process
in
general.
Any
any
items
that
you
need
attention
from
lockheed
for
or
from
the
release
team
leads
in
general.
Just
you
know.
I
think
it's
a
great
place
to
go.
Introduce
yourselves
to
everybody
else.
A
If
you
haven't
had
a
chance
to
do
that
yet
and
and
just
generally
make
the
most
of
your
shadowing
experience
and
ask
questions
anything
else
that
will
help
you
out
there
and
then
one
thing
I
added
here
last
week
we
mostly
did
introductions,
but
I
think
we
might
not
have
had
everybody
on
the
call.
Yet
so
I'll
pause
really
quickly
and
if
you
haven't
introduced
yourself,
this
would
be
an
awesome
opportunity
to
do
that.
Now.
A
Just
so
everybody
knows
everybody
else
on
the
team,
so
we'll
just
first
come
first
serve
whoever
wants
to
to
go
first
or
if
any
of
the
leads
know
that
their
shadows
weren't
on
last
time,
take
the
time
to
introduce
them.
E
D
I
believe
we
have
sonia
on
the
call
who's
a
release.
Note
shadow,
I'm
not
sure
if
you
got
the
opportunity
to
introduce
yourself
last
time.
N
N
Hi,
so
my
name
is
sonia
and
I'm
from
india,
so
yeah
I'll
be
working
with
release
shadow.
Apart
from
this,
I
am
associated
with
the
project
thanos
and
new
to
kubernetes
yeah.
A
All
right
well,
thank
you
for
introducing
yourself
feel
free
to
to
drop
into
sig
release.
If
you
don't
feel
like
saying
hello
here,
just
say
hello
in
the
sigridly
slack
channel
and
get
to
know
everybody
next
up.
My
update
today
I'll
be
sending
out
a
doodle
that
will
have
some
proposed
times
for
an
india
asia-pacific
centric
meeting
time.
A
A
One
update
is
that
we
added
a
test
freeze,
so
we
have
this
defined
as
a
milestone
and
it's
in
the
phases
document,
but
missed
it
when
we
make
when
I
was
making
the
schedule
for
this
time.
So
we
prod
a
change
in
and
now
we'll
have
test
freeze
on
november
23rd.
So,
ideally
for
that,
we
don't
want
to
make
any
new
tests.
A
After
that,
you
know
between
code
freeze
and
that
date
try
to
focus
on
getting
the
tests
short
up,
no
conformance
things
after
that
and
then
that'll
be
two
weeks
before
the
release,
and
then
the
release
will
be
on
december
8th
any
questions
about
the
calendar.
Any
concerns
about
the
schedule.
A
All
right,
we
don't
have
an
update
from
scalability.
So
let's
just
jump
over
to
program
management
with
lori.
L
Hi
there
so
a
couple
things
if
you're
new
to
this
meeting
the
release
team
has
a
project
board
and
I
updated
that
last
week.
So
there's
a
note
from
stephen:
I
jumped
it
into
the
stock
from
sig
release
channel,
please
be
sure
to
add
issues
and
prs
to
the
relevant
project
boards
right
now.
This
is
a
manual
process.
L
Second
thing
is,
I
was
doing
a
review
of
retro
items
going
back
to
115
to
see
if
we
followed
up
and
because
some
things
had
not
been
turned
into
github
issues
and
some
things
we
just
you
know
time
goes
by
and
we
hadn't
checked
in
with
them
to
see
if
they
were
really
done
or
not.
So
we're
actually
almost
done
reviewing
all
of
the
items
from
our
various
docs
and
github
issues
that
were
unaccounted
for
and
there
aren't
many
left.
L
There
are
a
couple
items
that
I've
posted
in
the
sig
release
channel
we've
been
doing
a
really
great
job
and
closing
those
out
lots
of
good
discussion
and
you'll
see
a
little
done,
emoticons
to
show
that
the
conversation
was
resolved
from
friday.
There's
a
couple
of
newer
items
that
we
have
not
resolved
yet
or
seen
any
comments
on.
L
I
I
L
One
of
them
yeah,
so
I'm
just
wondering
if
anybody
is
overseeing
the
action
items
from
119
at
the
moment
like
putting
them
into
a
github
issue
or
making
sure
we
don't
lose
track
of
those.
A
O
Sorry
sorry
you're
me
and
you
need
to
cut
some
of
the
dog's
issues
are
also
cracked
in
the
issue
which
anna
has
cc'd
like
reaching.
I
think,
and
I
was
following
up
on
one
of
the
stuff
that
worked
with
the
enhancements
team,
and
there
was
one
thing
that
came
out
that,
once
after
the
kk
code
prs
are
implemented,
then
only
the
docs
needs
to
be
merged,
and
there
we
need
to
check
on
that.
We
kind
of
missed
that,
so
we
were
discussing
on
how
to
track
it.
O
I
Yeah,
so
I
think
docs
related.
We
are
tracking
it,
but
other
than
that,
I
don't
think
it's
being
tracked
anywhere.
L
Okay,
so
oh
terrible.
L
L
L
Yeah,
so
I
don't
know
how
much
discussion
this
requires
it
just
came
up
while
I
was
reviewing
the
retro
items
and
then
in
release
engineering
document
jumped,
but
basically
do
we
need
clarification
around
how
we
handle
working
on
weekends
and
off
hours,
which
is
basically
to
say
that
we
don't
require
it
except
you
know.
L
If
you
sign
on
to
do
something
during
your
weekend
or
after
work
hours,
then,
ideally
you
tell
people
if
you
can
no
longer
follow
through
with
something
do
we
need
to
clarify
that
in
docs
for
this
group,
our
policy.
I
So
I
think
it
was
a
problem
in
the
past,
so
I
think
it
is
required
just
to
have
it
there
in
my
opinion,
but
of
course
like
I
don't
think
it
was
required
like
last
release
or
like
I'm,
not
sure
about
this
release.
But
it
is
something
good
to
have,
in
my
opinion,.
C
Okay
last
one
to
anna
that
I
think
that
would
really
help.
Given
that
a
lot
of
I
mean
given
the
distributed
time
zones
and
everything
else,
it
would
be
a
good
thing
for
all
the
you
know
concerned
teams
to
have
an
overview
of
how
the
person
is
at
you
know
having
the
workload
of
that
person
or
you
know
if
the
person's
availability
is
not
matching
at
that,
given
point
of
time
in
a
release
if
he
or
she
is
not
able
to
take
all
more
work.
L
Around
so
what
do
you
think
about
this?
If
we
take
a
look
at
what's
in
the
existing
docs
and
draft
any
sort
of
clarification
and
then
come
back
next
week
with
the
draft
language
and
then
or
we
can
post
it
in
the
channel
like
here's?
Here's
the
clarified
language
around
this
policy.
Does
anybody
object
and
make.
O
N
Yeah,
it
makes
sense
yeah.
I
A
A
Okay,
great,
I
just
closed
the
gen
attack.
Let
me
reopen.
G
A
The
agenda
and
the
doc
itself
in
the
same
place,
I
feel
like
there's
a
better
way
to
do
it,
but
I'm
not
sure
what
the
best
one
put
it
yeah
then
I
think
the
same
like
oh
more,
I'm
scrolling
all
the
way
down:
okay,
any
other
open
items
that
people
would
like
to
bring
up
before
we
jump
into
the
the
project
board.
A
Okay,
I
will
mention
that
the
retro
document
is
open
and
we
have
it
scheduled
for
the
end
of
the
release,
but
as
we're
going
through
this
just
as
a
reminder,
if
you
come
across
anything
that
you
think
would
be
worth
noting
to
discuss
to
change
for
next
time
or
things
you
think
are
working
really
really
well,
please
add
them
to
the
retro
so
that
we
have
them
documented.
A
It's
just
much
easier.
I
think
in
general
to
have
those
things
documented
when
you
think
about
them,
rather
than
we
get
to
the
retro
and
everybody's
trying
to
rack
their
brain,
to
figure
out
what
what
went
well
and
what
didn't
go.
Well,
all
right!
So,
let's,
let's
bring
up
the
project
board
and
I'll
share
my.
A
Screen
so
here's
a
fun
side
note
tim
has
been
uploading
all
of
the
sig
release
meetings
and
because
my
resolution
is
super
high.
The
recording
for
the
last
two
meetings
has
been
really
really
large.
So
I
need
to
fix
that
for
next
time.
F
A
Blocked
waiting
things,
update,
ci
signal
issue
format
to
be
more
conducive
to
triage
is
dan
on.
Do
you
want
to
discuss
this
or
rob?
Do
you
have
any
input
for
this?
One.
G
And
so,
since
the
last
time
since
the
last
time
I
this
came
up
on
our
walkthrough,
I
had
a
look
at
the
issue
and
at
the
moment
that
issue
is
kind
of
a
is
kind
of
stalled
by
a
philosophical
debate
on
on
how
we
should
report
ci
signal
issues
when
I've
bedded
down
the
automated
report,
I
might
be
able
to
weigh
in
on
that
and
try
and
close
it
off.
But
I
expect
it'll
be
a
few
days
before
I
get
to
see
that
maybe
more
realistically
next
week.
A
Okay,
cool
you
can
revisit
it
then
ci
signal
subproject
lori.
Do
you
have
any
updates
to
add
to
this
one.
L
Yeah,
so
I
don't
want
to
go
rogue
sasha
and
jorge,
and
I
talked
about
this
at
our
release-
lead
sync,
and
so
let's
just
table
that
for
now,
okay,.
A
A
Next
up
we
have
update
the
shadow
dot
md
fixed
role,
handbook
url,
so
this
one
we
probably
just
need
reviews
on
12
31.
Let's
take
a.
A
A
Cool
looks
like
dan
left
a
comment
and
we're
just
waiting.
Maybe
some
feedback
there
I'll
follow
up
offline
on
this
one
and
then
remove
sig
pm
references
from
the
enhancements
lead
handbook
definitely
need
to
fix
that
one
up.
Thanks
for
opening
that
eddie,
kristen
or
nabaroon.
Have
you
looked
at
this
one.
H
Yes,
so
I
have
been
updating
several
references
in
the
handbook,
as
well
as
like
making
some
structural
structural
changes
and
some
information
edition.
So
question
has
basically
reviewed
it
in
a
draft
mode
in
my
fork.
So
I'm
just
going
to
like
we
are
in
those
changes
in
the
release.
Sig
release
repository
basically
with
the
handbooks.
A
Great
thank
you
for
that
update
any
questions
on
that
one
eddie.
Do
you
think
that'll
address
this.
A
Awesome,
thank
you
in
progress,
improve
doc's
role,
handbook
savitha
anna.
Do
you
have
anything
you
want
to
discuss
on
that?
One.
O
I
we
have
one
or
a
couple:
priya's
marched
already,
and
there
are
few
more
I
need
to.
I
had
a
couple
things
to
one
regarding
the
embargo
process,
which
was
a
little
confusing
when
we
were
doing
the
release,
went
to
start
the
release.
The
docs
went
to
marge
and
stuff
like
that,
so
I
have
to
go
through
my
notes.
Chat.
Basically,
that's
my
notes.
O
I
will
update
that
create
a
prior
for
that
and
as
soon
as
I
I'm
hoping
to
do
it
today
or
tomorrow,
so
that
we
are
be
coming
up
and
there
are
more
tasks,
probably
online,
I
will
divide
and
if
anyone's
going
free
feel
free
to
jump
in.
That's
all
for
me.
A
Great
thank
you
for
that
update
and
I'll
just
echo
like,
if
you
have
any
interest
in
helping
out
with
that,
it's
great
great
way
to
jump
in
and
and
just
understand
how
the
flow
works
for
some
of
these
things.
Next
up
rob
any
more
update
on
your
ci
signal.
Weekly
status
updates
sounded
like
this
was
maybe
next
week.
You'll
have
something
yeah,
so
so
I.
G
I
worked
in
that
this
week
and
I'm
just
I'm
just
throwing
an
update
onto
the
issue
now,
essentially
where
I'm,
where
I'm
at
with
that
is.
There
was
an
unauthenticated,
http
client
call
in
there,
which
meant
that
it
got
rate
limited
after
one
run,
and
so
I
fixed
that
up
and
I'm
just
about
to
link
to
a
gist
that
has
so
for
the
moment.
I'm
just
outputting
it
as
an
org
file.
G
So
I
can
quickly
zip
through
it
in
emacs,
and
the
next
steps
here
are
to
just
add
some
parameters
on
the
upper
format
and
and
then
so
so
I
kind
of
have
a
mini
roadmap
in
my
head
as
to
where
this
would
go
and
I
kind
of
need
to
find
a
home
for
it
in
in
rico
land
from
with
respect
to
code,
and
then
I
need
to
find
a
home
first
to
run
and
I'm
thinking
that
that
I
might
run
it
as
a
crowd
job
four
times
an
hour.
G
G
So
the
update
is,
is
that
that
I
can
now
just
run
this
more
than
once
in
an
hour
so
and
I'll
drop
in
the
output
in
gist
form
on
the
issue
now
and
you'll
see
it
once
I
can
find
the
right
place.
The
agenda
places
today.
Sorry
about
that
again.
A
Else
all
right
cool,
so,
let's
just
go
through
the
backlog.
We
have
a
little
bit
of
time
left
this
one.
I
opened
this
the
s.
The
steering
committee
requires
that
sig,
chairs
and
tech
leads
complete.
The
cncf,
unbiased
unconscious
bias
training,
and
I
thought
it
was
a
good
idea
for
the
release
team
leads
to
do
that
as
well.
So
I'm
going
to
do
a
pr
to
add
that
to
the
onboarding
process
this
week,
so
that'll
move
to
in
progress
today.
A
Next
up
rob
do
you
want
to
discuss
this?
One
produce
onboarding.
G
Video
playlist-
and
I
haven't
looked
at
this
since
in
the
past
week
because
of
the
because
of
the
report
and
yeah
I'll
have
to
once
once
I'm
I'm
not
so
hot
on
the
report
I'll
get
around
to
this
okay
yeah.
L
Just
about
not
going
rogue
on
ci
signal,
so
this
issue
came
up
in
my
chat
with
sasha
and
jorge.
I
think
that
you
and
dan
and
the
two
of
them-
and
I
should
just
pull
together
a
plan
for
what
we
want
to
do
with
ci
signal
awareness,
phrasing,
yeah.
H
G
I
think
I
think
I
said
I'd
take
the
a
task-oriented
view
of
task,
food,
etc,
so
reporting
and
then
chasing
up
and
and
and
the
guys
are
talking
about
doing
reference
material
for
test
grid.
I
think.
A
A
G
Basically,
it
would
be
good
to
have
some
content
for
basically
it's
it's
a
it's,
it's
tips
and
tricks
for
day-to-day
operations
for
a
ci
signal
that
that's
what
I
want
to
produce
and
that's
what
I've
done
privately
in
in
one-on-one
sessions
with
the
shadows,
but
it
will
be
nice
to
have
that.
This
is
how
day-to-day
operations
happen
on
ci
signal.
A
A
And
work
with
my
my
shadows
to
get
this
one
done.
Add
information
about
what
qualifies
for
a
milestone.
A
E
L
A
More
general
general
one
ci
single.
A
Yeah,
this
was
a
little
old
rob.
Do
you
think
you
and
your
team
could
take
this
one
and
either
close
it
out
or.
G
Yeah
yeah
yeah.
Let
me
take
a
look
at
it.
Yeah
I'll,
take
a
look
at
that
yeah!
Okay!
Thank
you.
So
much.
A
All
right
deciding
procedure
for
jobs
entering
and
leaving
blocking
state
again.
That
seems
like
a
more
general
sig
release
item.
Does
it
read
on
that
one.
L
G
D
A
So
1040,
I
think,
is
something
we
could
probably
pick
up
within
the
release
team
this
time
around,
it
spans
multiple
releases,
but
I
think
this
is
pretty
specifically
in
the
area
of
the
release
team,
probably
the
same
for
688.
Does
anybody
want
to
take
a
look
at
these
and
maybe
pick
them
up
and
move
them
forward?
A
L
A
No,
probably
not
do
you
want
to
pick
it
up
and
report
back
next
time.
L
J
L
A
A
All
right,
scalability
tests
for
beta
releases
is
the
last
one,
that's
in
the
backlog,
let's
just
pop
that
one
open.
Currently,
we
have
the
following
jobs:
to
gauge
the
quality
of
the
current
release.
A
A
This
one
also
seems
like
probably
a
more
broad
than
just
this
release
team
discussing
it.
So
maybe
we
can
add
this
to
the
agenda
for
the
next
release
meeting
to
discuss.
A
Any
any
thoughts
on
this
one
are
we
good
to
put
punt
this
to
the
next
release
meeting
to
discuss.
A
All
right,
I
think,
that's
everything
in
the
backlog,
so
I
think
we're
done.
Anybody
have
any
topics
they
want
to
bring
up
before
we
jump.
A
Off
all
right,
well,
thank
you.
You
can
have
a
few
minutes
back
of
your
morning
and
your
evening
and
have
a
great
monday
or
have
a
great
rest
of
the
monday.
If
it's
the
evening,
for
you,
everybody
have
a
great
week.