►
From YouTube: Delivery Fast Boot: Day 2 kickoff
Description
Delivery team fast boot Day 2: the team discusses the whole release and deployment process and the tasks are created and divided.
This recording was cut off at the end due to a camera issue.
The issues listing the work done are contained in epic https://gitlab.com/groups/gitlab-org/release/-/epics/17
A
A
So
first
one
is
for
in
auto,
deploy
we're
gonna
be
automatically
creating
these
branches
and
they're
called
Auto
deploy
branches.
Most
of
this
is
done.
We
have
like
the
tasks
to
create
the
give
IBE
omnibus
11,
deploy
a
branch.
I
put
some
two
dues
or
some
questions
here.
Do
we
want
to
also
create
the
branch?
Won't
get
left,
see
yeah
we
have
to
so.
The
answer
is,
yes:
does
the
branch
name
and
in
EE
or
does
it
is
it
in
freshman
you
going
to
be
different
for
give
up
ceme.
A
A
D
A
A
A
D
A
B
B
B
Think
we
should
be
super
annoyed
with
it.
I
think
we
should
just
leave
labels
as
they
are
waiting
to,
because
one
of
the
problems
we
have
with
security
automation
was
you:
have
this
silence
reassigned?
You
know
and
we
slipped
one
or
two
times
with
so.
If
we
just
leave
the
comment
every
time
we
try
to
pick
it,
it's
gonna
affect
nation.
B
C
A
C
A
So
after
all
of
these
changes
have
been
picked
into
the
repos
and
maybe
even
we've
done
the
verge
via
the
Virgin
strain
or
something
now
everything
will
be
alive.
Calm.
Do
we
push
then
to
death,
or
do
we
let
the
because
the
reposting
will
do
this?
It's
a
protected
branch
out
of
the
play.
We
just
let
the
repose
think
do
it.
No,
do
we
do
an
explicit
push,
then
we
do
explicit
push
to
death,
make
sure
it
works
exactly
because.
B
A
B
D
B
A
D
C
B
D
A
A
A
D
C
B
True
exactly
and
she
our
variables
are
not
very
transparent,
so
we
cannot
even
understand
what's
happening
there.
So
if
we
tag,
then
we
can
figure
out
how
we
want
to
name
it
and
if
the
debt
already
exists
so
do
a
check.
Does
that
exist?
Yes,
he
does
then
you're
done
and
I'll
package
traded,
no
deployment.
A
C
B
B
B
B
Our
branch
is
just
a
name
that
we
figured
out
because
of
the
name
package
naming
constraints
so,
for
example,
the
reason
why
this
is
F
is
because
it
is
after
RC
right,
so
this
wouldn't
be
considered
like
if
you
install
an
RC
and
then
you
install
our
branch
on
top
of
it,
then
it's
an
upgrade.
If
we
set
our
B,
then
it
would
be
considered
the
downgrade,
dense
packaging
standards.
C
A
B
A
B
I
mean
obviously
changing.
This
now
would
be
a
problem,
but
this
we
can
change
to
something
else.
So
as
long
as
we
keep
that
you
know
our
needs
to
remain,
and
if
you
want
to
increment
it
here-
and
we
can
name
this,
whichever
way
we
want
and
then
we
can
remove,
actually
we
cannot
remove
the
pipeline
ID.
So
the
reason
for
this
is,
if
you
have,
if
you
have
the
EHR
remaining
the
same
and
how
many
verses
somewhere
it
is.
B
A
B
Honestly,
this
is
the
package
version
right
now.
This
is
the
package
version,
so
the
shopper
on
the
top
of
the
tag
actually
would
remain
the
same,
which
means
it
wouldn't
be
rebuilding
the
package.
We
would
abort
the
package
built
before,
because
we
were
trying
to
create
the
tag
and
it
already
exists,
and
that
would
fail
and
the
way
we
will
rebuild
this
package
if
we
needed
to
is
delete
the
tag.
B
A
It
is
I
mean
we
can
use
the
CIA
I
think
we
can
use
the
CI
variable
just
on
it
enables
true,
which
is
what
I'm
doing
now
in
the
CIA
to
limit
the
number
of
stages
that
are
run
and
also
to
on
an
employee
right
now,
a
pre-prom
so
staging
soon
I
think
that
will
be
fine
but
I'm
still
like
what
is
what
is
the
tank?
It'll
look
like
it's
going
to
be
11,
so
the
type
will
be
like
11
10
and
then.
A
B
B
B
B
Sorry
only
position
does
not
matter
in
that
case,
but
there
we
go
so
she
had
funds
a
green
commit
under
the
branch
and
tags.
Can
I
and
thanks
and
triggers
a
package
of
plastic
oil.
So
this
part
we
need
to
think
about
like
how
do
we
make
this
a
bit
more
robust
so
that
any
switch
and
change?
We
can
add
like
another
step.
So
if
we
died
here,
but
if
you're
dead
here
we
don't
have
the
Omnibus
she'll.
A
B
D
B
Concern
is,
we
are
going
to
add
more
steps
right.
It's
not
only
going
to
be
installing
a
package.
We
are
working
towards
complete
using
containers
as
well.
So
if
we
make
a
decision
here
that
is
going
to
rule
out
us
using
another
system,
yeah
I
would
like
to
meet
you
to
be
more
robust.
It
possible
Martin.
If
I
must.
C
B
A
B
B
B
But
there
is
like
two
things
that
that
you
need
to
care
about
denominators
then
the
the
specs
running
it
love
the
calm
and
the
build
like
packaged,
build
running
on
that
means
of
the
tour
we
have
that
separate.
So
you
will
have
to
let
me
logic
that
says,
find
me
green
coming
to
me,
I'll
come
and
finally
green
Committee
on
that
before
and
then
decide
you
both
are
being
that's.
A
C
B
B
A
A
A
B
B
B
B
This
is
the
point
where
we
need
to
manifest
project,
but
that's
a
lot
of
work.
Yeah,
that's
a
lot
of
work
and
I.
Don't
think
we
can
get
away
with
that
at
the
moment,
so
keeping
it
simple,
I
guess
we
need
to
continue
with
what
we
have
described
here
and
that
is
omnibus
is
included,
and
once
we
get
to
the
point,
I
guess
I
think
as
soon
as
we
start
adding
another
project.
B
A
D
A
C
B
A
B
We
we
don't
need
another
place
where
we
need
to
remember
to
change
things
around
and
because
these
branches
are
also
deployed.
Branches
are
temporary
wrenches.
To
begin
with,
it
feels
like
a
bit
redundant
to
have
dashi
in
them,
especially
if
you
say
that
you're
passing
E
and
variable.
So
that's
why
I
feel
like,
because
that
also
helps.