►
A
B
All
right,
there
is
one
issue
on
here:
that's
or
that's
not
on
here
yet,
which
is
for
the
new
commit
event
and
that's
going
to
be
top
priority.
I
just
don't
have
the
issue
yet
so
just
look
out
for
that.
Sorry,
why
premium
and
why
ultimate
are
going
to
be
closed
out
by
noon.
So
you
guys
can
take
them
on
thanks
for
bearing
with
us
getting
that
stakeholder
feedback
and
then,
if
you
can
scroll
down,
there's
a
couple
things
at
the
bottom.
B
These
moving
the
learn
more
links
within
the
pricing
page
somewhere
else,
so
we
can
a
b
test
it
and
then
also
adding
these
lead
capture
forms
onto
the
roi
calculator.
So
we
can
also
maybe
test
that
those
are
some
smaller
things
that
I'll
be
taking
on
the
sprint
in
order
to
like
set
us
up
for
for
a
b
test,
possibly
maybe
an
expert
or
something
like
that.
C
And
then
sorry,
just
no
no
go
ahead
can
maybe
just
add
some
clarity
for
commit.
I
think
it
should
be
in
the
open
column.
Now
I
just
created
the
issue,
so
I
just
met
with
the
the
commit
folks
this
morning.
So
it's
like
very
fresh
off
the
presses,
but
basically
we
need
to
get
a
commit
landing
page
for
registration
up
by
july
20th,
but
more
like
july
18th.
Just
so
we
have
a
couple
days
of
buffer.
C
Whoever
has
capacity
this
iteration,
but
because
it
is
like
a
company-wide
event,
it
will
take
priority
over
basically
anything
else
that
the
engineering
that
engineer
is
working
on
and
then
the
commit
folks
will
be
the
one
with
all
the
content,
images,
etc
and
it'll
likely
be
very
iterative,
as
in
like
we'll,
have
a
bit
of
information
right
now
and
then
we'll
just
get
more
information.
As
the
event
comes
closer,
so
it'll
be
quite
a
bit
of
work
there
and
then
also
just
for
clarity.
C
I
totally
understand
that
this
is
not
conversion
related,
but
this
is
kind
of
more
that
fourth
group
that
hasn't
fully
been
defined
so
just
had
a
bit
of
capacity
and
she
was
gender
not
generous
enough
to
like
volunteer
her
support
here.
So
ideally,
we
just
keep
it
within
conversion,
and
one
of
the
engineers
here
can
pick
it
up
if
they
have
capacity.
A
I
was
gonna
also
bring
up
kind
of
jess
and
megan
will
probably
touch
on
this,
and
hers
is
that
with
margareth
kind
of
being
on
vacation,
outish
megan
might
help
with
some
of
the
release
post
updates
so
that
some
of
that
might
transition
over
to
her
depending
upon
actually
now.
With
this
event,
we'll
kind
of
see
how
things
shake
out.
D
Yeah
people
who
are
tuning
in
week
to
week,
you'll
notice,
my
column,
looks
almost
exactly
the
same
with
an
important
distinction
that
the
second
item
there
is
now
in
the
doing
status.
So
the
content
security
policy
is
in
really
good
shape.
The
merge
request
is
in
I've
passed
one
rounded
review.
I've
we've
also
passed
security
review,
so
up
next
has
to
go
to
the
maintainer
review
before
merge
in
the
intervening
time,
while
all
those
reviews
were
happening,
it
started
like
breaking
pipelines.
I
made
no
code
changes.
D
This
is
just
the
nature
of
working
with
the
product.
Sometimes
the
ground
moves
underneath
your
feet,
so
I
need
to
fix
whatever's
broken
in
the
pipeline,
I'm
looking
at
it
right
now
and
it
doesn't
look
too
bad,
so
this
should
be
merged
in
like
today
or
tomorrow
or
or
it'll,
be
ready
for
maintainer
review
today
or
tomorrow,
and
hopefully
they
will
get
around
to
it
today
or
tomorrow
and
merge
it
in
we'll
see.
That's
almost
done.
D
It's
not
five
points,
it's
like
one
or
two
points
of
wrap-up
of
work
and
then
because
I'm
sort
of
done
with
that,
I'm
gonna
get
started
on
this
data
layer.
Events
for
sas
triunflow
there's
actually
like
six
things
in
there.
Maybe
seven
there's
like
a
bunch
of
different
like
smaller
items,
all
of
which
I'm
going
to
do
sort
of
one
at
a
time
to
see.
D
If
I
can
get
the
merge
requests
to
go
through
a
little
bit
faster,
there's
also,
it
seems
I
think
a
few
things
are
already
done
so
that
will
probably
take
up
most
of
this
week
and
some
of
next
week
for
me
and
then
once
I'm
there,
I'm
going
to
try
and
get
my
customers
doculab.com
development
environment
set
up.
This
is
my
I
think,
I'm
on
vacation
at
the
right
after
this
sprint.
D
I
think
I
have
like
a
full
sprint
and
then
I'm
in
that
I'm
out,
so
I
don't
want
to
like
start
anything
that
people
are
going
to
be
relying
on
me
for
because
I'm
going
to
be
out
for
like
three
weeks.
So
my
plan
here
is
really
just
like
wrap
up
those
two.
Those
top
two
items
and
then
get
started
on
the
bottom
two
and
hopefully
come
back
after
my
longer
vacation
sort
of
like
ready
to
go
on
whatever's
next.
So
I
think
that's
it.
E
Yeah
for
for
my
empty
column,
I
wanted
to
bring
that
up.
I've
been
watching
the
backlog
and
there
hasn't
been
much
except
for
that
y
ultimate,
which
I
knew
was
blocked.
Speaking
with
justin,
it
sounds
like
this
might
be
split
into
smaller
parts,
I'm
not
sure
and
then
mentioning
margaret's
issues.
I
didn't
want
to
just
assign
myself
to
those
unless
justin
you
had
the
conversations
he
needed
to.
E
A
F
F
Preview
of
what
the
design
will
be
and
I've
been
looking
over,
which
components
we
might
need
and
yeah.
I
think
I
will
be
working
on
that
this
sprint.
It
might
be
too
little.
It
depends
on
which
route
we
go
if
we
want
to
update
stuff
in
slippers
or
if
we
want
to
just
do
it
on
the
on
the
buyer.
Experience
repository
so.
F
F
As
I
understood
it
is
that
the
font
sizes,
like
grew
significantly
for
some
headers,
which
might
look
funky
in
some
of
the
site,
and
there
are
some
slippers
updates
coming.
I
think,
with
the
buttons
and
stuff
and
tyler
said
it
was
not
the
tyler
nathan
and
said
that
it
was
not
the
best
moment.
I
think.
D
D
If
you
go
into
the
merge
request,
just
I
don't
know
if
you
can
quickly
find
that
I
put
a
screenshot
of
just
like
two
headers
side
by
side,
but
basically
like
it's.
Probably
that
result
if
you
scroll
up
or
up
up
up
up,
resolve,
related,
merge
requests,
resolve
jam,
3,
typography
updates,
and
I
think
I've
got
a
comment
down
in
this
thread,
but
yeah.
So
like
that's
going
to
move
a
bunch
of
stuff
around,
it
might
be
fine.
C
D
Yeah,
I
think
this,
I
think
it's
done.
Gabby's
gaby's
work
is
done.
This
is
like
gabby
has
done.
The
thing
like
it
was
mostly
just
changing
values
right
but
like
substantially
changing
those
values.
So
all
that
to
say
I
think
it
would
be
prudent
for
us
to
merge
this
in
get
it
into
slippers.
Nathan
has
a
release
cycle
going,
so
we
might
be
a
day
or
two
out
from
that
being
like
totally
ready,
but
once
slippers
gets
like
incremented.
B
Yeah,
I
think
that's
fine.
I
also
just
want
to
let
gabby
know
it
might
not
have
been
obvious
in
the
updates,
but
we
did
adjust
the
kerning,
which
is
the
spacing
between
the
letters
as
well
and
and
the
line
height.
So
I
just
want
to
make
sure
that
everything,
not
just
the
size
of
the
type
but
the
size
of
the
line
height
and
the
size
of
the
space
between
the
letters
got
adjusted.
F
B
F
C
F
A
H
H
F
H
A
Little
both
would
be
independent
issues
that
help
support
gabby.
Wouldn't
it
wouldn't
necessarily
be
pairing,
but
that'd,
be
you
if
it's
a
new
component
build,
you
would
have
all
the
specs
that
gabby
needs
for
her
page,
and
you
would
build
that
component
that
then
she
can
use
to
her
page
as
she's
building
other
components
to
build
the
overall
page
structure.
G
Dennis
all
right,
I'm
up
ga4
one
trust,
consent
mode
that
one
is
enabled
by
jameson.
I'm
still
waiting
on
the
g
tag
code
update
on
each
subdomain.
We
have
it
live
for
docs.gitlab,
but
the
other
ones
are
still
pending.
I
think
we
have
an
mr
for
about.gitlab,
so
I'm
hoping
that
one
can
go
live
sometime
this
week
and
that
kind
of
is
like
a
domino
effect
on
other
tasks
that
I'm
working
on
so
ecommerce.
G
G
A
G
Aside
from
that,
I'm
working
on
analysis
for
each
group.
We
have
one
for
product
marketing
tomorrow
and
then
conversion
is
next
week
and
then
towards
the
end
of
the
sprint.
I'm
gonna
start
on
the
post
post
redesign
analysis,
which
is
the
same
analysis
that
I'm
doing
but
extending
that
date
for
our
group
convo
on
july
28th.