►
From YouTube: 15.7 Monthly Release Kickoff (Public Livestream)
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
Hey
everyone
Welcome
to
our
release,
kickoff
for
15.7.
My
name
is
David
DeSanto
and
I
lead
the
product
team
here
at
gitlab
I
will
be
your
MC
on
today's
live
stream.
I'm
also
joined
today
by
some
of
the
team
members
of
our
awesome
product
team.
They
are
in
order
in
which
they'll
be
presenting.
Hillary
Benson
director
of
products
will
be
providing
our
updates
for
the
sex
section.
A
Taylor
McCaslin
group
product
manager
will
provide
our
updates
for
the
data
science
section,
James,
heimbach
principal
product
manager,
on
the
verify
team
we'll
be
providing
updates
for
our
op
section.
Josh
Lambert
director
of
products
will
be
giving
us
updates
on
enablement
and
bringing
us
home
will
be
Erika.
Lewinsky
director
of
product
we'll
be
covering
our
Dev
section.
A
At
gitlab,
we're
focused
on
delivering
value
iteratively,
with
a
focus
on
our
fla23
or
calendar
year.
2022
product
investment
themes
they
are
get
lab
posted
first,
give
up
hosted.
First,
does
not
mean
to
have
hosted
only
gitlab.com
is
the
largest
self
hosted
or
self-managed
deployment,
and
we
know
if
we
can
meet
the
needs
of
gitlab.com,
we
can
meet
the
needs
of
our
users.
A
Our
second
theme
is
improved
key
workflow
usability.
This
theme
is
focused
on
improving
the
workflows
most
critical
to
our
users.
This
team
is
focused
on
improving
things
like
merge,
request
experience
where
we
know.
If
we
can
get
this
right,
we
can
drive
multi-stage
adoption
and
that
makes
scale
out
more
valuable
to
you
and
our
final
theme
is
extend
our
lead,
NCI,
CD
devops
doesn't
stop
till
applications
are
in
production
and
we
want
to
make
sure
that's
as
seamless
and
frictionless
as
possible
before
I
head
over
to
Hillary.
To
kick
us
off.
A
We
do
have
our
typical
short
public
service
announcement
on
this
live
stream,
we'll
be
discussing
our
product
roadmap,
which
includes
upcoming
features
and
functionality.
It's
important
to
note
that
the
information
presented
on
this
live
stream
is
for
informational
purposes.
Only
please
do
not
rely
on
it
for
purchasing
or
planning
purposes.
A
We
plan
very
ambitiously
here
at
gitlab
and
all
details
discussed
on
this
live
streamer
are
subject
to
change.
The
topic
of
any
products
features
and
functionality
remain
at
the
sole
discussion
of
gitlab.
Okay.
So
with
that
out
of
the
way,
it's
time
for
the
fun
stuff,
so
Hillary,
please
kick
us
off
with
the
sex
section.
B
A
B
So
to
kick
us
off
here,
the
sex
section
again
this
this
Milestone
is
focused
on
our
investment
theme
to
improve
key
workflow
usability.
So
the
composition,
analysis
team
is
focused
on
replacing
the
underlying
technology
behind
our
license
compliance
capabilities.
We
don't
anticipate
shipping
this
this
Milestone,
but
we'll
make
substantial
progress
on
this
project.
B
The
static
analysis
team
is
working
on
an
effortless
Milestone
to
make
it
easier
for
us
to
provide
higher
quality
security
findings
so,
for
instance,
among
other
things,
this
will
make
it
easier
for
us
to
drop
noisy
rules
from
our
analyzers
without
creating
confusion
for
users
when
they
go
and
look
at
the
vulnerability
report.
So
today,
if
we
drop
a
noisy
rule
previously
reported
findings
from
that
rule
will
be
tagged
as
no
longer
detected,
because
the
rules
now
off,
but
right
now,
it's
not
clear
to
the
user.
Why?
B
Those
findings
are
no
longer
detected,
so
they
don't
have
a
way
of
easily
attracting
what
happens
so
we're
working
to
improve
that
experience.
The
dynamic
analysis
team
is
working
on
two
projects.
This
Milestone
the
first
is
to
add
support
for
graphql
in
on-demand
scanning,
and
the
second
is
actually
a
really
exciting
milestone
for
us.
So
we're
going
to
be
moving
our
browser-based
Dash
capabilities
to
General
availability
of
this
Milestone,
the
first
GA
release
of
browser-based
gas
is
going
to
include
our
crawler,
our
auth
service
and
our
passive
vulnerability
checks.
B
So
the
main
portion
of
browser-based
Das
that
will
not
move
to
GA
this
Milestone
are
our
active
checks,
we're
still
working
on
getting
active
checks
ready,
so
those
will
come
in
a
future
release,
but
the
dynamic
analysis
team
has
been
working
really
hard
to
deliver
this
for
some
time
now,
and
the
core
engine
and
passive
checks
are
fully
ready.
This
represents
a
really
great
set
of
improvements
for
our
users
that
will
provide
you
know
a
vastly
improved
experience
over
our
old
desk
scanning
engine
spread.
B
And
finally,
the
compliance
team
has
a
couple
projects
that
they're
looking
to
close
out
this
Milestone.
The
first
is
to
extend
support
for
the
chain
of
custody
report.
So
today
this
report
provides
a
list
of
all
merge
commits
in
a
group
with
this
change.
That
list
will
include
all
commits,
not
just
merge,
commits
and
then
they'll
also
be
working
on,
adding
full
support
for
the
ability
to
block
an
MR
from
merging
if
that
Mr
has
failed
status
checks.
B
So
today
the
ability
to
block
merging
is
available
only
via
the
API
and
users
have
to
enable
it
with
a
feature
flag.
So
the
idea
here
is
to
add
first
class
support
for
blocking
Bridges,
including
UI
configuration,
and
that
is
it
the
sex
section
with
that
I'll
turn
it
over
to
Taylor
to
take
us
through
upcoming
work
in
data
science.
C
Awesome
thanks
Hillary,
so
my
name
is
Taylor
McCaslin
I'm
going
to
talk
you
through
our
data
science
section.
This
includes
our
anti-abuse
group,
so
they're
focused
on
protecting
git
lab
instances
from
user
behavior
that
disrupts
productivity
and
an
organization's
ability
to
build
and
deploy
code.
So
in
that
mind
we're
looking
at
improving
the
abuse
mechanism
with
the
abuse
recording
mechanism
within
gitlab
today,
I'm
submitting
an
abusive
report
goes
to
an
admin
and
kind
of
just
disappears
with
little
context
about
what's
happening
in
this
new
design.
C
Basically,
when
you
choose
to
report
admin
repeat
report
abuse
to
admins
you'll
get
a
a
detailed
form
to
explain
why
you're
reporting
that
content
and
we've
improved
the
ux
of
that
entire
experience
to
help
keep
activity
within
gitlab,
appropriate
and
and
non-abusive
we're
also
in
the
process
of
rolling
out
to
sell
posted
users,
get
abuse
rate
limiting
so
basically
preventing
insiders
from
downloading
large
numbers
of
repositories.
C
This
is
a
configurable
setting,
so
you
can
control
how
many
repositories
you
want
to
allow
your
users
to
download
this
is
a
common
Insider
threat
risk
where
someone
you
know
gets
released
from
the
company
goes
and
downloads.
All
your
resources
code
and
dumps
that
on
the
internet,
this
can
help
protect
against
that.
So
those
are
a
few
of
the
highlights
that
we're
looking
for
particularly
around
our
git
lab,
hosted
first
product
theme
to
support
anti-abuse
use
cases.
C
This
next
upcoming
Milestone
we're
also
adding
support
in
partnership
with
the
Ops
Team
to
enable
SAS,
GPU
Runners,
so
we're
looking
at
offering
an
N1
standard
for
NVIDIA
Tesla
T4
GPU,
with
availability
from
gcp
to
our
SAS
availability,
basically
able
to
tab
tag
a
job
as
GPU
and
get
this
high
power
compute
for
your
Runners.
Finally,
we're
also
as
part
of
our
AI
or
as
part
of
our
incubation
engineering,
we're
working
on
an
NVC
integration
of
ml
flow.
This
will
support
ml
experiment,
tracking
and
metadata
tracking.
C
This
is
an
experimental
feature,
but
we're
hopeful
and
excited
about
what
this
offers
to
customers
and
then
finally,
on
our
applied
mlfront
we're
also
exploring
what
we're
calling
code
completion.
Basically,
the
ability
to
generate
code
suggestions,
we're
releasing
our
first
internal
POC
of
this
tool
in
the
upcoming
weeks
and
we'll
have
much
more
to
say
about
this
in
the
future.
So
that
is
a
quick
overview
of
our
data
science
plans
and
now
I'll
hand
it
over
to
James
to
talk
about
Ops.
D
Unmute
awesome
thanks:
Taylor,
hey
everyone,
I'm
James,
eibach
principal
product
manager
in
the
app
section
at
gitlab.
The
app
section
is
comprised
of
the
five
stages,
verify
package,
release,
configure
and
monitor,
and
our
vision
is
to
help
orgs
rapidly
adopt
Ops
best
practices
through
a
great
developer
experience
and
let
those
organizations
achieve
efficiency
and
safety
through
Enterprise
controls.
D
So
each
group
within
Ops
has
a
number
of
great
features
that
they
have
done
or
that
they're
going
to
be
working
on
and
Bug
fixes
through
15
7,
as
well
as
a
focus
on
maintenance
issues
to
ensure
reliability
and
stability
of
the
platform
and
I'll
be
highlighting
a
few
notable
features,
starting
with
our
theme
of
improving
product
usability
and
so
starting
with
the
runner
team,
they've
heard
and
really
throughout
all
of
verify.
We've
heard
from
customers
that
it
could
be
hard
to
troubleshoot
what
is
causing
a
job
and
pipeline
to
be
slowed.
D
So
one
part
of
that
that
the
runner
team
has
really
been
able
to
focus
in
on
is
surfacing
the
time
it
takes
for
an
instance
Runner
to
pick
up
a
job.
So
in
this
issue
providing
estimated
wait
times,
for
instance
Runners,
the
team
will
be
creating
an
interface
to
show
the
average
time
it
takes
for
a
runner
by
tag
to
pick
up
a
job
so
that
platform
Engineers,
who
are
looking
to
answer
the
question
of.
Why
did
this
pipeline?
D
Take
so
long,
can
eliminate
or
point
at
the
runner
being
a
root
cause
for
a
contributing
factor
to
that
next
up
we
have
the
release
team
so
previously
released
team
had
introduced
multi-access
levels
and
deployment
approvals
which
can
be
set
up
through
the
gitlab
API
that
allowed
teams
to
achieve
a
separation
of
Duty
so
that
different
folks
could
approve
and
different
folks
could
deploy
releases.
But
there
was
no
really
easy
way
to
review
what
was
already
set
up
within
the
UI
or
to
change
those
things.
D
D
The
first
is
around
adding
and
removing
data
sources,
so
today
data
sources
are
configured
automatically
by
the
back
end,
only
for
our
own
implementations,
which
can
be
limiting
to
users
if
they
can't-
or
they
just
don't
want
to
use
the
back
ends
that
we
provide.
So,
for
instance,
if
a
company
has
a
working
High
scale
metric
system
that
they
can't
bring
with
them
to
get
Labs
observability
tools,
they're
not
going
to
be
able
to
use
those
tools.
D
The
other
exciting
observability
feature
that
I
wanted
to
talk
about
was
managing
dashboards
in
Project
repositories
as
code.
So
we
know
that
users
may
want
to
keep
those
dashboards
for
a
project
close
to
the
project
since
oftentimes
the
user.
Who's
working
on
new
functionality
is
also
the
one
who's
building
out
that
dashboard,
keeping
those
things
in
different
places
or
different
systems
can
discourage,
discourage
simultaneous
updates
and
that,
in
turn,
limits
the
team's
ability
to
learn
how
those
changes
that
they're
making
are
impacting
their
service.
D
Moving
on
to
extending
our
lead
in
CI
CD
back
to
the
runner
team
and
we've
heard
from
users
that
Secrets
can
accidentally
be
linked
into
job
logs,
sometimes
on
purpose,
after
which,
if
you
have
a
leak,
you're,
often
forced
to
rotate
those
Secrets
everywhere.
That's
time
consuming
and
just
super
annoying
for
an
organization.
So
we
have
a
proposal
to
find
resolved,
Vault
secrets
and
mask
them
within
the
job
logs.
So
users
who
try
to
say
cat
a
validated
secret
or
into
the
log
to
check
it
can't
accidentally
do
that
or
even
on
purpose.
D
Next
is
a
small
win
and
a
quick
win
for
the
configure
team
and
that's
allowing
agent
cicd
access
sharing
within
a
personal
name
space,
so
they're
working
on
this
to
set
up
the
same
experience
for
someone
who
wants
to
try
out
the
CI
CD
access
with
the
gitlab
agent,
just
within
a
personal
namespace.
So
for
users
who
are
trialing
the
cicd
tunnel
functionality
within
a
personal
namespace,
it's
a
really
different
experience
than
what
they
might
be
actually
setting
up
within
their
organization.
D
So
if
you
have
a
pipeline
engineer
or
a
devops
engineer,
who's
trialing,
something
within
gitlab
to
see
if
they
want
to
bring
it
to
the
whole
org
right
now,
there's
a
lot
of
overhead
that
they
have
to
go
through
to
get
that
set
up
and
just
to
see
if
it's
working.
So
this
makes
that
experience
a
lot
more
similar
to
what
they
would
have
if
it
was
fully
deployed
just
within
their
personal
namespace.
D
The
last
big
feature
I
want
to
talk
about
is
from
our
package
team
and
that's
the
RPM
package
manager
MVC.
So
the
package
team
has
been
working
on
this
NPC
for
a
while,
and
we
at
gitlab
are
especially
excited
about
this,
since
our
own
gitlab
Runner
is
an
RPM,
and
so
this
is
going
to
help
us
reduce
our
complexity
of
our
own
release
process,
as
well
as
serve
the
need
for
customers,
also
creating
RPMs,
who
can't
use
the
gitlab
package
manager.
D
Today,
the
NBC,
as
it
rolls
out,
will
allow
users
to
push
and
pull
RPM
packages
through
the
API
and
I
know.
The
team
is
already
starting
to
think
about
enhancements.
On
top
of
that,
and
the
last
thing
I
wanted
to
highlight,
isn't
a
feature
per
se,
but
a
change
in
something
that
one
of
the
other
observability
groups
did
in
respond
and
that's
in
their
planning
issue.
They've
created
this
seeking
Community
contribution.
D
Compute
excuse
me
seeking
Community
contribution
section,
so
these
are
issues
that
are
well
scoped,
with
solid,
solid
Improvement
guides
to
them
and
a
great
place
if
you're
looking
to
contribute
to
gitlab,
to
take
a
look
and
pick
up
an
issue
so
that
you
can
contribute
back
to
the
platform
and
with
that
I'll
hand
it
off
to
Josh
for
the
enablement
section.
E
Thanks
James,
those
are
some
exciting
improvements
and
I
get
to
talk
about
enablement,
as
James
mentioned.
Let
me
go
ahead
and
share
my
screen
here
and
we'll
go
we'll
go
from
there.
So
hopefully
that's
coming
through
okay,
but
we'll
kick
off
the
name
of
it.
As
always,
we
have
our
videos
for
all
of
our
groups.
Please,
today,
I
think
you
know,
please
do
look
through
those
if
you
have
any
further
interest
in
these
areas.
E
E
These
are
things
like
other
other
dependencies
that
we
bundle
in
Omnibus
like
postgres,
and
you
know
redis,
and
things
like
that,
where
we
oftentimes
need
to
actually
pass
that
on
to
another
configuration
file.
So
we're
going
to
do
some
investigation
on
how
to
best
handle
this
to
kind
of
move
towards
that
goal
of
having
all
of
our
secrets
encrypted
for
omnibus
moving
over
towards
our
get
a
lease
service.
E
We
have
a
really
exciting
enhancement
that
we're
working
on,
which
is
to
provide
the
foundational
support
to
have
bundles
and
that's
kind
of
an
underlying
get
technology,
but
a
lot
of
those
available
on
a
URI,
and
what
this
will
allow
us
to
do
is
actually
offload
a
good
chunk
of
the
data
and
processing
to
a
static
file
and
have
that
get
routed
away
from
the
gitly
server
itself.
This
will
have
a
number
of
benefits
number
one.
It
will
reduce
the
CPU
load,
because
this
request
will
ever
goes
through
the
delete
service
allowing
increased
scale.
E
It'll
also
allow
us
to
potentially
put
these
bundles
on
a
CDN
which
will
move
that
content
closer
to
users,
but
also
frequently
reduce
the
balance
charges
for
a
lot
of
our.
You
know:
diplomas
out
there,
because
cdns
can
oftentimes
be
cheaper
than
directly
connecting
to
a
a
machine.
So
a
number
of
benefits
here
from
the
user
experience
to
cost
profile
to
scale
and
really
excited
about
this
one
moving
over
towards
our
application.
Performance
Group.
E
We
are
working
to
now
be
able
to
easily
collect
the
Ruby
heat
dumps
that
we
create
that
we
created
earlier,
and
this
will
allow
us
to
get
live
production
views
of
how
Ruby
memory
is
performing
and
allow
us
to
get
a
better
understanding
of
how
fragmentation
and
potentially
memory
use
change
in
the
production
service.
So,
looking
forward
to
having
this
that
will
allow
us
to
better
Target
our
efforts
going
forward
moving
over
to
our
key
workflows.
Another
one
I'm
really
excited
about
in
this
release
is
we
want
to
go
ahead
and
start
indexing.
E
This
way,
when
you're
at
mentioning
folks,
you
can
continue
in
your
flow
and
keep
typing
without
waiting
for
that
to
complete
so
really
excited
about
that
Improvement
as
well
and
further
on
the
search
side,
we
are
going
to
continue
our
efforts
to
add
search
filtering
by
programming
language.
We
recently
moved
the
search
filtering
experience
over
the
left
hand,
side
that
allows
it
to
be
more
expandable
and
allow
us
to
do
things
like
actually
adding
additional
filtering
options
based
on
the
type
of
content
you're
searching
for
like
code
to
extend
to
things
like
languages.
E
So
looking
forward
to
this
being
more
available
we're
quite
far
along
here,
and
we
want
to
wrap
it
up
here
in
15.7
last
thing
on
the
key
workflows,
we
want
to
fix
an
issue
that
is
causing
timeouts
for
users
when
they
push
through
a
geosecondary
right
now,
if
it
takes
longer
than
60
seconds.
Unfortunately,
the
push
will
time
out,
and
this
can
impact
larger,
pushes
larger
repositories
and
things
like
that
and
so
I'm
going
to
go
ahead
and
fix
this
workflow
for
our
users,
who
use
those
to
better
support
them.
E
Moving
over
towards
maintenance,
We
are
continuing
our
efforts
on
Ruby
3.0.
This
will
allow
us
to
move
on
to
this
version
prior
to
the
2.7
deprecation
and
we
are
quite
far
along,
but
we're
actually
expecting
to
have
a
green
pipeline
for
gitlab
in
15.7,
which
is
quite
exciting
and
overall,
the
team
is
confident
that
we
can
move
on
to
the
Ruby
3.0
well
in
advance.
So
when
the
duplication
event
will
happen
over
towards
distribution
and
continuing
the
theme
of
efficiency,
we
are
working
on
further
improving
our
pipelines.
E
You
want
to
go
ahead
and
deprecate
libgit2
in
giddly
right
now.
We
utilize
both
git
and
lib
get2,
and
what
this
means
is
that,
right
now
to
maintain
both
of
them
and
if
a
feature
launches
and
get,
we
have
to
wait
for
it
to
arrive
and
let
it
get
two
before
we
can
take
advantage
of
it.
So
we
want
to
go
ahead
and
deprecate.
It
rely
on
just
one
Library,
which
allows
to
have
a
faster
velocity
for
our
new
features
and
finally,
on
the
database
side.
We
are
continuing
our
work
on
batch
back
on
migrations.
E
This
will
allow
us
to
have
all
teams
in
gitlab
and
all
contributors
in
gitlab
to
have
an
easier
way
of
running
large
migrations
and
right
now,
the
past.
You
know
it
was
pretty
bumpy
and
we
are
getting
quite
close
to
General
availability
with
a
new
framework,
and
this
will
allow
an
automatically
tuned
batch
backup
migration,
which
we
can
pause.
We
can
resume
and
overall,
have
a
much
easier
experience
in
rolling
this
app.
It's
also
safer
for
our
production
users
as
well,
and
not
just
more
efficient
for
our
developers.
F
Thank
you,
Josh
really
exciting,
to
see
all
the
improvements
to
reliability
and
security
and
performance,
and
also
making
our
migration
life
easier.
So
with
that
I'll
jump
into
the
dev
section,
there's
so
many
exciting
things
to
to
talk
about
coming
from
Dev
I
only
have
time
for
a
few.
So
please
check
out
the
planning
issues
to
see
what
the
entire
team
is
doing.
F
So
the
first
issue
that
I
want
to
talk
about
which
I'm
really
excited
about
a
lot
of
customers
are
asking
for
is
that
ethics
can
now
have
issues
and
sub-eptics
assigned
from
different
groups.
This
is
really
exciting,
because
we
internally
also
in
GitHub,
have
different
projects
that
we
need
to
often
link
between
one
and
another,
so
really
exciting.
To
see
this
coming
coming
in
the
near
future.
The
next
thing
that
the
product
planning
team
is
doing
is
working
on
okr
support
in
gitlab,
which
is
also
super
exciting.
F
We
want
to
introduce
a
new
issue
type
which
is
okrs,
and
we
plan
to
use
it
also
internally
for
dog
fooding,
a
lot
of
different
efforts
are
going
to
be
worked
on
and,
as
part
of
this
I'll
highlight
just
one,
which
is
adding
the
ability
to
see
hierarchy
and
children
relationship
on
these
types
of
work
items
so,
for
example,
a
career
key
result
is
a
child
from
objective.
So
this
also
has
wider
effects
on
the
work
items
in
the
future,
we're
starting
with
oprs
and
really
really
exciting.
F
Moving
on
to
the
auth
team,
several
really
exciting
features
coming
up.
The
one
that
I'm
most
excited
excited
about
is
our
first
MVC
for
customizable
roles,
which
is
something
that
a
lot
of
our
users
are
asking
as
well.
This
is
going
to
be
an
API
only
and
will
be
available
to
group
owners
on
our
gitlab.com
SAS
project,
and
we
will
be
able
to
create
a
custom
role
that
adds
view
only
code
permission
to
guest
users,
which
is
something
that
we
can't
do
today,
but
is
highly
requested.
F
Next
is
introducing
skin
for
self-managed
users
today
this
is
not
available,
and
this
will
allow
administrators,
end-to-end
user
lifecycle
management,
deep
provisioning
users
who
are
at
the
end
of
their
life
cycle
and
so
on,
which
is
a
problem
today
on
that
same
theme
of
making
the
Enterprise
user
management
easier,
we
are
also
adding
the
ability
to
automatically
claim
user
accounts
matching
verified
domain.
So
if
the
users
are
not
provisioned
with
salmon
or
skin
they
can
they
match
a
verified
domain.
F
For
example,
any
user
at
gitlab.com,
their
account,
is
automatically
marked
as
belonging
to
the
company
so
exciting.
To
see
this
as
well,
the
workspace
team
is
working
on
making
project
owner's
life
Easier
by
adding
to
Do's,
for
when
a
member
asks
requests
for
access.
F
Moving
on
to
editor
also
super
exciting
we're
going
to
introduce
an
MVC
for
our
remote
development
initiative,
so
very
excited
to
see
this.
This
is
going
to
be
a
beta
that
users
can
participate
in
and
give
us
feedback
of
the
new
web
ID.
That's
running
vs
code.
F
In
addition
to
that,
the
editor
team
is
working
on
displaying
and
editing
markdown
comments
in
the
content
editor.
So
this
will
treat
comments
within
the
editor
better
than
it
does
today.
F
Moving
on
to
the
import
team,
two
really
exciting
initiatives
that
are
coming
forward.
Another
beta.
This
is
the
second
of
three
that
I'll
talk
about
today,
another
beta
coming
out
for
gitlab
migration.
F
The
the
feature
will
allow
users
to
migrate
in
bulk
entire
groups,
including
all
the
projects
beneath
it
from
one
instance
to
another
instance.
We've
been
working
on
this
for
a
really
long
time
and
really
really
exciting.
To
get
this
to
the
beta
and
on
the
GitHub
importer
side,
we're
adding
the
ability
to
buy
API
bulk
import,
all
personal
gifts
that
will
be
imported
as
Snippets
in
gitlab,
and
also
adding
the
ability
to
cancel
GitHub
project
Imports,
which
didn't
doesn't
exist
today.
F
Foundations
has
been
has
been
doing
a
lot
of
work
around
validating
our
new
new
look
for
gitlab
and
we're
going
to
work
on
the
redesign
for
the
new
sidebar,
which
looks
a
little
bit
like
this,
so
very
excited
to
see.
Continued
work
on
that
as
well.
F
Source
code
also
has
a
huge
initiative
of
introducing
Branch
rules
with
this
new
MVC
users
can
view
source
code
rules
in
one
single
place
and
it
gets
organized
by
branches.
F
There's
no
big
functionality
change,
but
it
doesn't
improve
the
discoverability
and
of
the
settings
and
it
it's
also
helps
solve
a
lot
of
the
usability
problems
that
we've
uncovered
in
different
user
surveys.
They
will.
They
will
also
be
working
on
improving
the
forking
experience
so
showing
how
far
behind
or
ahead
of
fork
is
from
the
Upstream
project,
which
should
help
a
lot
of
our
users.
F
In
addition,
they're
going
to
work
on
supporting
SSH
signed,
commits
moving
on
to
certify
certify,
is
working
on
allowing
to
reference
work
items
at
our
requirements,
independence
of
their
ID,
which
is
a
great
help
for
today,
and
then
the
second
to
last
item
group
is
the
project
management
group,
which
is
continuing
our
work
on
work
items,
adding
the
ability
to
view
activity
and
system
node.
F
So
if,
for
example,
someone
renamed
the
title
of
it
of
the
task
or
something
changed,
adding
that
ability
which
was
missing
today
and
also
adding
the
ability
to
start
a
thread
and
leave
a
comment,
this
will
also
help
our
okr
story
from
that
I
started
with
so
very
excited
to
see
those
two
teams
work
together
and
the
last
team
that
I
want
to
highlight
is
in
our
extend
our
CI
CD
lead
is
the
optimized
team
with
the
third
beta
coming
out
from
this
Milestone,
which
we're
very
excited
about
which
is
introducing
an
executive
dashboard
with
metrics
that
that
should
have
a
comparative
view
that
will
help
Executives
View
and
compare
all
the
developer
productivity
metrics
so
excited
to
get
everyone
joining
on
the
beta
programs
and
getting
your
feedback
and
with
that
I'll
bring
pass
it
back
to
David.
A
A
First,
we
talked
about
encrypting
all
rails
passwords
stored
in
galab.rb
Gilly
support
for
bundle
Uris
for
clones
and
the
ability
to
collect
Ruby
Heap
dumps,
really
giving
us
a
way
to
continue
to
improve
the
uptime
effectiveness
and
efficiency
of
gitlab.com
and
thus,
by
extension,
Get
Loud
self-managed
users
as
well
under
improved
keywordful
usability,
improve
the
user
experience
when
we
change
analyzer
roles,
support
for
all
commits
not
just
merge,
commits
in
the
chain
of
custody
report,
GA,
release
of
browser-based
or
the
browser-based
crawler
auth
service
and
passive
checks.
A
I
know
the
team's
been
working
on
that
for
a
very
long
time,
very
excited
to
see
Echo
GA,
add,
search
filtering
by
programming.
Language
epics
can
now
have
issues
in
sub
epics
from
different
groups.
Improving
our
portfolio
management,
customizable
roles,
NBC
super
excited
about
that
and
then
I'll
Echo
reads:
excitement
on
remote
development.
The
team's
been
working
hard
to
bring
this
to
Market
and
allow
users
to
be
able
to
truly
take
advantage
of
remote
development
environments
and
then
finally
manage
dashboards
and
project
repositories
as
code.
A
What
a
way
to
shift
observability
left
by
being
able
to
express
those
items
within
the
project
Repository
and
then.
Finally,
our
extender
lead
on
cicd
new
exec
dashboards
with
metrics
comparative
views,
dynamically
mask
Vault
variables
and
excited
about
another
MVC,
our
RPM
package
manager
as
well.
Please
check
out
the
release
kickoff
page
for
our
full
list
of
items
make
sure
to
like
and
comment
on
issues
you
like,
so
you
can
engage
with
the
product
team
as
an
example.
A
Something
that
I'm
personally
excited
about
was
the
volume
of
effort
put
by
the
teams
on
improving
our
keyword
for
actually
a
key
workflow
usability.
I
was
only
able
to
touch
on
a
very
small
percentage
of
them,
so
please
make
sure
to
go
out
and
check
out
what
the
team's
doing
to
make
gitlab
a
more
usable
and
livable
experience.
So
thank
you.
Everyone
for
watching
and
join
us
for
this
kickoff.