►
From YouTube: Monthly Release Kickoff 15.1 (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
A
Josh
libert,
director
of
tag
car
enablement
section,
will
be
providing
our
enablement
updates.
Eureka
of
product
for
our
dev
section,
we'll
be
providing
our
dev
updates.
Hillary
benson
director
product
for
our
sex
section
we'll
be
providing
our
sec
updates.
Taylor
mccaslin
principal
product
manager
for
our
model
up
stage
will
be
providing
our
updates
for
the
model.
Ops
section
and
chris
blind
senior
product
manager
for
the
release
stage
will
be
bringing
us
home
with
ops
updates.
A
We're
focused
on
providing
value
iteratively
here
at
gitlab,
with
a
focus
on
the
following
product
investment
themes,
get
lab,
hosted
first,
improve
key
workflow
usability
and
extend
our
lead
in
ci
cd.
Before
I
hand
it
over
to
josh.
We
have
a
short
public
service
announcement
on
this
live
stream.
We
will
be
discussing
our
product
roadmap,
which
includes
upcoming
features
and
functionality.
A
It
is
important
to
note
that
this
is
presented
to
you
for
informational
purposes.
Only
please
not
rely
on
this
information
for
purchasing
or
planning
decisions.
We've
planned
very
ambitiously
here
at
gitlab
and
all
items
discussed
in
this
live
stream
are
subject
to
change.
The
timing
of
any
products
features
and
functionality
remain
at
the
soul.
Discretionary
lab
so
now
that
I've
gotten
legal
data
taken
care
of
here,
I'm
gonna
hand
it
over
to
josh
to
kick
us
off
with
updates.
B
Thanks
david
I'll,
take
us
through
enablement
here
and
first
kick
off
with
the
gitlab
posted
first
theme.
So
we'll
start
things
off
with
distribution
and
they
are
working
on
an
item
that
will
support
two
larger
initiatives
that
we've
been
working
on
over
the
past
few
milestones.
The
first
is
supporting
our
operators
vacation
by
red
hat
and
the
other
one
also
is
fips
2
compliance.
B
Unfortunately,
one
of
the
images
that
we
utilize
upstream
dependencies
is
nginx
ingress
and
it
is
not
compatible
with
either
of
these
two
initiatives,
and
so
we
need
to
figure
out
what
we're
going
to
do,
and
so
we
are
looking
at
either
forking
this
and
making
the
changes
ourselves
and
potentially
contributing
them
back
upstream
or
considering
some
alternatives
and
so
we'll
be
defining
which
we
want
to
go
this
milestone
and
then
proceeding
to
move
forward
forward
on
this
to
support
again
operational
vacation
and
both
also
fips
from
fertility
compliance
which
will
be
quite
exciting
from
there.
B
We
can
move
on
to
our
geo
team
and
they
are
continuing
to
improve
some
of
the
underlying
work
tools
that
replicate
content
from
a
primary
over
to
multiple
secondaries
and
we've
been
working
on
this
for
some
time
and
we're
going
through
and
taking
content,
that's
replicated
using
own
custom
code
and
moving
it
to
the
cell
service
framework.
B
So
we
can
maintain
it
more
easily
and
focus
on
adding
other
content,
other
features
that
add
more
value
rather
than
maintaining
old
code,
and
so
we're
going
through
and
adding
projects
and
wikis,
as
well
as
the
container
registry
to
the
cell
service
framework.
This
release
from
there
we
can
move
on
to
our
database
group
and
we
are
working
on
improving
how
git
lab
can
handle
large
data.
Large
data
changes
so
oftentimes
when
a
change
is
made.
B
For
example,
in
a
new
version
of
code,
we
have
to
run
a
large
change
across
the
database
for
instances
that
are
big
like
gitlab.com.
This
can
include
quite
a
lot
of
changes.
We've
made
some
improvements
here
already,
but
we're
continuing
to
improve
the
support
that
we
have
so
we
can
automatically,
for
example,
pause
migrations,
while
certain
events
are
occurring
like
auto
vacuum
or
potentially
some
other
archival
work.
B
We
are
also
working
on
improving
our
how
we
handle
testing
of
our
data
changes
itself
right
now
we
have
a
huge
milestone
that
was
achieved
last
milestone
in
15.0,
which
is
that
we
now
have
hundred
percent
coverage
of
all
scheduled
database
changes,
and
these
are
all
tested
on
a
gitlab.com
production
clone.
So
a
very
large
database
where
we
can
actually
see
performance
changes
as
opposed
to
a
smaller
data,
set
working
more
more
difficult
to
determine
them,
but
we're
not.
B
You
know
what
these
are
new
changes
to
the
queries,
please
review
them
and
make
sure
they're,
okay
and
over
time,
we'll
work
on
animating,
adding
automated
coverage
of
these
as
well
like
we
have
with
automated.
Do
this
changes.
So
looking
forward
to
that
here,
as
well
moving
over
to
key
workflow
improvements,
we
are
working
on
improving
the
search
functionality
across
all
of
get
lab
and
what
we
are
doing
to
support
that
is
moving
commits,
which
is
kind
of
part
of
how
you
change
code
in
gitlab
over
to
its
own
dedicated
index.
B
The
main
reason
for
doing
this
is
that
it
will
improve
the
search
performance,
so
we
can
deliver
results
faster
to
users
across
both
commits
and
code
search,
but
it'll
also
set
the
stage
for
us
to
be
able
to
tune
this
index
just
for
this
content
type
in
particular,
and
have
better
filtering
options
in
the
future
as
well.
So
look
forward
to
that
we're
also
working
on
improving
the
user
experience
of
the
global
search
bar,
which
you
can
see
here
and
one
of
the
areas
we're
improving
at
this
milestone.
B
Is
you
want
to
better
indicate
the
scope
you're
searching
in?
We
added
some
text
here
you
can
see
to
try
to
indicate
you
know
where
you're
searching
right
now,
but
it's
not
very
clear
and
users
still
provide
feedback,
that's
not
sufficient
and
so
we're
working
to
improve
this
by
making
the
search
bar
wider
and
calling
out
more
particularly
the
scope
where
you're
searching.
So
hopefully
this
will
better
tell
users
what's
happening,
but
also
inform
them
that
hey.
You
know
what
you
can
search
across
multiple
scopes.
B
So
looking
forward
to
that
improvement
and,
finally,
also
kind
of
under
the
hood,
our
distribution
team
is
working
to
reduce
the
overall
effort
and
complexity
in
the
pipelines
we
use
for
building
images
and
linux
packages
for
all
of
our
users
and
ourselves
to
consume
right
now.
Maintaining
these
is
largely
two
separate
efforts
for
both
the
cloud
native
and
the
linux
packages,
and
it's
quite
a
lot
of
effort
for
our
team
to
focus
on,
and
so
we
want
to
try
and
make
this
as
common
as
possible
and
reduce
the
overall
effort
it
takes
to
maintain.
B
C
Thanks
josh
lots
of
exciting
stuff
coming
from
me,
especially
around
search
and
the
database
improvement,
so
really
excited
to
see
that
I'm
going
to
go
ahead
and
share
my
screen
so
also
based
on
the
product
investment
things
that
we
have.
The
dev
section
has
a
lot
of
really
exciting
things.
I've
highlighted
a
few,
but
all
the
teams
are
working
towards
lots
of
different
improvements.
C
I'm
really
excited
to
see
the
enhanced
security
on
still
that
subject
of
security,
we
have
our
workspace
group,
which
is
working
on
ip
support
for
user
management.
C
C
Moving
on
to
our
improved
key
workflow
workflow
usability,
our
compliance
team
is
going
to
be
adding
some
highly
requested
enhancements
to
our
streamline
audit
events,
functionality
by
adding
support
for
custom,
http
headers
for
streaming
audit
events.
This
allows
you
to
send
a
custom,
http
header
to
any
system
that
requires
a
specific
header
value,
just
as
any
ad
specific
lost
token
or
logging
values
to
be
sent
along.
This
is
the
first
iteration
and
it
adds
this
via
api
and
the
next
upcoming
releases
we're
going
to
add
it
also
to
the
ui.
C
So
it
will
look
something
like
this:
we're
really
excited
for
this
improvement
in
streaming.
Other
events,
the
compliance
team,
is
also
going
to
be
adding
the
following
audit
events
changes
in
group
level,
mr
settings,
which
will
allow,
which
will
add
an
audit
event
in
the
change
of
the
setting
at
the
group
level.
C
Audit
events
for
streaming
audit
filtering
changes,
so
any
change.
The
filter
will
send
an
audited
event
over
and
streaming
audit
events
that
do
not
currently
send
the
streaming
audit
event.
When
you
change
the
destination
in
this
upcoming
releases,
we're
going
to
add
an
audit
event
for
this
event
as
well.
C
Our
authentication
authorization
team
is
going
to
be
adding
admin
ability
to
define
password
complexity.
So
this
will
look
something
like
this.
An
administrator
can
now
create
rules
for
password
setting.
It
can
be
a
mix
mixture
of
different
rules
or
just
one
specific
one,
including
helping
the
user
out
in
on
the
user
interface
telling
them
what
is
the
valid
password.
C
So
this
is
exciting.
The
same
team
is
going
to
be
following
this
trend
for
helping
get
lab
administrators
and
are
also
going
to
be
adding
a
way
to
expose
sim
identities
in
admin
gui,
and
this
will
look
something
like
this.
So
now,
when
you
have
a
user
you're,
also
going
to
get
the
identifier
itself,
which
will
help
a
little
bit
with
visibility
around
users,
especially
provision
users.
C
So
we're
excited
to
bring
this
to
the
users.
It
was
hidden
behind
a
feature
flag.
Up
until
now,
our
integration
team
is
going
to
be
migrating
slack,
app
from
a
classic
app
to
a
granular
bot
permission
app,
which
will
allow
users
to
have
more
control
over
permissions
on
the
app,
and
this
is
going
to
be
enabled
for
users
in
this
milestone.
C
Product
planning
are
adding
a
long
anticipated
task
as
a
child
of
an
issue
which
will
this
capability
will
enable
decomposing
issues
to
allow
for
more
fine-grained
planning
at
the
project
level,
and
this
will
look
something
like
this,
so
you
will
be
able
to
add
a
child
issue,
search
for
a
child
issue
and
so
and
so
on,
and
this
is
the
first
iteration
of
our
new
work
items
model
which
will
introduce
even
more
work
items
and
hierarchies
less
for
this
theme
is
our
group
editor
who's,
going
to
be
adding
the
ability
to
preview
mermaid
diagrams,
which
will
look
something
like
this
in
our
wysiwyg
editor
and
our
last
theme
is
extending
our
lead
in
ci
cd
and
our
group.
C
D
Thanks
reeds
lots
of
good
stuff
coming
up
there
in
your
section,
really
excited
for
child
issues.
That's
that's
awesome
that
that's
coming.
Okay,
let's
see
share
all
my
screen
here.
D
All
right
awesome,
so
the
sex
section
again
is
largely
focused
on
work
that
supports
our
fiscal
23
theme
of
improving
keyword,
flow
usability.
D
If
you
haven't
seen
it
yet,
that's
where
you
can
find
that
and
in
security
orchestration,
the
team
plans
to
make
it
easier
for
users
to
catch
yaml
errors
as
they're
editing,
security
policies
by
providing
interactive
validation
directly
in
the
policy
editor.
D
D
One
second
here
got
stuff
in
the
way,
a
little
bit
of
what
that's
going
to
look
like
so
basically
you'll
be
able
to
come
into
the
configuration
screen
and
create
a
new
scan,
give
it
a
scan
name
and
description,
assign
a
scanner
profile,
so
you
can
say:
do
I
want
a
quick
scan
or
deep
scan
go
ahead
and
create
that
profile
and
then
you'll
be
able
to
enable
a
scan
schedule
set
the
time
whether
it
should
repeat
and
then
save
and
run
that
scan
as
you
as
you
want.
D
The
static
analysis
team
is
leading
an
effort
this
milestone
to
improve
supportability
across
all
of
our
security
analyzers,
so
today,
troubleshooting,
why
an
analyzer
is
failing,
can
be
a
pretty
mysterious
exercise.
So
we
want
to
make
it
easier
for
users
to
quickly
figure
out
what's
going
wrong
and
to
correct
it.
The
work
to
do
that
more
or
less
corresponds
to
you
know,
encouraging
users
to
turn
on
debug
logging
and
then
improving
the
quality
of
the
information
that
is
contained
in
those
logs
static
analysis.
D
Team
is
also
working
on
a
number
of
improvements
to
our
code
quality
capabilities.
Those
include
improvements,
the
ui
experience
and
the
code
quality
mr
widget,
as
well
as
work
to
resolve
a
current
limitation
of
the
product
where
the
pipeline
report
and
inline
diffs
can
only
display
results
from
a
single
code
quality
report,
even
if
there
are
multiple
relevant
reports
to
pull
from
and
then
finally
the
composition,
analysis
team
is
executing
on
some
foundational
architecture,
work
around
data
storage.
This
milestone
that
will
enable
us
to
deliver
a
series
of
features
that
are
in
high
demand.
D
So
we
won't
be
working
on
the
features
in
this
release,
but
some
of
those
features
include
the
ability
to
search,
sort
and
filter
the
dependency
list,
ability
to
display
the
dependency
list
at
the
group
and
subgroup
levels,
the
ability
to
download
a
cyclone
dx,
formatted
s-bom,
and
also
the
ability
to
continuously
rescan
projects
anytime.
The
vulnerability
database
is
updated
and
alert
on
new
findings
and
code.
That's
already
committed
to
the
default
branch
of
a
project.
E
Some
thanks
hillary,
those
are
exciting
updates.
Our
model
ops
team
is
actually
using
our
security
scanning.
So
I'm
looking
forward
to
some
of
those
updates
hi
everyone.
My
name
is
taylor.
Mccaslin,
I'm
a
principal
product
manager
for
the
gitlab
new
section
model.
Ops
model
ops
is
focused
on
enabling
and
empowering
data
science
workloads
across
gitlab.
E
There
we
go
awesome
today,
we'll
talk
about
two
groups
within
model.
Ops.
Both
are
focused
on
our
theme
of
improving
key
workflow
usability.
The
applied
ml
group
is
focused
on
making
gitlab
more
intelligent,
with
machine
learning
and
in
15.1.
Our
applied
ml
group
is
continuing
to
work
on
implementing
the
ui
integration
for
a
new
ultimate
feature
called
suggested.
Reviewers
suggested
reviewers
uses
a
novel
machine
learning
algorithm
to
suggest
a
reviewer
likely
with
context
to
review
code
changes
in
a
merge
request.
E
E
If
you
are
interested
in
what
we're
doing
here
also
mention,
we
are
in
a
closed
public
beta
for
this
feature,
there's
a
link
to
the
form
to
express
your
interest
if
you're,
an
ultimate.com
user
so
fill
this
out,
and
we
can
help
you
get
enabled
in
this
beta
and
you
can
help
us
shape.
What
this
feature
will
look
like
next.
E
Moving
on
to
our
ml
ops
group,
this
is
focused
on
making
it
easier
for
customers
to
run
ml
and
ai
workloads
on
gitlab,
with
15.1
we're
continuing
improving
how
python
notebooks
work
in
merge
requests
to
improve
data
scientist
workflows.
In
a
previous
release,
we
made
python
notebooks
more
readable
by
rendering
them
in
the
commit
view,
we're
bringing
that
to
the
merge
request
view
that
will
look
something
like
this
you'll
notice,
this
little
toggle
to
switch
between
the
rock
code
view
and
the
rendered
view
in
a
diff.
E
This
will
make
it
easier
to
code
review
and
comment
on
python
notebooks.
This
is
a
feature
for
all
git
lab
users.
This
is
just
the
beginning
for
model
ops.
We
have
lots
of
exciting
things
planned,
be
sure
to
check
out
our
stage
direction
for
more
details
on
our
future
plans
now
I'll
hand
it
over
to
chris
to
talk
about
ops.
F
Thanks
taylor,
I
really
love
that
suggested
reviewer's
speech
you're,
looking
forward
to
seeing
that
rolled
out,
so
everyone,
my
name,
is
chris
bellani,
I'm
the
pm
for
the
release
stage
here
at
git,
lab
I'll,
be
covering
for
ops.
For
today.
Let
me
share
my
screen.
F
Also
too
many
tabs
over
here,
let's
see
well
I'll
continue
on,
so
the
ops
section
is
comprised
as
a
reminder
of
the
verified
package
release
configured
in
monitor
stages.
F
So
here's
what
this
manual
job
page
looks
like
today
and
then,
with
this
update,
we'll
add
a
new
drop
down
button
for
the
retry
action.
If
you
hit
that
button,
you'll
see
two
options:
retry
which
retries
the
job,
just
as
it
was
run
previously
and
then,
if
you
hit
update
variables,
it'll
take
you
back
to
this.
F
This
run
screen,
but
now
you'll
be
able
to
see
which
variables
and
what
their
values
were
for
the
job,
as
well
as
add
or
edit
some
of
those
variables
so
again,
super
useful
for
for
making
sure
those
pipelines
continue
running
the
next
one.
Another
key
workflow
is
creating
releases
and
tags
using
the
apis.
F
So
right
now
it's
possible
to
create
releases
from
right
from
with
your
ci
pipelines,
but
we
only
allow
the
ability
to
create
lightweight
tags
so
tags
without
messages.
With
this
update,
we'll
give
you
the
ability
to
add
a
message
as
part
of
your
api
call
and
give
you
the
ability
to
create
an
annotated
tag
so
again,
streamlining
that
process
a
little
bit
more,
giving
you
that
added
information
across
your
tags.
F
The
next
key
workflow,
is
adding
timeline.
Events
for
incidents,
and
so
here
is
our
incidents
page
and,
with
this
update,
we'll
add
a
new
icon
button
that
looks
like
this
clock
and
when
you
click
that
button
it'll
add
automatically
that
comment
right
into
your
incident
timeline.
So
the
idea
here
is,
we
want
to
quickly
give
you
a
way
to
facilitate
adding
information
into
the
timelines
rather
than
worrying
about
kind
of
adding
and
writing
messages.
F
We
want
you
to
be
efficient
and
really
focus
on
triaging
resolving
those
incidents
rather
than
kind
of
adding
these
these
events
manually
and
then
on
to
the
next
theme
extending
our
lead
in
ci
cd.
So
this
is
our
core
mission
for
the
op
section
and
then
this
first
update
here
is
adding
usage
by
projects
graph
and
project
table
for
sas
runner
usage.
F
So
today
you
can
see
at
the
group
level
or
name
space
level,
the
the
amount
of
minutes
you
use
for
sas
runners,
but
you
can't
see
which
project
across
all
of
your
projects,
but
you
can't
see
which
projects
specifically
are
using
those
and
so
with
us,
with
this
update
you'll,
be
able
to
see
a
breakdown
of
the
different
projects
and
how
much,
how
much
minutes
they're
using
and
again
giving
you
more
visibility
to
manage
those
those
costs.
F
The
next
one
here
is
adding
software
at
stations
to
enable
salsa,
2
and
gitlab
ci.
So
really
what
this
means
is
adding
the
ability
for
for
the
runner
to
generate
some
metadata
during
the
ci
job
execution
and
why
this
is
important.
Gitlab
is
driving
towards
security.
Software
supply
chain
direction.
F
Next
update
here
is
migrating.
The
paid
tier
images
to
the
new
registry,
so
we've
been,
we've
been
migrating
last
mile
since
we
started
on
the
fleet
here
this
milestone,
we
want
to
start
migrating
paid
tier
customers
from
the
old
registry
to
the
next
generation
registry
and
as
a
reminder,
no
work
needed
to
support.
This
you'll
just
expect
to
see
better
improvements
and
performance
improvements,
as
this
rolls
out
the
next
one
here
is
package,
fips
compliance,
and
so
just
this
is
making
sure
the
package
registry
and
container
registry
are
compliant.
F
It's
a
government
standard
and
it's
a
requirement
for
working
with
our
us
government
partners
and
it's
a
requirement
for
bismuth
veteran
as
well.
Then
last
but
not
least,
we'll
be
adding
kubernetes
1.22
support
for
our
gitlab
agent
and
that's
it
for
for
offs.
A
lot
of
great
work
coming
up
super
excited
for
that
and
I'll
pass
it
back
to
david
to
wrap
this
up.
A
A
I'm
excited
about
that
as
well
and
then,
finally,
adding
admin
ability
to
define
password
complexity,
policies
for
our
extend
our
lead
in
ci
cd,
showing
shared
runner
usage
duration
by
project
in
the
group
user
usage
quota,
as
software
attestations
to
enable
salsa
to
get
lab
ci
packaging
container
registries
supporting
fips
also
very
excited
about
that
one
as
well,
and
adding
more
visibility
around
our
metrics,
including
some
new
charts.
A
Please
check
out
the
release,
kickoff
page
for
a
full
list
of
items
and
please
feel
free
to
like
and
comment
on
the
issues
and
engage
with
the
product
team.
Also
before
we
wrap
up
just
want
to
highlight
that
everyone's
excited
about
lab
15
with
gallop
15
only
being
four
days
away.
Please
stay
tuned
for
updates
on
there's
a
dedicated
website.
A
We
can
go
and
sign
up
to
join
the
live
stream
of
it,
we'll
be
bringing
you
all
the
exciting
things
that
are
happening
with
15,
as
well
as
a
look
back
and
get
lab
reports
and
all
the
value
provided.
A
I
want
to
highlight
some
of
the
themes
that
we're
going
to
be
using
as
part
of
the
lab,
15
visibility
and
observability
by
removing
silos
and
driving
efficiency,
continuous
security
and
compliance,
agile
or
energy,
again,
enterprise,
agile
planning
and
workflow
automation,
and
supporting
data
science
teams
and
workloads.