►
From YouTube: Secure Team scheduling for 11.8
Description
In this session, we are scheduling the tasks for the next iteration (GitLab 11.8, starting January 8th, 2018).
After the planning meeting with the Product Manager, we need to evaluate what can the team commit to, depending on each task complexity, but also the team availability.
B
D
F
G
G
A
G
A
D
A
B
G
B
A
A
D
A
A
B
A
A
B
Oh
sorry,
good
test,
that's
188,
24
that
from
a
license
management
reports
and
buzzer,
so
I'm
thinking
about
that
one
I'm
thinking
about
issues
created
from
diabetes
should
be
confidential.
87
25
yeah
that
one
is
easy
easy.
As
long
as
you
know
how
to
find
the
thighs
in
Wales.
D
D
E
B
A
D
The
way
we
could
recognize
em
and
maybe
we
can
focus
on
some
of
them
instead
of
trying
to
solve
every
problems
at
once.
So
I
was
suggesting
to
focus
more
on
keeping
track
of
moving
lines
in
the
same
file,
but
Fabian
point
of
that
it
could
be
even
it's
it,
let's
likely
to
rename
a
file
or
to
move
directory.
If
it
happens,
it
will
have
a
huge
impact,
so
I'm,
not
quite
sure
I
mean
I.
Don't
have
ideas
of
what
per
stage
is
more
like
I
mean
what
issue
is
more
likely
to
happen.
B
B
B
D
B
B
D
B
D
A
D
B
D
D
D
F
A
A
B
A
B
It
is
I
had
a
talk
yesterday.
That's
a
different
script.
Singing
out
to
is
a
proxy
baseline
is
that
baseline,
I
think
dot
PI,
so
different
script
called
I,
don't
remember:
cold
cold!
Oh
oh
I!
Don't
remember,
but
there's
a
different
script
similar
to
the
one
year
year.
We
are
using
right
now
and
it
performs
I
can
scan
massive
come
online
in
trying
to
do
that.
Well,
that
seems
to
it
all.
B
A
D
A
D
I
think
in
the
end,
we
can
regroup
the
four
issues
about
SAS
tasks.
Company
scanning
in
depends
is
getting
into
one
issue
and
what
has
been
done
is
at
Andrea
from
the
DBA
team
work
on
not
a
POC
actually
is
already
using
it.
It's
a
different
way
to
count
based
on
estimations
instead
of
counting
the
all
the
records
into
in
the
table,
so
that
will
unlock
having
the
same
users
being
system
but
really
big
table
that
wasn't
working
today
when
breaking
the
usage
being
on
the
dot-com.
D
D
A
D
E
A
Someone
as
we
have
really
smashers
across
the
company
for
github,
you
get
Hep
C,
but
we
also
have
reason
and
a
jurors
inside
the
secure
team,
because
we
are
shipping,
some
docker
images
and
this
part
of
the
process
is
not
integrated
in
the
world
distribution
process
that
we
haven't
get
lab.
So
we
still
require
people
all
that,
and
since
we
require
people
for
that,
when
it's
really
time
to
mean
the
release
manager
is
going
to
be
dedicated
to
QA,
to
release
and
to
all
the.
A
B
B
B
B
B
D
B
A
A
B
B
A
A
A
A
B
A
A
A
B
A
B
B
B
B
A
B
B
B
A
D
H
A
B
B
A
B
A
A
A
D
G
D
D
G
B
H
C
A
F
G
A
A
D
We
had
a
lot
of
follow
up
since
the
beginning
of
the
conception
of
the
DB
model,
and
we
still
don't
have
indexes
that
could
help
speeding
up
the
different
queries
we
are
doing
like
the
group,
security,
dashboard
controls,
history
and
inner
abilities
list.
This
is
even
more
true
now
that
we
adding
featuring
capabilities.
D
We
were
dealing
this
issue
because
we
were
we
wanted
to
to
wait
to
have
more
data
in
the
database
and
also
to
know
more
about
which
usage
is.
We
will
do
of
it.
So
I
think
it's
it's
a
good
time
or
may
be
in
the
next
duration,
but
this
one
is
time
consuming,
because
we
have
to
discuss
also
with
TB
maintenance
and.
D
A
A
D
A
B
B
H
B
B
Know
just
it's
not
critical,
that's
not
just
keep
it
that
way.
It
may
be
in
the
future.
If
we,
if
the
butt
of
the
front
end
depends
on
this
I
mean
if
we
refactor
the
coding
in
the
front
and
I'm
not
even
sure
that,
because
I
use,
we
should
use
the
back
end
to
normalize
the
data
coming
from
the
reports,
so
it
shouldn't
be
an
issue
a
week.
It's
just
an
issue
for
us
really
so
you're
right.
It
shouldn't
be
there.
Maybe
I.
B
B
B
A
A
G
B
H
B
A
B
H
B
D
B
Issues
so
it's
it's
perfect
I'm
gonna
be
the
one
fixing
bugs
my
own
bags.
In
that
case,
that's
great
already
looking
forward
to
it
and
nobody,
that's
good.
Any
we'd
have
some
feedback
on
the
feature
on
the
new
feature
before
planning.
You
never
know.
Oh
well,
not
twelve,
twelve,
zero,
so
yeah,
that's
good
timing!
It's
it's
better!
That
way,
actually
yeah
good,
but
it's
not
a
mistake.
A
Okay,
all
right,
we
we
don't
have
any
discussion
group
today,
that's
good!
That's
fine
with
me!
We're
going
to
end
up
that
there
are
thank
you.
Everyone
I'm,
going
to
publish
the
planning
in
a
few
seconds
right
after
the
score,
so
I'm,
probably
going
to
see
you
in
the
company
code
then
enjoy
the
rest
of
the
day.
Thank
you
bye-bye.
My.