►
From YouTube: 2021 12 02 Docs Office Hours
Description
Jenkins documentation office hours highlighting the process used to create the LTS changelog and the LTS upgrade guide
A
Welcome
to
doc's
office
hours,
it's
the
2nd
of
december
2021
and
delighted
to
talk
to
documentation.
Remember
we
abide
by
the
jenkins
code
of
conduct,
so
today's
agenda
modernizing
a
plug-in
blog
post,
yoraj
and
I
working
together
on
it
and
if
time
allows-
and
if
it's
not
too
much,
we
may
review
gavin
mogan's
election
results
blog
post.
It
needs
to
it's
scheduled
to
post
tomorrow.
A
B
A
A
A
A
A
A
B
A
A
A
A
B
A
Okay,
so
now-
and
that
was-
I
suspect,
a
capability
you
didn't
have
before
so
you
have-
you,
you've
always
had
the
ability
to
comment,
but
now
you
can
also
close
an
issue.
This
is
not
one
we
should
close,
but
just
knowing
that
you've
got
it.
That's
a
permission
that
I
believe,
you're
granted
by
being
part
of
the
triage
team.
A
A
B
A
So
your
we'll
have
you
remain
as
a
as
a
triage
team
member
for
two
or
four
weeks
at
least
then
then,
after
a
period
of
this,
like
this
mentoring,
then
we'll
submit
the
request
to
the
jenkins
developer
list,
asking
that
you'd
be
granted
permission
to
be
a
copy
editor
and
considering
how
few
copy
editors
there
are.
We
really
need
you.
A
B
A
A
B
A
I'm
not
well
yeah,
that's
that's
why
we
want
some
training
time
for
you,
so
that
you
don't
now.
Thankfully,
it's
just
get
and
therefore
we
can
always
revert
your
commit.
It's
very
easy
to
revert
a
mistake.
So
we're
not
we're
not
frightened
of
people's
mistakes.
Mistakes
happen,
we
fix
them,
but
I
don't
know
that
it
will
give
you
this
permission.
So
let
me
show
you
show
you
this
one
where,
for
instance,
this
is
a
draft
item
and
I
don't
I'm
not
sure
if
copy
editor
will
let
you
uncheck
the
ready
for
review.
A
A
B
A
A
Well-
and
I
think
I
think
it's
good
for
us
to
record
this,
so
this
is
a
perfect
excuse
for
us
to
do
a
recording
like
this
and
say
here
are
the
steps
that
are
commonly
taken.
So
how
is
the
change
log
assembled?
How
is
content
chosen?
How
is
the
upgrade
guy?
How
are
the
upgrade
topics
upgrade
the
grid
topic
selected.
A
A
B
B
B
A
A
A
A
B
A
A
A
B
B
Yes,
so
I
was
wondering
why
are
we
picking
something
up
from
future
weekly
releases
now?
I
know
because
the
current
three
2.391
is
not
something
that
that
we
want
to
show
to
use,
because
it
is
just
a
statement
saying
that
we
have
this
bug
and
we
actually
want
to
show
them
a
fix
of
that
bug
and
which
is
in
the
future.
One
right.
That's
right,.
A
B
B
A
A
B
B
A
Well,
good,
so
you,
you
asked
exactly
the
right
question,
so
the
the
earlier
discussion
talked
about
how
we
assembled
this
piece.
These
are
back
points
now.
Your
next
you've
immediately
taken
us
to
the
next
question
is
how
do
we
assemble
this
piece
and
and
what?
What
is
it
that
chooses
things
to
go
there
because
notice?
The
word
here
is
notable,
so
this
this
is
telling
me
a
human
being
reviewed
all
the
changes
and
decided
which
ones
were
important
enough
to
be
notable,
and
so
so.
A
B
A
Yes,
exactly
the
what's
new
in
2.303.3
doesn't
know
anything
about.
What's
in
304
305
306.,
all
it
knows
about
is
what
was
actually
applied
to
303.3,
and
so
this
does
not
include.
Excuse
me
all
of
the
new
things
added
in
304,
305,
306,
etc.
So
it
has
to
be
mentioned
here.
If
it's
notable,
it
meant
it's
mentioned
in
notable
changes.
B
A
A
Yeah,
so
I
I
wonder,
maybe
it
would
yeah
I
mean
I
may
want
to
consider
diagramming,
because
what
what
this
really
reminds
me
is
that
we've
got
yeah,
let's
see
if
I've
got
hang
on,
we've
got
to
try
this.
I'm
remote
is
much
more
difficult
than
being
being
with
you
and
me
sitting
around
a
white
board
together.
If,
if
I
took
this
and
said
okay
here,
we've
got
2.303.3
oops
three
and
here
we've
got.
A
A
B
B
A
A
A
A
A
B
A
B
Definitely
I
am
loving
it
because
without
this
I
would
that
be
a
bit
more
difficult,
but
this
makes
it
easier
for
me
great
okay,
thanks
for
that-
and
you
use
this
term
weekly
baseline.
So
it
is
oh
we,
it
is
a
weekly
release
that
we
decide
that
okay.
So
this
is
the
weekly
release
on
which
we'll
be
basing
our
lds
release
right
in.
B
Okay,
so
is
2.319
and
we
are
back
quoting
some
changes
from
the
on
2.3,
20
and
onwards
weekly
releases.
Some
of
those
fixes
the
changes
which
are
entries
which
are
mentioned
in
the
weekly
baseline
and,
and
so
that
will
be
in
the
first
section
of
our
release
and
on
the
second
section,
the
notable
changes
it
will
have.
All
the
cherry
picked
selected
entries
from
the
previous
lds
releases,
weekly
change
log
till
my
current
weekly
change
log.
A
B
A
A
A
Oh
that's
not
relevant
to
a
user,
that's
not
relevant
to
your
users,
so
I
created
the
subset
by
doing
a
copy
everything
in
delete
things
that
I
thought
didn't
matter
and
then
I
did
a
grouping
exercise
to
collect
things
that
I
thought
were
related
to
each
other
near
each
other.
That's
why
you
see
modernize
the
jenkins
managed
screen
and
the
jenkins.
B
B
A
B
A
A
A
B
A
Right
it
is,
it
is,
it
is.
It's
called
long-term
support
because
it's
intended
to
be
more
stable
than
the
weekly
release,
and
so
the
the
lts,
the
long-term
support
release,
gets
extra
testing
before
we
deliver
it
and
then
lasts
longer
as
a
as
a
stream
of
release.
So
it's
we
stay
on
the
same
baseline
for
three
months.
B
A
B
A
B
B
So
you
said
you
need
to
read
through
them
in
order
to
be
thorough,
with
the
changes
right
right,
so
that
is
just
for
the
benefit
of
the
user
so
that
they
know
what
all
happened
between
this
period.
But
but
if
they
just
directly
change
it
to
the
latest
version,
it
won't
in
the
best
case,
break
their
system.
A
A
B
A
A
So
the
next
lts
will
be
approximately
four
to
five
weeks
from
now,
so
we
release
a
new
lts
version
every
four
weeks.
Every
three
months
we
release
a
new
baseline,
so
the
next
lts
will
be
2.319.2,
then
2.319.3
and
after
those
three
month
period
then
we'll
switch
to
a
new
baseline
2.330.
Something
probably.
A
A
A
A
B
Makes
sense
right
so
since
most
of
our
time
will
be
spent
on
this,
and
I
wanted
to
ask
another
question
around
this
and
we
just
worked
on
this
x
point
x,
dot
one
yesterday
right!
Yes,
so
if
I
want
to
help
you
on
x,
dot
to
release
cycle
release
candidate,
which,
how
should
I
be
which
weak
block
should
I
be
monitoring
for
that.
A
Yeah
yeah,
so
the
jenkins
developer
list
will
announce
x.2
release
candidate
and
it
will
in
the
announcement
to
it,
it
will
say
someone
will
will
say
I
am
willing
to
be
the
release
lead
and
they
will
propose
which
thing
should
be
backported
to
it,
and
those
back
ports
actually
are
marked
in
the
jenkins
jira
system.
I'm
going
to
move
this
off
screen
just
temporarily
just
a
minute.
While
I
go
to
find
this
on
jira
there's
some
sensitive
things
in
my
jira
that
I
have
to
be
sure
we
don't
show
okay.
A
B
A
So
this
one
is
to
be
considered
and
it
was
chosen
intentionally
not
to
include
2.319.1,
so
this
2.319.1-rejected
says
we
chose
not
to
include
it.
It
was
too
new
to
include
it
in
319.1,
so
we
will
wait
four
weeks
and
then
included
in.2
most
likely
giving
it
more
time
to
be
tested
more
time
to
be
verified
that
it's
it's
good
and
okay
for
lts.
A
A
A
A
If
we
look
down
here
at
its
history,
what
we'll
see
is
I
created
the
issue.
First
of
november,
I
updated
the
description,
etc
changed
the
status
to
open
in
progress,
daniel
beck
labeled
it
as
an
lts
candidate.
He
said
this
is
serious
enough.
It
needs
to
be
an
lts
candidate
and
or
he
labeled.
No,
I
labeled
it
as
an
lts
candidate.
He
said.
Not
only
is
it
an
lts
candidate,
it
is
also
a
regression
and
he's
right.
It
was
and
he
corrected
it
instead
of
being
a
task.
A
A
So
so
this
bug
is
is
in
weekly
between
2-314
and
2-319
and
then
its
fix
is
merged
into
2.320
and
the
bug
is
closed.
So
at
this
point
in
time
the
bug
is
closed.
But
still
has
the
label
lts
candidate,
kathy,
finds
it
and
says:
oh,
it's
closed
and
has
lts
candidate.
Therefore,
it's
a
candidate
she
proposes
it
and
when
she
proposes
it,
she
changes
the
label
to
add
this
fixed
label
to
it
to
say
this
thing
is
ready
and
will
be
fixed
in
2.319,
stable.