►
A
B
Oh
yeah
jump
in
what
I'm
up
to
so.
There
was
two
surprise
releases.
There
was
version
2.0.15,
which
should
have
been
2.1,
and
then
there
was
2.1,
which
I
just
released
today
and
so
there's
a
lot
of
changes
in
those
you
can
check
them
out.
I
post
them
in
the
digital
experience,
slack
channel
so
they're
both
there
I
looked
into
the
figma
storybook
plugin.
I
spoke
with
jess
today
about
it
and
looks
like
we
might
try
it
out.
B
So
this
would
allow
us
to
bring
in
storybook
components
and
their
variants
into
figma,
so
it
allowed
design
to
kind
of
compare
them
easier
and
then
they
could
also
use
them
in
the
designs
if
they
want
to
also
went
pretty,
I
was
gonna,
say
pretty
ham,
but
I
don't
know
if
people
understand
that
I
went
wild
on
the
www
repo,
so
I
deleted
a
ton
of
old
features
and
pricing
stuff.
So
a
lot
of
old,
like
experiments,
there
were
so
many
ammo
files
that
were
like,
for
I
don't
know
what
they
were.
B
They
weren't
used.
So
hopefully
nobody.
Nobody
comes
back,
it's
been
so
far
so
good.
It
should
make
things
easier,
though,
because
I've
noticed
that
there's
been
a
lot
of
changes
to
the
old
pricing
faq
yaml,
which
doesn't
exist
anywhere,
because
we
don't
use
the
pricing
faq
page.
So
I
created
a
new
issue.
It's
set
up
for,
like
that
pricing
team,
the
conversion
team
for
next
iteration
to
go
back
and
update
the
pricing
faq
with
all
the
changes
that
have
happened
in
the
last.
Who
knows
how
long?
B
Also
that
side
nav
is
in
it's
currently
on
the
support
page
and
I
think
gabby's
going
to
bring
it
into
a
page
he's
working
on?
Maybe
this
iteration
or
next
and
yeah.
I
also
added
kind
of
process
for
slippers
releases.
So
now
there's
an
epic
that
houses
all
the
releases
inside
the
release.
You
have
the
release,
notes
and
then
there's
two
blocking
issues.
So
that's
the
import
and
the
publish-
and
they
all
have
links
in
there.
C
Yep,
so
I
work
on
the
features
landing
page.
Currently,
I
need
to
make
some
updates,
as
nathan
discussed,
we're
still
figuring
out
things
with
the
features
oml
file.
So
I
need
to
update
that.
I
also
worked
on
migrating
the
continuous
delivery
page.
I
have
an
mrn
place
for
that
already,
so
I
just
need
some
review
from
jess
since
tina
is
a
little
bit
busy,
so
I
think
that's
it
for
me.
I
guess
matteo.
D
Okay,
so
I
took
my
vacations
this
iteration,
so
it
was
a
short
one
for
me.
I
picked
up
a
bunch
of
one
pointers:
typography
updates
in
solutions
features
and
missing
images
and
icons
on
some
topics;
pages
and
also
adding
a
new
cta
button
to
the
header
in
the
topics
pages
and
that's
it
for
me.
Next,
one
happy.
E
E
I'm
just
pulled
up
this
comment
just
to
see
one
trust
is
blocking
gtm's
preview
mode
from
firing,
if
you
just
doesn't
consent
to
the
performance
cookie.
So
we
have
to
wait
on
that
one.
I
worked
on
enhancements.
That's
still
in
review
app
for
the
for
the
enterprise
and
small
business
page.
It's
that
little
like
other
side
nav.
Maybe
we
come
up
with
better
names
for
that
stuff,
but
working
on
that
and
then
worked
on
adding
documentation
to
the
launch
darkly
experiment.
E
I
got
word
from
support
that
we
should
be
able
to
run
an
experiment
now
I
have
to
actually
try
it,
but
hopefully
that'll
work
and
I
did
start
on
the
data
later.
Events
for
the
sas
trial
flow
didn't
get
very
far
with
that,
as
I
was
focused
with
some
of
the
other,
mrs,
but
I
was
hoping
to
get
that
finished
up
before
tyler
gets
back,
so
that's
it
for
me.
I
think
that's
all
of
us
and
so.
B
B
Hopefully,
everyone
can
see
this
so
yeah.
There's
a
spike
to
investigate
features.
Ammo,
as
everyone
knows,
features
yaml
is
like
11
000
lines,
it's
massive,
and
so
I
just
want
to
understand
how
it's
used
who's
using
it
and
why
it's
used,
and
so
just
some
interesting
things.
I
looked
at
the
bat
that
the
last
20,
I
guess
the
history
of
the
edits
for
this
page,
there's
18
unique
contributors.
So
it's
not
the
same.
People
that
are
updating
it.
12
are
from
products
six
from
engineering
and
then
this
is
what
they
were
doing.
B
So
when
we
release
features,
get
updated
and
I
never
really
thought
about
it.
So
I'm
curious.
If
there's
a
way
we
can
also
automate
when
they
do
the
release
post,
that
we
could
somehow
add
the
features
to
the
the
file
as
well.
There's
just
some
related
resources,
so
just
random
files
that
talk
about
features
yaml
and
then
these
are
the
ones
that
are
actually
reading
features
yaml.
B
So
there's
a
bunch
still
in
www,
there's
actually
two
of
them
that
are
used
by
products
to
just
understand,
I
guess
what's
in
features
yaml
or
kind
of
visualize
it
and
so
there's
by
theme
and
paid
tier,
and
I
can
try
and
show
them
here.
This
bar
is
in
the
way
and
it's
pretty
cool.
I
guess
it
just
reads:
the
file
grabs
all
the
scores
rates
them
by
the
highest
groups.
B
Them
they
do
all
sorts
of
fun
stuff
and
there's
also
this
one
like
what
plans
things
are
a
part
of
what
stage
they're
part
of,
and
so
I'm
wondering,
if
there's
a
place
here
where
we
can
kind
of
work
with
products
to
maybe
help
them
visualize
this
better
and
maybe
get.
I
don't
know
make
this
easier
for
everybody,
maybe
bring
it
to
buyer
experience,
because
one
day,
I
think
this
all
is
going
to
go
to
buyer
experience
and
then
a
bunch
of
pricing
pages
and
then
one
interesting
thing.
B
I
know
I
learned
there's
116
unique
properties
in
that
file,
and
so
what
was
going
on
in
the
past
is
that
all
the
competitors,
like
a
small
big,
we
were
checking.
If
they
had
a
lot
of
these
features,
and
so
we
would
check,
there's
a
boolean
that
says
like
true
or
false
and
we
don't
use
it
anymore
like
now.
B
If
you
look
at
our
feature
comparison
page
there's
only
like
bitbucket
and
like
the
bigger
bigger
competitors,
and
so
I
asked
if
we
can
remove
them,
and
I
think
it's
just
bubbling
up
now
to
whoever's
in
charge.
But
if
that's
the
case,
we
can
remove
probably
around
2
000
lines
from
that
file,
and
then
we
can
move
another
thousand
lines
from
there's.
Another
field
that
is
like
is
it
free?
Is
it
premium?
Is
it
ultimate?
And
so
obviously,
if
something's
ultimate,
then
it's
free
and
pretty
good?
B
It
has
all
the
fields
underneath
it
all
the
plants
underneath
it.
So,
instead
of
having
three
or
four
booleans,
we
could
just
have
one.
That's
like
an
enum
that
just
accepts
like
the
plan,
so
I
think
there's
a
lot
of
immediate
cleanup.
We
can
do
at
least
get
it
down
by,
like
thirty
percent
and
then
later
on.
We
can
confine
maybe
a
longer
term
solution
but
yeah.
Hopefully
this
was
interesting.
These
were
the
findings
and
then
we'll
come
up
with
an
action
plan
for
for
going
forward.