►
From YouTube: Monthly Release Kickoff 13.3
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
B
B
This
helps
for
groups
that
organizations
that
have
multiple
projects
that
span
the
bear
application
and
want
to
get
an
overview
of
how
their
code
coverage
is
improving
across
all
their
different
projects.
As
a
part
of
our
true
MVC
iteration,
we're
going
to
be
starting
with
just
the
ability
to
download
the
report
for
all
of
the
projects
within
that
group,
but
we'll
soon
add
the
ability
to
have
this
similar
chart
that
you
see
at
the
project
level
at
the
group
level.
B
That
is
my
most
the
feature
I'm
most
excited
about
coming
in
13.3,
but
I
also
want
to
highlight
a
real
cool
theme
that
is
a
merge
across
13.3
in
our
release,
configure
and
monitor
stages.
These
stages
are
all
about
what
happens
with
your
application
in
production
releases
about
getting
its
production
configure
is
about
how
the
infrastructure
is
prepared
in
your
production.
B
Environments
and
monitor
is
about
responding
to
the
live
health
of
your
application
in
production
environments
and
as
part
of
that,
where
I
want
to
go
stage
by
stage
through
how
we're
improving
real
production
quality
support
for
your
applications
and
larger
organizations.
The
first
step
we're
taking
is
this
ability
to
revolt
directly
from
your
CI
variables
as
part
of
your
release
process.
B
There
are
probably
core
secrets
in
your
deployment
process
that
are
stored
in
vault,
and
this
allows
you
to
directly
reference
them
in
your
get
web
CI
mo
as
part
of
your
release
or
deployments
definition
without
having
to
have
the
kind
of
intermediaries
that
we've
been
supporting
as
a
as
a
workaround
today.
The
next
feature
we'll
be
adding,
is
group
deploy
keys
if
you're
familiar
with
deploy
Keys.
They
enable
you
or
deployment
processes
to
have
credentials
to
access
the
code.
In
your
repository,
these
deploy
keys
are
managed
at
the
project
level.
B
We're
also
going
to
be
adding
initial
support
for
what
we
call
separation
of
duties.
Many
DevOps
aficionados
would
tell
you
that
we
don't
need
to
have
separate
permissions
or
roles
between
developers
and
operators
that
we
should
be
sharing
those
permissions,
but
lots
of
organizations
on
their
way
to
migrates
to
DevOps
need
to
continue
to
have
support
for
operators
not
being
able
to
touch
code
and
developers
not
being
able
to
touch
production
environments.
B
This
MVC
that
we'll
be
shipping
in
13.3
this
initial
step
to
allow
for
some
explicit
definition
of
those
separations
of
duties
in
the
early
stage.
We're
also
going
to
be
moving
to
group
based
releases
which
allow
you
to
have
combined
milestones
across
multiple
projects
under
one
release
item
and
as
well
as
triggering
webhooks
for
new
environments,
which
will
allow,
when
you're,
sharing
an
environment
across
multiple
projects,
to
have
one
kind
of
singular
release,
process
or
pipeline
across
all
of
those
projects.
B
We're
also
going
to
be
adding
enhanced
support
for
the
CI
CD
dashboards
and
those
dashboards
will
give
you
an
overview
of
how
your
release
processes
are
going
across
your
multiple
projects.
Another
cool
feature,
we're
adding,
is
a
UI
improvement
to
an
existing
feature
in
our
progressive
delivery
group.
Progressive
delivery
again
allows
you
to
more
rapidly
deploy
to
production
in
controlled
ways
in
this
case,
where
it's
it's
using
feature
flags
and
we've
recently
added
the
ability
to
add
strategies
to
your
feature
flag
rollout.
B
So
you
know
what
types
of
users
or
attributes
of
users
you
are
rolling
out
to
you
as
part
of
that
feature
flag.
We're
now
going
to
be
displaying
that
directly
in
the
view
of
the
feature
flag
itself,
so
you
can
know
if
I
check
that
box
on
the
feature
flag.
How
is
that
rollout
going
to
happen
and
what's
the
strategy
being
used
in
our
configure
stage,
we
have
frequently
encountered
I'm
going
to
show
my
configure
after
release
in
configure.
B
We've
frequently
encountered
concerns
about
using
our
existing
kubernetes
management
capabilities
because
they
require
both
direct
access
to
the
kubernetes
cluster.
So
typically
that
means
it
can't
be
behind
firewalls,
and
it
means
that
you
have
to
give
cluster
wide
credentials
to
get
lab
in
order
for
us
to
manage
this
cluster
as
part
of
our
13.3
release,
we're
going
to
be
rolling
out
what
we've
been
working
on
in
the
last
release,
which
is
a
kubernetes
agent.
This
agent
we're
going
to
be
rolling
out
to
github.com,
and
our
omnibus
deployments
enables
you
to
do
true.
B
Get-Ups
style
pull
based
deployments
to
kubernetes
clusters
without
having
to
give
up
the
security
that
you
would
want.
You
know
kind
of
more
production
in
enterprise
environment,
we're
also
going
to
be
adding
a
management
interface
for
the
terraform
state.
Back-End,
so
terraform
allows
you
to
by
hosting
your
terraform
stay
within
gitlab.
B
You
can
manage
the
environment
definition
that
terraform
is
defining
in
that
state
file,
where
we
want
to
give
you
more
capabilities
to
enable
multiple
state
files
per
project,
maybe
define
the
environment,
scope
or
project
similar
to
what
you
can
do
in
kubernetes
management,
where
you
can
attach
a
cluster
to
a
project
or
a
group.
We
want
to
give
you
the
same
capabilities
with
terraform
state
files,
also
in
terraform
in
our
terraform
improvements.
B
Our
infrastructure,
as
code
has
been
generating
these
reports
that
show
you
really
useful
reports
that
show
you
the
effect
of
a
merge
request
on
your
infrastructure
definition
right
there
in
the
merge
request.
Widget
we're
going
to
be
extending
that
support
to
allow
for
multiple
different
terraform
state
files
to
report
back.
B
This
would
be
the
case
if
you
were
had
really
clean
separation
between
environments
and
applications
in
your
terraform
definitions,
and
you
wanted
to
have
a
single,
mr,
that
might
adjust
many
of
them
in
our
monitor
stage,
we're
adding
not
just
the
ability
to
support
production
environments,
but
how
to
get
up
how
to
get
started
quickly
with
using
our
monitoring
tools.
This
is
a
really
cool
feature
that
allows
you
to
define
in
a
kind
of
WYSIWYG
editor
kind
of
way.
What
you
want.
B
Your
monitor,
dashboard
panel
to
look
like
and
quickly
see
what
that,
what
data
that
would
display
right
here
in
get
lab.
So
when
you're,
creating
new
dashboards,
there's
not
that
kind
of
inner
loop
of
waiting
to
see
what
the
dashboard
looks
like.
You
can
see
it
right
here
in
our
in
the
gait
lab
interface.
We're
also
going
to
be
adding.
B
We
recently
added
support
for
this
drop
down
here,
where
you
can
filter
an
entire
dashboard
by
a
specific
variable
and,
in
this
case
we're
using
pod
name
to
filter
and
I've
selected
the
ingres
pod,
and
it
gives
me
you
know
the
view
of
the
network
traffic,
but
I
could
use
any
other
pod.
This
shift
in
13.2,
where
I
will
ship
in
1302
later
this
week.
B
It
was
in
your
get
lab
interface
first
as
an
MVC,
for
this
incident
alert
incident
list
where
we'll
have
a
brand
new
menu
item,
for
instance
right
in
the
gate,
lab
application
and
show
an
overview
of
recently
created
incidents
within
get
lab,
including
important
information
like
when
it
was
created
and
who
the
assignee
is
and
whether
that's
been
published
to
your
status
page
we're
also
adding
the
ability
to
connect
a
run
book
to
an
alert.
So
when
an
alert
fires,
you
might
have
a
defined
process
for
how
to
respond
to
that
alert.
B
You
can
add
that
URL
directly
in
the
alert
definition
page
and
then
have
that
show
up
when
the
alert
fires
in
creates
an
alert
or
incident
for
your
team
to
respond
to
you
super
helpful
to
get
that
mean
time
to
resolution
as
short
as
possible.
So
you
have
all
the
information
you
need
when
responding
to
production
incidents.
B
Lastly,
when
you
view
your
alerts
themselves,
you
might
be
trying
to
decide
and
triage
whether
this
alert
should
be
an
incident
and
we're
going
to
be
adding
the
ability
to
see
the
log
view
that
pertains
to
that
specific
alert
right
in
the
alert
overview.
So
you
can
quickly
make
a
decision
about
whether
this
warrants
an
incident
or
not,
and
those
are
the
features
that
I'm
really
excited
about
and
again
with
the
theme
of
supporting
production
environments
throughout
the
gait
lab
application.
I'm
really
excited
for
13.3
I'll
hand
it
over
to
David
to
talk
about
secure.
C
Okay,
Pete
updates
for
secure
and
defend
first
was
secure.
We've
been
working
off
of
two
major
themes
for
the
first
half
of
the
year
versus
offline
environment,
support
at
a
couple,
more
updates
related
to
that.
Primarily,
the
team
is
working
on
number
two
of
our
goals,
which
are
ast
or
applications
very
testing
leadership,
kind
of
helping
with
stack
analysis.
C
First,
very
much
focused
on
the
application
security
testing
leadership
focus
on
building
out
UI,
so
you
don't
have
to
just
rely
on
the
animal
but
actually
be
able
to
look
through,
but
lots
of
other
things
are
going
on
the
team
as
well
I
highly
recommend
you
check
out
Taylor's
planning
issue.
You
can
see
our
priorities
focus
by
category
as
well
as
here
you
can
see
that
same
easy
to
use
configuration.
C
The
other
thing
that
the
team
is
very
much
focused
on
is
our
open
source
stewardship
and
we're
beginning
to
move
more
of
our
scanners
down
to
court.
A
couple
releases
ago
we
talked
about
rails
support
and
this
release.
He
has
several
scanners
coming
down
to
core
on
the
dynamic
analysis,
so
dynamic
analysis
is
very
much
focused
on
getting
that's
to
complete
as
part
of
our
application,
security,
testing,
leadership
and
example.
That
is
giving
you
profiles
that
you
can
use
as
part
of
your
scan
and
so
within
the
13.3
release.
C
You're
gonna
be
able
to
save
site
profiles
and
reviews,
and
in
here
you
can
get
a
name
to
find
what
the
target
is.
If
you
want
to
run
not
a
passive
skin
but
an
actual
security
skin
against
it,
you
can
validate
your
domain,
so
we
can
use
it
as
well
as
all
the
other
types
of
settings
you
would
want
as
part
of
the
site
profile,
and
then
you
can
save
that
in
to
your
conversion.
C
On
the
composition,
analysis
team
there
again
focused
on
those
two
major
themes
for
them,
primarily
on
the
offline
support
example
that
mr.
lease
is
bringing
our
PHP
license.
Compliance
to
make
it
available
offline
as
well.
I
wanted
a
highly
stress
at
this
point
that
working
offline
environment
is
very
important.
We've
had
a
lot
of
customers
who
had
switched
over
to
get
lab
at
support,
because
traditional
security
tools
are
requiring
them
to
have
that
environment
connected
the
internet,
and
we
want
to
be
a
partner
with
you
as
part
of
doing
your
security
testing.
C
Next,
with
regards
to
fuzzing-
and
yes,
I
want
to
say,
with
a
big
smile
that
we
have
fuzz
testing
now
and
I
know.
That
was
something
we
didn't
have
a
couple
releases
ago,
and
so
we
have
our
initial
release
of
our
coverage.
Guided
fuzzer
available
on
here,
I'm
showing
you
both
Direction
items
are
deliverable
items.
The
team's
committed
to
is
all
some
stretch
items
because
we're
ahead
of
schedule
with
our
API
fuzzing,
as
well
as
we're
looking
at
it.
C
That
is
a
stretchable
for
August,
with
a
commitment
of
getting
it
out
in
September
timeframe,
of
course,
coverage
credit
fuzzing.
First,
we
want
to
be
able
to
allow
you
to
reuse
corpus
data
that
corpus
data
is
what
the
scanner
learned
about
your
environment
to
then
trigger
future
scans.
To
leverage
that
knowledge.
C
You
can
see
that
here
in
the
example
yellow
file,
where
you
can
now
point
into
the
corpus
you
want
to
use
next
with
regards
to
the
API
like
buzzing,
we're
looking
at
bringing
support
for
API,
open,
API,
v2
definition,
so
you
can
take
that
definition,
give
it
to
the
scanner.
The
scanners
now
gonna
know
what
to
fuzz
as
part
of
API
and
test
it
for
vulnerabilities
it'll
be
integrated
just
like
the
coverage
guide.
C
Exposure
was
first
not
available
on
the
dashboard
or
the
merge
request
view
yet,
but
we'll
give
a
little
within
the
pipeline
view
with
the
goal
september/october
getting
both
I'm
available
in
the
merger.
Present
you
within
the
dashboards
and
so
forth,
and
then
finally,
on
the
secure
side
is
our
threatened
sites
team.
They
were
moved
from
defend
over
to
secure
because
they're
primarily
focused
on
vulnerability
management
of
secure
findings.
C
There's
two
really
cool
things
are
coming
out
as
well:
I,
really
like
the
first
one
here,
not
that
I
say
I,
don't
like
the
second
one,
but
this
is
allow
you
to
take
already
created
issues
and
attach
your
vulnerability
findings.
So
now
you
can
begin
to
have
that
cause
and
effect
root,
cause
analysis
attached
to
the
finding
itself.
Also,
we
generally
don't
talk
about
things
that
are
just
in
design
as
part
of
the
kickoff,
but
we're
really
excited
to
kick
off
the
beginning
of
our
security
dashboard
restructuring.
C
It's
gonna
allow
us
to
provide
you
a
lot
more
content,
an
example
this
this
is
the
mock-up,
the
team's
working
off
of
the
security
we
rolled
out.
We
include
the
widgets
that
are
on
the
group
dashboard
today,
so
that
current
project
status,
as
well
as
poor
mobility
trends
over
time,
but
this
is
enabling
us
to
come
in
and
now
allow
the
scan
teams
be
able
to
create
their
own
widgets
as
well
and
have
them
added
to
the
dashboard
and
give
you
a
true
dashboard
experience
for
your
security
findings.
C
The
second
part
is
that
long
list
of
vulnerabilities
that
were
on
the
left-hand
side
will
now
be
under
faller,
though
they
report,
you
know
that
same
ability
to
drill
down
into
the
results.
Well,
I
personally
like
about
this,
though,
is
because
we
have
more
room
now
we
can
add
in
things
like
the
identifier
for
the
vulnerability,
the
secatur
that
found
it
and
so
forth.
This
is
really
taking
the
security
findings
and
giving
you
actionable
next
steps.
So
that
way
you
can
resolve
and
reduce
your
risk.
I
always
scratch
the
surface.
C
C
Sam
has
a
really
great
priorities.
Page.
You
want
to
check
it
out,
I
highly
recommend
it.
It
can
show
you
what
we're
working
on
across
the
themes,
as
well
as
the
current
status
of
those
items
and
to
drill
into
this
release.
The
one
thing
that
is
very
interesting,
we're
being
add,
point-and-click
GUI,
is
for
the
policies
is
about.
We've
talked
about
this
loosely
when
it
first
showed
up
while,
but
now
it's
getting
a
lot
more
complex
and
a
lot
more
feature-rich.
C
So,
to
kind
of
show
you
this,
this
is
the
common
view,
you'd
see
for
things
like
a
Cisco
firewall
or
Palo
Alto
Networks
firewall.
We
want
you
to
be
able
to
still
type
out
configurations
like
you.
Could
you
know
the
products?
What
we
also
want
to
give
you
a
nice
point-and-click
experience
as
well,
and
this
is
great
for
being
able
to
think
about
your
role
set
in
English
and
the
terminology
in
which
you
write
a
sentence.
Oh,
you
can
see
that
here
with
you
know.
C
If
network
traffic
is
inbound
to
this
container,
I
want
to
apply
this
mall
and
that's
very,
very
cool,
and
this
is
the
thing
that's
going
to
continue
to
grow,
not
just
for
container
network
security
of
our
our
container
host
security,
which
just
recently
launched
the
venn
pages,
had
a
major
overhaul
to
it.
So
if
you've
not
put
that
recently
I
highly
recommend,
you
check
it
out,
it
goes
through
all
of
our
long-term
themes.
Our
current
plans,
as
well
as
some
status
as
to
where
we
are
delivering
to
our
goals.
C
D
Thanks
David,
so
like
others,
we
have
a
lot
of
really
exciting
features
coming
in
this
release
or
plan
for
this
release,
and
so
please
do
check
up
the
videos
on
our
enablement
section
page
on
the
kickoff
page.
You
can
see
those
here,
but
I
want
to
highlight
primarily
two
items
that
come
in
to
two
themes:
one
is
improving
the
performance
and
scalability
of
gitlab,
but
also
to
help
to
ease
the
operational
task
of
running
a
club
instance
as
well
as
also
supporting
some
new
deployment
targets
as
well.
So,
let's
jump
into
it.
D
The
first
one
is
that
we
want
to
add
support
for
dynamic,
resizing
in
to
get
lab
itself.
When
we
looked
at
the
opportunities
for
improving
the
performance
of
gitlab,
our
front
end
team
quickly
found
out
that
for
many
pages
that
have
a
lot
of
for
simple
avatars.
This
is
the
number
one
thing
that
we
can
do
to
help
improve
the
speed
of
our
pages.
D
Similarly,
we're
also
going
through
and
looking
for
cash
equal
calls,
the
team
found
these
and
in
particularly
found
that
they
were
pretty
impactful
or
performance
I'm,
recommending
that
we
treat
them
similar
to
what's
kind
of
called
n
plus-1
queries.
The
net-net
here
is
at
the
consume
memory
and
they
slow
down
performance.
There
see
some
results
of
this.
D
We
actually
have
a
work
in
progress
branch
right
now
and
we
dis
initial
testing,
and
you
can
see
here
that
for
a
particular
call
the
top
offender
we
were
able
to
reduce
the
amount
of
memory
allocated
by
half
and
the
overall
time
it
takes
to
complete.
The
operation
was
reduced
by
75%.
So
again,
some
pretty
nice
improvements
here,
and
this
is
just
the
one
top
offender
we'll
go
through
and
kind
of
work
away
them
to
list
as
well
over
the
next
couple
of
releases,
but
some
really
nice
work.
I
was
done
there.
D
Similarly,
on
the
search
side
of
things,
we're
also
looking
to
address
slow
search
performance
when
using
an
advanced
mobile
search
on
large
groups,
and
so
as
groups
get
larger
the
time
it
takes
to
perform
a
search
goes
up
kind
of
linearly,
and
so
we're
looking
to
solve
that
problem
going
forward
to
help
make
sure
our
search
responsiveness
is
as
fast
as
it
possibly
can
be,
transitioning
slowly
over
to
partitioning
this
can
help
performance,
but
also
helps
to
increase
our
scalability
of
the
getline
platform
as
well.
Who
looked
at
our
last
milestone?
D
We
were
working
on
implemented
missioning
for
our
audit
event
stable
and
we're
wrapping
that
up
here
well
should
be
rolling
out.
If
not
now,
then
shortly
on
github.com
and
we'll
be
moving
on
over
to
our
events
table,
the
events
table
essentially
tracks
all
the
activity
by
all
users
that
powers
your
profile.
This
is
a
lot
of
content
in
there.
We
want
to
keep
that
content.
D
We
don't
want
to
delete
it,
and
so,
when
I
go
through
and
start
to
partition
that
content
on
the
database
side,
we
also
are
working
to
add
support
for
Postgres
12
post
press
12.
Aside
from
being
the
next
new
release,
also
includes
a
number
of
performance
enhancements.
Last
release
with
PG
last
major
release
of
PG
11.
We
saw
about
8%
performance
increased
across
the
board,
but
PG
12
probably
has
similar,
but
also
some
really
key
improvements
for
partitioning.
D
So
with
that
that's
a
kind
of
focus
on
the
performance
side
of
things.
Moving
on
to
the
operational
and
deployment
targets,
we're
going
to
go
ahead
and
add
support
for
official
packages
for
Army
64,
this
a
platform
that
we
see
growing
demand
for.
We
want
to
provide
official
easy-to-use
packages
for
it
and
we're
also
looking
to
add
support
for
Red
Hat
Red
Hat
OpenShift
by
means
of
an
official
operator.
D
Finally,
working
on
a
couple
other
areas
here
away
from
the
twin
targets
to
endzone.
To
call
out
one
is
that
we
wanted
to
improve
the
relevance
for
best
global
search
as
well.
The
team
noticed
that
we're
actually
utilizing
updated
acts
as
the
only
sort
option,
so
we're
actually
using
relevance
as
a
sort
order,
so
we're
fixing
that
and
we'll
be
continuing
to
also
add
support
for
letting
you
choose
what
sorting
option
you
want
in
the
near
future
here.
D
But
relevance
seemed
like
a
better
option
than
simply
date
when
it
was
last
utilized
and
finally,
we're
also
continuing
to
work
on
adding
an
additional
data
types
for
geo
and
so
we're
going
through
and
adding
support
for
packaged
files.
It
just
missed
the
fruity
not
to
official
release
and
so
that'll
begin
13.3
and
we'll
be
moving
on
over
to
also
including
snipper
application,
as
we
look
to
add
support
for
all
data
types
in
geo,
so
that
when
you
do
failover,
when
you
have
a
G
replica
geo
node,
your
content
is
there
and
can
be
utilized.
E
I
share
my
screen
and
we'll
get
going
so
I'm
going
to
talk
about
what
the
team's
planned
for
13-3
in
the
depth
section.
As
a
quick
reminder,
the
dev
section
is
the
first
three
stages
of
the
develops
title,
so
that's
managed
plan
and
create
and
I've
grouped
the
issues
that
we
planned
into
kind
of
three
big
thematic
buckets.
The
first
of
these
is
product
team
efficiency,
so
making
probably
teams
faster
and
more
efficient
and
so
to
get
level
in
13
2.
E
We
are
releasing
the
ability
to
assign
an
issue
to
what
we
call
an
iteration,
so
this
will
essentially
allow
product
teams
to
assign
an
issue
to
a
longer
running
milestone,
but
then
attach
them
to
shorter
running
iteration
sprints.
If
you
will
so
like
a
one
or
two
week,
sprint,
which
will
really
help
people
follow.
Whatever
methodologies
is
using
the
organization
and
in
13-3,
we're
going
to
be
focused
on
is
providing
a
little
bit
more
analytics
and
insight
into
the
iteration
process.
E
So
this
this
screen
right
here
is
really
what
we're
going
to
be
shipping
in
13-3
the
ability
to
see
it
burn
down,
burn
up
chart
as
well
as
this
issue
and
more
widget
below,
and
the
ability
to
group
them
by
labels
assignee
of
ethics.
So
it's
providing
more
visibility
and
usefulness
into
the
iteration
feature.
E
This
is
something
that
we
at
get
lot
of
use
to
understand
how
we
efficient
our
engineering
organization
is
being,
and
it's
something
that
we
use
a
third-party
tool
for
data
collection
and
visualization,
but
we
think
this
should
be
front
and
center
inside
of
github,
so
that
our
teams
can
take
advantage
of
it,
but
also
that
your
teams
can
take
advantage
of
it
as
well.
So
looking
forward
to
what
we're
going
to
call
merge
request,
analytics,
we've
made
a
bunch
of
great
improvements
to
our
design
management
features
over
the
past
few
releases.
E
But
the
one
thing
is
looking
through
is
reorder.
Your
designs,
they
always
show
up
in
the
date
that
they
were
uploaded
and
what
this
can
kind
of
lead
to
is
a
problem
like
this,
where
you
want
to
click
through
a
page,
four
screens
but
they're
out
of
order,
because
the
flow
isn't
isn't
there
and
because
you
upload
them
in
an
order
that
didn't
really
make
sense,
and
so
we're
going
to
allow
the
ability
for
you
to
reorder
these
so
that
when
you
click
through,
you
can
easily
show
a
flow
or
a
specific
path
through
UI.
E
And
so
there
should
be
a
really
nice
improvement
to
our
design
management
features.
We're
also
going
to
support,
selecting
a
code
owners
section
to
be
a
required
approval
rule.
Currently
you
can
do
this
for
a
user
or
a
group,
and
over
the
past
few
releases,
we
we,
we
added
code
owners
sections,
and
so
now
you
can
select
the
code
under
section
to
be
a
required,
mr
approval
rule,
which
would
really
help
streamline
that
process
of
defining
a
code
owner
as
well
as
then
linking
that
code
ownership
to
an
mr
approval
rule
in
thirteen
two.
E
You
know
that
a
spacing
issue
or
a
typo
can
really
hamper
your
output,
and
so
we
wouldn't
allow
the
ability
to
essentially
define
a
JSON
schema
and
then
allowing
you
to
validate
whatever
you're.
Writing
against
that
schema
right
in
the
web.
Ide,
making
the
process
a
little
bit
more
streamlined
and
there's
an
example.
How
we're
going
to
use
this
I
get
loud
is
the
release
post
so
we're
going
to
upload
a
release
post
schema.
We
have
a
release
post,
that's
delivered
every
single
month,
we're
a
lot.
E
Fifty
product
team
members
collaborate
on
that
post
and
this
will
really
help
to
kind
of
check
the
spacing
and
the
wording
and
making
sure
that
all
the
blocks
are
properly
formatted
and
then,
lastly,
for
product
efficiency,
we
focus
a
lot
on
devs
and
product
managers,
but
one
team
that
is
really
important
in
the
product
creation
process
is
the
quality
team
and
we've
been
talking
about
quality
management
inside
of
get
lab
for
a
long
time.
I'm
really
excited
that
we're
finally
scheduling
our
minimal,
viable
change
for
quality
management
and
13-3.
E
What
this
will
look
like
is
essentially
a
programmatic
way
to
create
epics
and
issues
and
link
those
to
what
we
call
test
sessions
test,
Suites
and
tests.
So
it's
gonna
be
a
pretty
simple
MVC,
but
we're
gonna,
obviously
utilize
this
Foundation
to
make
a
more
robust
quality
management
framework
inside
of
get
lab,
so
I'm
really
excited
for
them.
E
Our
second
theme
is
access
and
compliance,
and
this
will
probably
be
a
theme
for
the
rest
of
the
year.
So
it's
very
very
important
to
us.
The
first
issue
I
wanna
highlight,
is
setting
a
default
rule
for
SSO
and
get
lab
comm.
Currently,
if
us
and
so
and
ticket
lab
column
is
a
top-level
group
here,
you
are
created
as
a
guest
which
in
some
cases
is
too
permissive
and
in
some
cases
it's
not
permissive
enough.
E
So
we
want
to
provide
the
ability
to
allow
for
a
default
role
to
be
set
whenever
someone
SSO
is
in,
so
that
they
can
be
made
a
different
role
or
they
can
be
given
no
access
at
all.
We
should
really
help
with
managing
those
those
groups
on
get
love
comm
and
for
users
SSO
Union
we're
also
going
to
allow
an
option
to
federate
your
last
scene
and
JIRA
account
in
ticket
lab.
This
is
useful
for
two
reasons.
E
The
first
is,
if
you're
using
your
Atlassian
account
for
your
source
of
truth
them
they'll
be
able
to
use,
get
lab
powered
by
that
account.
The
second
reason
is:
we've
been
focusing
on
a
deeper
integration
with
Atlassian's
JIRA,
and
this
will
allow
us
to
deepen
that
integration
by
allowing
you
to
take
several
actions
against
your
issues
right
inside
a
get
lab
and
then
be
linked,
how
those
actions
link
back
to
your
JIRA
user
accounts
as
well.
E
So
that
should
be
really
really
useful
and
excited
to
see
that
work
land
we're
also
going
to
make
some
improvements
to
personal
access
tokens
we're
going
to
allow
admins
the
ability
to
revoke
those
tokens
via
an
API,
and
then
we're
also
going
to
provide
an
additional
warning
if
those
personal
access
tokens
have
expired.
We
already
do
provide
a
notification
that
your
token
will
expire
within
seven
days,
but
then
there's
no
further
notification
job
and
so
we're
going
to
provide
an
additional
email
that
says:
hey
your
token
has
expired.
E
You
may
want
to
create
a
new
one
or
check
it
out
in
the
personal
access
token
section,
we're
going
to
continue
iterating
on
our
group
compliance
dashboard
feature
by
adding
a
source
and
destination
branch
data
to
that
dashboard.
This
will
help
you
quickly
understand
if
something
kind
of
went
out
of
order
in
your
deployment
or
merge
process.
E
I'm
really
focusing
that
change
management
look
flow
to
make
sure
that
branches
were
merged
to
the
right
branch
in
the
right
place
and
in
the
right
order,
and
so
a
nice
iteration
here
to
our
group
compliance
dashboard
and
then,
lastly,
on
compliance,
we're
going
to
we're
going
to
ship
our
minimal
Bible
change
for
chain
of
custody
reporting,
and
this
will
simply
look
like
a
an
export
job
in
the
compliance
dashboard.
Next
to
each
project,
there
will
be
a
button.
They'll
provide
a
CSV
of
all
commits
the
table.
E
Will
look
directionally
like
this
I,
don't
know
if
it'll
look
exactly
like
this
upon
CSV
export,
but
will
essentially
show
the
author
the
merge
request
the
commit
Shah
as
well
as
some
other
information,
which
will
be
really
helpful
to
just
hand
to
an
auditor
to
prove
that
code
was
only
touched
by
certain
people
and
via
whatever
compliance
regiment.
That
organization
was
held
to
so
really
excited
for
these
great
improvements
here
and
then.
E
Lastly,
we
are
going
to
focus
on
just
better
acute
lab
management
in
general,
and
the
first
way
we're
going
to
do
this
is
just
by
providing
some
better
mechanisms
and
hooks
to
clean
up
your
repository.
So
whenever
you
run
the
get
GC
command,
we
want
to
train
all
loose
objects
immediately
in
the
repo,
and
we
also
want
to
do
the
same
thing
for
unreferenced
LFS
objects.
So
this
should
help
keep
your
repository
size
manageable
and
make
sure
that
those
objects
that
aren't
doing
reference
anymore,
aren't
in
that
repository
anymore
and
then.
E
Similarly,
when
you
do
that,
we
want
to
update
those
repository
stats
immediately,
so
that
you
can
see
exactly
how
much
storage
repository
is
taking
up.
I
mentioned
this
last
time,
but
it's
important
enough
to
highlight
again
we're
gonna
continue.
Adding
concurrency
support.
Forget
repository
backups
right
now.
This
is
a
serialized
process.
Warning
obviously
make
this
parallel,
so
that
more
threads
can
run
in
parallel,
which
will
basically
make
that
backup
time
a
lot
quicker
and
then,
as
always,
we're
continuing
our
work
on
improving
get
early.
E
Cluster
Gili
cluster
is
a
highly
available
Gidley
architecture,
and
what
we're
going
to
do
in
this
release
is,
by
start
to
use
a
corn-based
voting
strategy.
What
does
this
mean?
Well,
what
it
means
is
in
order
for
us
to
enable
strong
consistency,
we're
requiring
all
nodes
to
agree
that
a
right
happened,
but
if
a
node
goes
down,
the
net
node
can
never
agree,
which
will
basically
lead
to
your
giddily
cluster
being
offline
and
unavailable.
E
Introducing
another
single
point
of
failure,
which
the
entire
point
of
giddily
cluster
was
to
get
away
from
in
the
first
place,
so
we're
going
to
start
using
a
quorum
based
loading
strategy
so
that
if
a
single
node
goes
down,
a
quorum
can
still
be
maintained
and
that
the
right
can
be
accepted.
As
always,
this
is
just
a
small
section
of
the
amazing
features
that
the
dev
section
is
going
to
deliver
in
13-3,
and
it's
always
going
to
kick
off
pages,
see
they're
instantly
a
new
over
to
you.
Thank.