►
From YouTube: GitLab 14.7 Kickoff - Verify:Pipeline Authoring
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
Hi
everyone-
this
is
dr
hoshkovitz,
and
this
is
a
pipeline
authoring,
14.7
kickoff
video
before
we'll
get
going.
I
want
to
point
you
to
our
planning
issue.
Question
number
36,
underneath
the
pipeline
authoring,
a
project
where
you
can
see
the
scope
of
this
iteration
of
this
milestone,
and
you
can
also
see
how
the
team
is
collaborating
as
we
plan
this
milestone.
A
You
can
also
add
your
questions
on
all
comments
if
you
have
any
in
there,
so
this
coming
with
a
milestone
is
going
to
be
pretty
light,
mainly
because
of
the
engineering
allocation
and
the
upcoming
vacation,
and
I
want
to
emphasize
one
issue
out
of
all
the
issues
and
which
is
the
track:
can
notify
the
application
of
types
keyword.
This
is
actually
our
way
of
starting
to
implement
a
ci
duplication,
ci
deprecation
process.
A
A
So
the
idea
that
was
formed
by
one
of
our
engineers
is
to
create
some
sort
of
a
process,
and
we
decided
that
we'll
take
a
one
keyword
and
we
will
try
to
do
this
process
on
15.0
and
if
it
will
be
successful,
it
will
be
our
official
ci
deprecation
process
and,
first
of
all,
the
keyword
that
we
selected
is
type
and
types.
A
It
was
actually
deprecated
five
years
ago
and
up
until
today,
and
we
we
didn't
thought
about
removing
it
and
because
of
this
process,
we
can
actually
I'm
hoping
we'll
be
able
to
remove
it
in
15.00.
So
what
this
process
is
all
about,
and,
first
of
all,
whenever
we
decide
that
we
want
to
duplicate
the
keyword,
we
sorry
to
remove
a
keyword
we'll
start
with
the
deportation.
A
The
application
is
an
announcement
for
our
user
that
this
keyword
is
going
to
be
deprecated
and
then
the
second
the
second
level
comes-
and
this
is
what
this
is
the
this
is
what
we
plan
to
implement.
This
is
what
is
new.
Is
the
warning
provide
the
user
with
some
sort
of
a
notification
and
that
the
keyword
that
they
are
using
is
about
to
be
removed
and
will
provide
a
link
to
the
duplication
and
notice,
but
the
cool
thing
about
it
is
that
we
don't
only
do
that.
A
We
can
remove
this
keyword
and
level.
Three
is
removable
and
removal
is
scheduled
for
the
next,
the
next
major.
So
in
this
milestone,
we
are
looking
at
the
type
and
types
keyword.
Actually,
those
are
two
keywords
and
that
are
practically
the
same
and
and
the
implementation
is
on
adding
the
warning
and
capturing
the
telemetry
and
until
15.0
we
will.
A
We
will
take
down
and
see
and
assess
the
impact,
and
if
we
say
that
the
impact
is
low,
then
we'll
be
able
to
deprecate
to
remove
the
keyword
and,
of
course
removing
the
keyboard
is
something
that
we
want
to
do,
because
we
don't
want
to
support
all
the
keywords
that
we
have
forever.
We
do
need
to
start
thinking
about
how
we
can
deprecate
it.
A
So
I'm
really
excited
about
about
this
milestone
and
this
process
that
we
are
going
to
start
and
hoping
it
will
be
successful
and
with
that
I'm
going
to
hand
it
over
to
nadia
to
talk
about
the
scope
of
work
for
ux.
Thank
you
and
bye.
B
Hey
everyone,
14.7
will
be
a
very
short
milestone
for
me.
I
will
be
away
for
christmas
and
years
holidays
for
most
of
the
milestone,
so
we're
keeping
the
scope
of
work
for
ux
for
14.7
pretty
light.
So
in
line
with
one
of
our
oqrs
in
q4,
I
will
be
focusing
on
ux
depth,
so
I
will
be
working
on
ongoing
ux
step
issues
and
making
sure
that
any
new
ux
issues
have
refined
proposals.
So
we
can
continue
scheduling
them
for
the
upcoming
milestones.
B
One
design
issue
that
I
will
be
working
on
is
for
showing
tool
tips
with
links
to
the
docs
in
the
pipeline
editor.
So
this
issue
is
about
improving
the
usability
of
the
pipeline
editor
and
making
it
easier
for
you
to
learn
ci
yml
essentially.
B
So
the
idea
here
is
that
we
want
to
add
tooltips
to
the
editor
when
you
hover
over
yaml
keywords
or
cim
on
keywords
that
will
show
a
little
description
of
that
keyword
and
provide
a
link
to
the
documentation
where
you
can
learn
more
about
how
to
use
this
keyword,
see
the
examples
and
things
like
that
and
as
an
mvc
iteration
most
likely,
we
will
just
link
to
the
documentation.
B
So
you
would
be
able
to
open
github
docs,
but
we're
also
thinking
about
how
we
can
improve
it
further
and
some
ideas
we
have
is
around
adding
contextual
documentation
for
the
keywords
to
the
drawer.
So
perhaps
you
would
be
able
to
click
on
the
link
in
the
tooltip
and
then
see
the
desired
documentation
right
there
within
the
editing
experience
without
having
to
leave
your
tab.
Your
browser
tab,
so
yeah.
B
As
you
can
see,
there
is
not
much
work
going
on
in
14.7,
but
we're
continuing
our
focus
on
usability
improvements
and
burning
down
ux
depth,
so
very
excited
to
see
how
it
will
improve
the
pipeline
authoring.
Experience.