►
From YouTube: Kubernetes SIG Release - 2019-02-26
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
B
A
A
A
C
A
C
There
are
were
34
enhancements
this
week,
which
is
for
less
than
last
week
to
or
from
EWS
out
of
tree,
and
this
sparked
the
whole
interesting
discussion
on
out
of
tree
sings
and
the
release
both
from
perspective
of
marketing
release,
notes
and
whole.
You
know
all
throughout
the
stack
really,
which
was
interesting,
but
you
know
there
was
the
34
enhancements
waited
for
114
33
of
them
habitat
one
doesn't
have
a
cap.
This
is
due
to
an
improved
exception
and
it
will
have
a
cap.
C
C
Similarly,
the
topic
I
feel
like
the
main
thing
that
we
should
be
like
following
up
on
with
bug.
Triage
is,
it
seems
as
though
we're
going
into
we're
going
to
burn
down
right
yesterday
was
the
starting
burned
down
final
four
weeks
into
release.
We
have
more
wasted
meetings
and
there
are
potentially
too
many.
C
There
are
not
enough
issues
in
the
Mostow
relating
to
some
of
the
things
that
we're
seeing,
whether
it's
in
the
dashboards
or
what
have
you
so
ideally
we're
whittling
down
issues
in
the
milestone
throughout
burn
down,
not
adding
them
and
then
trying
to
whittle
them
down
so
I
think
that's
the
main
initiative
over
the
next
few
days
should
be
making
sure
that
we
have
an
accurate
assessment
of
all
the
issues
in
their
tests.
Infra
looks
pretty
good,
looks
pretty
clean
numbers
of
PRS
merged
her
up
this
week,
and
that
is
kind
of
expected.
C
As
coach
Frese
is
looming,
everyone's
trying
to
merge
more
code
in
and
that's
great
Doc's
also
seems
to
be
looking
good.
March
1st
on
Friday
is
the
placeholder
Doc's
deadline,
hoping
to
get
like
a
pretty
complete
picture
of
the
docs
up
by
then
I
believe,
but
it's
crunch
time
for
Doc's
now,
so
you
know
fingers
crossed
release,
notices.
There's
lots
of
happy
observing
entrances
great
near
and
during
my
heart,
Jeff
is
going
to
talk
about
a
lot
of
banks
mostly
skip
this
comms
are
also
looking
good.
C
So
you
know
whenever
possible.
That
is
something
that
we
should
encourage.
Folks
to
do.
You
know
just
to
keep
the
folks
that
are
working
on
the
release
working
on
strictly
the
roots
with
regrets
release
branch
management.
The
thing
that
we
were
focused
on
making
sure
is
in
place
for
this
week
was
fast
forwards
and
automating
fast
forwards
and
Hannes
got
back
going
on
a
daily
basis.
C
A
A
D
D
It's
tight,
it's
close,
it's
risky
I
would
love
to
see
something.
That's
a
little
bit
more
planned
and
further
out,
but
I
also
recognize
that,
because
of
the
relationship
of
goes
release,
cycle
and
kubernetes
release
cycle,
we
can,
if
we're
not
careful
and
up
on
versions
of
go
that
are
not
supported,
which
is
a
super-fun
so
but
it's
up
to
the
contributors
to
decide
what
to
do
I'm
just
along
for
the
ride.
A
So
it
sounds
like
the
general
feeling.
Is
we
either
do
it
ASAP
or
we
wait
I
I
think
so
I
mentioned
in
the
channel
that
like
if
we
don't
have
some
documented
policy
about
this,
we
should
probably
look
at
drafting
one.
It's
I
think
it's
something
that
comes
up
every
other
cycle,
if
not
every
cycle
about
doing
something
with
go,
and
it's
usually
somewhere
around
the
I'm,
not
sure
if
we
have
time
for
this
timeframe,
so
the
fact
that
it
keeps
coming
up
means
we
should
we
should
have
it
document.
D
E
F
E
E
D
Also
won't
say
no
to
that.
My
caveat
is
that
in
attempting
to
look
for
a
documented
policy
here,
the
only
thing
I
can
find
at
the
moment
is
that
SIG's
scalability
has
it
in
their
charter
that
they
can.
They
need
explicit
approval
on
any
large-scale
changes
that
could
potentially
impact
the
scalability
of
the
project,
so
think
of
bumping.
The
version
of
that
CD.
Think
of
bumping
the
version
of
go
like
things
of
that
nature
and
for
them
to
get
a
sign-off
usually
involves
spinning
up
a
very
expensive
job.
E
Yeah,
yes,
I
guess
so
I
would
consider
the
whole
thing
in
scope.
Words
like
creating
a
pipeline
that
allows
you
to
show
six
scalability
that
a
proposed
bump
is
safe.
I
mean
this
is
all
pretty
standard
stuff
that
we
used
at
you
know
in
developing
Cloud
Foundry,
so
I
have
seen
and
been
part
of
a
delivery
team
responsible
for
producing
such
a
pipeline.
So.
B
E
Definitely
confident
that
there
are
people
at
pivotal
who
can
help
Mohandas
do
some
sort
of
preview
that
we
can
then
evaluate
for
business
and
also
get
the
documentation
to
see
the
process
documented.
So
I
think
when
we
can,
we
can
actually
voluntold
honest
here.
I
think
it's
it's
nicely
in
the
wheelhouse
of
things
that
he
had
expressed
interest
in
wanting
to
do.
H
D
E
C
D
Or
well,
whatever
comes
out
of
that
issue
that
I
linked
because
again,
there's
discussion
about
now
that
go
112
has
been
released
earlier
versions
of
kubernetes
are
built
on
an
unsupported
version
of
go
surprised,
so
we
probably
need
to
figure
out
what
we
want
to
do
about
that.
Is
it
race
how
that
issue
is
proposing
that
we
bump
every
version
of
kubernetes
up
to
the
latest
version
of
go
so.
A
D
I
D
E
Yeah
I
mean
I'm,
I,
guess
I'm,
not
super
concerned,
but
the
practical
consequences
for
people
I
have
a
hard
time,
believing
that
a
supported
version
of
kubernetes
given
Larry
I,
guess
our
own
I
guess
commercial
obligations,
don't
allow
us
or
a
Red
Hat,
IBM
or
VMware
to
walk
away
from
customers
who
are
still
using
a
supported
version
of
kubernetes,
which
I
imagine
is
the
majority
of
folks
I.
Guess
I
would
like
to
avoid
the
world
or
policy
that
would
prevent
us
from
consuming
new
version
new
functionality.
E
D
Caleb's
in
shooter
in
the
release
engineering
sub
project
is
one
of
the
owners.
I
would
encourage
you
to
go
comment
and
share
your
opinion
on
that
issue,
because
I
feel
like
deciding
on
this
issue
is
under
the
purview
of
the
release
engineering
sub-project.
My
scope
is
just
literally
this
release
and
I'm
saying
if
somebody
wants
to
give
it
a
shot,
I'm
supportive
of
them,
giving
it
a
shot
for
this
release
of
kubernetes,
but
only
if
it
lands
in
the
next
couple
of
days.
So.
A
E
A
A
All
right
sounds
good.
So
next
topic
is
patch
release
team
comms.
So
so
Tim
pepper
opened
up
an
issue
around
having
a
singular
contact
point
for
the
patch
release.
Team
I
have
actually
created
a
mailing
list
when
we
were
starting
to
talk
about
the
patch
release
team
that
I
believe
already
has
Tim
and
Alexandre
and
a
few
other
people
on
it.
So
I
will
comment
on
that
issue.
I
think
it's
kubernetes
patch
release
management
that
Google
Groups,
something
like
that.
But
I'll
find
it
comments
on
that
issue
and
get
that
wrapped
up
any
questions
there.
A
A
I'm
not
opposed
to
it.
I
like
I,
don't
have
strong
opinions
either
way.
I
also
am
like
you.
You
were
part
of
the
the
release.
Engineering
and
patch
release
team
falls
under
their
purview.
So
if
you
feel
that
that's
a
more
appropriate,
that's
totally
fine
with
me.
Even
if
it's
I
wonder
I
wonder
if
we
do
a
combination
of
both
the
Google
Group
and
then
the
discourse
list
as
part
of
that
I'm
not
sure
if
that's
possible,
technically.
E
A
A
I
I
blew
it
so
first-time
caller
many
time
listener,
I've,
never
actually
hopped
onto
a
cig
release
call
so
hello.
I
am
one
of
the
release.
Notes,
shadows
for
1:14
and
I
have
come
to
preach
about
release,
notes
and
why
I
think
they
could
be
a
lot
better.
So
it's
gonna
make
a
lot
more
sense
if
I
share
my
screen.
So
if
they're
warning
you're
about
to
see
a
screen
share,
so
these
are
the
release
notes
for
1:13.
I
When
you
think
about
release
notes,
they
should
be
end-user
focused.
In
my
opinion,
we
we
are
telling
our
end
users.
What
is
changing
in
kubernetes,
we
aren't
necessarily
informing
them
of
internal
things
that
are
happening,
so
security
content
makes
sense,
urgent,
upgrade
notes.
I
would
hope
we
put
that
on
blast
for
all
of
the
end
users
known
issues
deprecations,
that's
fine,
its
major
themes
so.
A
I
A
E
I
One
of
the
things
that
I
want
to
talk
about
is
major
themes.
I
am
all
for
city
light.
Let
me
let
me
put
it
this
way
for
most
of
the
SIG's
and
I'm
using
113
is
a
good
example.
Most
of
the
cig
themes
are
the
equivalent
of
a
quarterly
update
for
what
they
did
during
the
release
cycle,
not
necessarily
for
the
113
release
and
I
will
pick
on
myself.
I
I
Another
wonderful
example
of
themes
that
don't
make
sense.
Sic
big
data
focused
on
community
engagements.
So
what
what
I
was
thinking
of
so
part
part
of
my
rant
is
twofold.
The
first
part
is:
why
do
we
have
themes
when
they
don't
have
anything
to
do
with
the
actual
release?
Should
release
notes
just
be
specific
to
what
is
in
the
1:1?
A
This
this
has
been
a
quite
a
conversation.
I
think
I,
think
that
you
know,
we've
we've
had
it
a
little
bit
in
sig
p.m.
today
last
last
two
weeks
ago
and
sig
release
around
out
of
tree
handling
right
and
how
SIG's
can
present
information.
The
my
overall
feeling
is
that
the
release
notes
and
the
changelog
for
kubernetes
is
not
the
appropriate
place
for
this.
A
The
problem
that
we
have
is
there
isn't
currently
a
an
alternative
presentation
mechanism
for
that
right,
so
so
to
Aaron's
point
earlier
they
were
thinking.
Maybe
is
the
blog
the
right
place
for
people
to
do
this
and
to
Caleb's
point
from
the
from
the
cig
release
call
two
weeks
ago.
The
ability
to
or
the
the
privilege
to
to
be
able
to
put
your
notes
in
this
changelog
is
exactly
that
right.
It's
a
privilege,
right,
it's
not
a
right.
A
The
expectation
should
be
for
people
to
give
us
the
information
ahead
of
time
right
release,
notes
Docs,
whoever
should
not
be
tracking
you
down
to
try
to
figure
out
how
to
collate
this
stuff
in
time
for
the
release,
and
if
it's
out
of
scope,
it
should
not
be
here.
I
think
that
was
the
the
general
agreement.
I
think
we
need
to
to
codify
that
as
policy
there
isn't.
There
is
a
there
is
a
issue
open
that
I
will
link
in
the
notes.
Give
me
a
second
fantastic,
so.
E
E
It
also
was
an
attempt
to
address
the
fact
that
the
quote
the
release
notes
attached
to
pull
requests
are
themselves
not
high
enough
quality
to
present
in
a
a
what
I
guess
what
I
was
considered
to
be
a
high
quality,
changelog
or
lease
notes,
product
I
think
you
know,
you
know
as
released
to
I
guess
the
organization
I
would
look
to,
and
I
have
looked
to
projects
like
fedora
for
inspiration.
Like
you
look
at
four
doors
release
notes.
It
is
for
each
version
of
keturah.
E
There
are
sections
that
are
relevant
for
each
of
the
personas
that
they
project
has
identified
that
are
relevant
there.
So
you
know
desktop
users,
dis,
admins
developers,
etc,
and
so
the
major
theme
section
was
attempt
to
create
something
similar
where
cig
would
be
able
to
summer.
I'll
give
a
summary
of
the
pull
request
that
went
into
the
release.
Now
we
have
definitely
drifted
from
that
ideal,
and
so
we
can
I
guess
we're
now
at
the
position
of
kind
of
decide
what
to
do
now.
E
I
think,
there's
still
a
lot
of
value
and
driving
those
summaries
of
what
what
happens,
but
I
also
agree
that
it's
not
useful
to
duplicate
that
with
the
updates
to
the
community
meeting
and
that
the
changelog
we
have
needs
more
any
you
know
more
long-term
editorial
support
and
I
would
love
to
talk
with
anyone
about.
You
know
trying
to
provide
that
kind
of
staffing,
long
term,
at
least
from
where
we.
B
B
Sig
API
machinery,
you
know
server
side
apply.
You
know,
you
know
push
through
seven
enhancements
designed
to
support
server
side
of
the
block,
it's
actually
in
the
release
and
I'm.
Looking
for
the
theme
section
to
supply
me
with
some
sort
of
big
picture
view
over
the
you
know,
300
lines
of
individual
enhancements
right.
E
B
E
To
see
you
know
that
all
the
things
were
that
many
of
the
things
are
working
say
on
a
stability
development
fee,
and
it
has
its
pertinent
to
that
individual
sig.
So
I,
like
also
to
see
from
sig
note
additional.
You
know
refactoring
of
Jeepster
piece
forward
additional
metrics
out
of
public
that
are.
B
E
Running
a
kubernetes
cluster
and
so
I
would
like
to
see
sig
p.m.
most
likely
as
the
source
of
these
development
things,
as
you
know,
kind
of
serving
in
their
role
as
Crofts
project
coordination
not
necessary
early.
Now,
the
stakes
coming
up
with
the
themes
themselves,
because
I
yeah
I
agree
have
not
proven
to
work.
We
says
intended
I.
D
I
can
respond
so
I
I
feel
like
the
release.
Themes,
Kate
I
said
this
in
there
at
least
team
meeting
on
Monday,
I
guess
and
to
say
what
I
said
in
CPM
again.
Caleb
I
share
that
aspiration,
but
this
is
open.
Source
I
have
yet
to
find
anybody
who
can
say,
thou
shalt
to
do
this
and
everybody
goes
and
does
it
in
fact
explicitly
written
in
sick
teams.
Chartered
sig
p.m.
doesn't
have
the
authority
to
say
that
yeah.
A
E
But
I
guess
my.
My
approach
has
been
to
provide
the
to
work
on
the
you
know,
the
proxies
that
will
hopefully
all
dovetail
and
allow
the
release
that
one
first,
given
that
we
seem
additional
control
over
the
rate
of
change
the
project
and
then,
after
that,
to
work
with
the
project-wide
groups
like
PM
and
architecture,
to
move
that
dating
off
of
the
dismissal.
The
shoulders
of
the
newly
steamed
like
a
need
to
occur
earlier.
B
E
D
D
Maybe
some
of
these
are
linked
to
these
things
called
enhancements,
and
maybe
some
of
these
PRS
also
come
from
SIG's,
and
so
we'll
ask
the
SIG's,
like
hey
of
all
of
these
PRS?
What
are
the
most
important
things?
And
maybe
some
of
these
things
are
the
enhancements
over
here
and
what
I
feel
like
has
evolved
over
time.
Is
we've
done
this
work
of
asking
everything
of
SIG's
from
a
Content
perspective,
but
then
we've
never
actually
mapped
it
like
reduced
the
map.
D
D
You
know
reverse
engineering,
the
narrative,
that's
typed
out
by
an
army
of
monkeys,
that's
riding
on
a
herd
of
cats
like
that's
what
release
notes
is
and
I
want
to
give
them
as
much
power
and
authority
as
they
can
to
do
that,
so
just
for
getting
all
the
tooling
and
stuff
for
a
second.
If
it's
purely
from
the
do
the
humans
have
the
ability
to
do
the
thing,
I
always
support
release,
notes
like
removing
anything
they
feel
like,
isn't
relevant
and
making
it
making
release.
E
What
I
guess
I
am
saying
is
that
after
doing
this
couple
times
and
not
having
that
beat
the
final
product
I,
it
is
my
assertion
now
that
it
is
because
we
have
no
way
of
enforcing
that
requirement
or
that
agreement
amongst
ourselves
with
any
sort
of
tool
so
that,
even
though
we
agreed
as
humans
and
that
in
theory
gave
allows
an
individual
once
selected
to
remind
the
group
of
that
power,
it
has
not
been.
It
is
not
well.
I
am
arguing.
We
need
additional
tools
that
help
that
person
wield,
that
responsibility
and.
D
I
agree
with
that
everything
you
and
I
and
Steven,
and
other
people
here
have
been
doing,
is
all
in
an
effort
to
try
and
put
in
guide
rails
and
improve
the
stability
of
kubernetes
over
time.
I
was
really
trying
to
make
the
point
that
themes
are
not
this
top-down
thing
that
push
themes.
Are
this
thing
that
organically
happened
that
are
humans,
trying
to
reverse-engineer
themes
and
clustered
like
things
together,
and
this
is
what
we
started
when
we
met
with
MIT
and
Kaitlyn
start
talking
about
from
the
communications
and
marketing
perspective.
D
How
are
we
going
to
describe
the
shape
of
this
release,
setting
aside
stability
as
something
we
should
constantly
be
striving
for,
like
what
are
the?
What
are
the
top
three
things
that
I
can
say
that
this
release
offers
right
and
so
I
want
to
give
the
release,
notes,
people
the
ability
to
to
say
that
not
to
have
to
like
way
everybody's
input
equally
and
try
to
give
everybody
fair
time.
Look
I,
like
I'm
gonna,
find
it
for
an
editorial
voice
to
be
a
dictatorial
voice.
I'm
really,
okay
with
it
right.
E
I
guess
I
I
am
I
believe
that
we
can
in
fact
push
down,
seems
top-down.
I,
think
that
certainly,
that
is
defining
the
scope
of
what
kubernetes
is,
which
I
hope
is
something
we
were
visit
on.
A
release
by
release.
Nearly
continuous
basis
is
in
the
purview
of
cig
architecture,
and
so,
if
they
can't,
then
I
don't
understand
really
what
the
purpose
of
that
cig
is
if
they
are
not
able
to
define
what
kubernetes
is
on
a
continuous
basis.
E
I
think
that
that's
definition
of
what
kubernetes
is
and
should
inform
what
development
themes
are
I
mean.
So
I
do
believe
that
if
we
are
successful-
and
you
know
managing
the
project,
we
will
be
able
at
some
point
to
have
themes
flow
from
a
group
like
Sagarika,
texture
or
cig
p.m.
not
that
is
just
dictating.
E
You
know,
laterally
what
people
should
work
on,
what
is
able
to
help
guide
the
project
by
informing
what
we
should
be
working
on,
where
we
should
be
focusing
our
energy
and
I
plan
or
I
hope
to
support
that
process,
I
think
by
incentivizing
the
participants
to
participate.
So
that's
what
I'm
talking
about
by
like
getting
to
submit
to
you?
If
you
cannot
have
your
pull
request
merged,
then
you
know
I
think
it's
pretty
obvious.
You
won't
need
to
conform
to
the
process
that
allows
your
pull
request
to
be
merged.
If
you
care
you.
I
A
I
I
In
it
goes
till
five
four,
oh
five
forty-five.
I
If
I'm
going
from
say
one
twelve
one
to
one
fourteen.
What
all
changed
that
I
care
about
so
being
able
to
actually
filter
based
on
the
technology
or
the
specific
areas
would
be
kind
of
neat
and
nice
and
also
let
people
search
on
stuff.
This
is
literally
just
taking
the
raw
JSON
out
of
Mike's
tool
and
then
just
dumping
it
into
a
little
API
that
you
can
search
on,
and
then
we
do
the
things.
So
this
was
again
just
a
weekend
project
I'm,
not
sure
if
I
should
continue
doing
the
thing
with
it
or
not.
I
A
There
are
talks
about
like
how
to
present
caps
in
a
way
that
is
like
easy
to
sort,
and
this
is
close
to
I
mean
this
is
a
you
know,
at
least
something
of
what
it
could
look
like
right,
being
able
to
filter
by
SIG's
or
the
you
know
the
participating
SIG's
different
things
like
that:
I
I,
like
it
like,
if
it's
a
matter
of
like
figuring
out
how
to
make
it
more
human,
readable,
yeah
like
yeah.
This
is
a
step
in
the
right
direction.
B
I
B
Just
yeah,
you
know
we
have.
We
have
outreach
interns
coming
up.
We
have
google
Summer
of
Code
coming
up
that
sort
of
thing.
So,
looking
at
it,
you
know
for
the
next
release
cycle.
We
could
potentially
have
an
intern
turn
this
into
a
little
bit
more
of
a
tool
if
you'd
be
interested
in
mentoring
them.
E
E
This
enhancement
is
working.
How
do
I
know
it
was
not
working
what
metrics
aren't
she's
injecting
the
system?
What
dependencies
on
other
components
of
the
system
are
required
for
this
component
to
work,
and
that
needs
to
go
into
a
larger
document.
That's
part
of
the
test
in
my
mind,
and
so
you
know
there's
the
first
part
about
getting
that
living
in
a
place,
because
you
know
you
probably
need
a
to
write
on
that
as
you're
going.
F
E
E
In
other
places,
the
release
notes,
content
itself,
which
also
needs
to
increase
in
terms
of
I,
guess,
understand
ability,
not
I,
guess
through
unnecessary
shade
on
contributors
here,
so
I
think
that
those
are
two
places
where
there's
a
lot
of
I
guess
value
or
not
all
that
much
effort
or
those
are
just
kind
of
how
I,
how
I
see
the
the
challenge
currently
and
it's
a
Content
problem
as
much.
It
is
a
tooling
problem,
I.
I
I
One
of
the
things
I'll
note
is
like
I
said
in
the
background.
This
is
just
a
JSON
file
that
gets
output
from
Mike's
tool
and
the
reason
I
kind
of
built
it
like
that
is
a
a
database
seems
a
little
heavyweight,
even
if
we
have
like
30
releases
worth
of
release
notes
but
B.
That
means
that
those
release
notes
are
in
a
git
repo,
so
we
can
continually
be
able
to
improve
them.
Someone
could
go
through
and
add
more
metadata,
and
then
we
can
support
said
metadata
that
was
kind
of
my
thinking
behind
that.
J
Sorry
I
just
want
to
chime
in
real
quick
is
Jeff
there.
This
is
awesome
and
I
think
when
you
look
at
it
from
like
a
double-click
point
of
view,
you
get
a
lot
of
great
data
in
here
coming
from
a
pass
of
where
I've
had
to
sit
there
and
look
at
the
enhancements
and
try
to
track
ok.
Well,
what
happened
in
113
versus
114?
What
said
115
I
know:
you're,
probably
not
accepting
feature
requests
already,
but
it's
like.
J
E
Either
at
least
tooling
I
guess
I
would
suggest
that
you
Mike
Jett
and
Kendrick.
You
should
should
work
on
a
time
where
you
can
I
think
if
you'll
walk
through
where
we
are
with
the
kept
tooling
Edward,
not
legacy
duplicative,
because
the
there's
a
lot
I
guess
cool
I
mean
you'll,
see
or
you
know,
you'll
have
opinions
when
when
we
sink
to
see
what
the
gap
there
is
and
how
much
where
you'd.
F
D
E
E
I
Definitely
probably
won't
be
till
tomorrow
morning,
fair
warning,
but
I'll
get
it
done
the
morning
yeah.
A
A
To
have
you
it's
your
party,
all
right,
so
I'm,
going
to
try
to
speed
through
this
well
I
mean
there's
not
really
anything
to
speed
through
the
last
two
items
are
115
planning
and
enhancement,
115
enhancements
and
comms
right,
so
115
planning,
the
all
I
wanted
to
say,
is
if
you
were
on
the
release
team.
If
you
are
a
release,
team
role
lead
or
the
the
release
team
lead
shadows.
You
should
start
considering
the
succession
plan.
We
would
want
to
start
start
getting
that
train
rolling.
A
Four
four
release
team
selection,
once
code
freeze
starts
hitting
so
keep
that
in
mind.
Think
about
your
your
shadows
and
who's
been
performing
really
well
who's
well
suited
to
the
job
who
you
think
should
should
carry
the
baton
moving
forward?
That's
really
it
on
that
point
from
a
enhancements
enhancements
perspective.
We
were
discussing
this
earlier
today
in
sig
Jim
and
it's
my
feeling
that
the
both
the
enhancements
lead
and
the
communications
coordinator
roles
on
the
release
team
are
extensions
of
sig
p.m.
A
and
they're
liaisons
to
the
release
team,
as
opposed
to
being
staffed
in
staffed
from
sig
release.
So
my
feeling
is
for
one
15
I'd
like
to
move
the
staffing
for
enhancements
and
for
communications
into
sig
p.m.
as
opposed
to
from
the
release
team
perspective.
I'll
still
be
looking
at
the
the
people
who
have
been
shadowing
and
and,
of
course,
synching
with
the
people
who
were
currently.
Those
role
leads
to
get
feedback
on
who
best
and
what
we
can
be
doing
to
improve
the
process
overall
there.
A
A
One
other
suggestion
that
we
had
was
a
suggestion,
but
iterative
improvement
is
moving
away
from
enhancement
tracking
issues
and
into
enhancement
tracking
PRS
right
so
being
able
to
codify
the
the
means
that
people
submit
changes
for
for
a
release
right
and
capturing
that
in
a
repo.
So
you
know
it
goes
through.
It
goes
through
an
approval
process
right
where
we
can
easily
aggregate
the
list
of
things
that
are
supposed
to
land
in
the
release
and
a
human
doesn't
have
to
do
that.
A
E
E
Ultimately,
it
is
font
ability
of
the
pairs
of
chairs
to
ensure
that
a
release
team
is
staffed,
but
once
there
is
a
release,
manager,
I
think
we
should
continue
with
the
with
the
previous
art
where,
whereby
the
release
manager
is
ultimately
responsible
for
accepting
people
onto
the
release
team
now,
I
would
think
that
those
people
primarily
should
have
should
have
spent
most
of
their
time
in
cig
p.m.
but
I
guess
I'm,
not
I'm,
not
convinced
that
any
changing
of
the
language
we
have
is
helpful
in
that
effort.
D
So
I
have
a
random
opinion
that
I
think
is
related
to
that
and
may
try
that's
off
topic,
but
so
I
agree.
One
of
the
strengths
of
the
release
team
is
that
it
is
all
contributors
can
show
up
and
help
out.
That's
what
generated
a
thunderous
amount
of
interest
when
we
publicized
the
fact
that
we
had
a
survey
for
release
team
shadows
now
I'll
be
honest
as
the
released
team
we'd.
D
This
was
way
more
people
in
a
much
higher
level
of
than
I
was
comfortable
with
and
today,
I
still
don't
even
know
if
it's
actually
effective,
like
I,
had
no
way
of
vetting
this
year.
Volume
of
people
that
were
coming
in
I
really
liked
the
level
of
interest,
but
I
don't
actually
know
who's
doing.
What
and
like
of
the
people
who
showed
up
and
said
they
wanted
to
help
and
then
bounce
the
way
like
what
we
can
do
about
that.
So
I
would
just
kind
of
be
mindful
of
that.
D
Don't
actually
feel
super
gelled
because
there
are
like
30
people
who
show
up
all
the
time.
Just
a
random
thing
like
if
we're
gonna
do
the
questionnaire
again.
What
are
we
gonna?
Have
the
questionnaire
ready?
By
will
that
work?
Should
we
put
barriers
on
the
number
of
people
who
show
up
and
how
about
things
like
that?
But
again,
this
is
just
me
being
a
curmudgeon
like
I
voted
with
my
feet.
I
didn't
use
a
questionnaire.
D
I
talked
to
my
shadows
personally:
I
interviewed
them
personally
and
just
went
that
route
and
let
the
rest
of
it
proceeded.
However,
at
me
and
so
for
all
I
know,
this
is
worked
wonderfully
for
all
of
you.
I
just
felt
the
need
to
share
my
opinion
or
speak
up,
because
that's
how
it's
worked
for
me
and
I'd
love
to
be
shouted
down
with,
like
nothing
but
praise
for
the
way
the
process
worked
for
everybody
else.
A
So
I
popped
a
link
into
the
chat.
That
is
a
issue
about
the
release
team
survey,
improvements
to
Aaron's
point.
If
you
think
we
should
not
do
the
survey
again,
if
you
think
there
are
things
that
we
should
fix
about
it,
if
you
feel
like
there
were
too
many
people
coming
at
you,
I
know,
for
you
know,
I
know
personally
that
you
know,
as
as
the
person
who's
gone
like
very
the
shot
like
the
survey
is
available.
Like
the
you
know,
the
peanut,
you
know
the
the
PM's
DMS
are
constant
right
or
going
hey.
A
Okay,
do
we
have
an
update
on
who?
How
we're
staffing
CI
signal,
like
I,
don't
know
I'm,
not
the
person
doing
it
right
so,
like
the
process
overall
can
be
overwhelming.
I
think
I
think,
like
even
doing
the
tracking
issue
and
and
and
trying
to
follow
up
with
everyone,
who's
available
or
interested
in
in
that
is
it's
difficult
and
in
and
of
itself
so
like.
A
If
there
are
improvements
for
this
process
before
we
get
the
train
rolling
again,
the
release
team,
like
you,
should
feel
that
it
is
your
responsibility
as
a
release
team
to
suggest
improvements
for
that
process.
You're
the
ones
who
are
going
through
it
and
we'll
you
know
and
and
your
shadows
will
be
going
through
it
next
cycle
as
they
pick
people.
So
so
please,
please,
give
feedback.
I
only
have
so
much
context.
D
A
D
A
To
concentrate
on
this
stuff,
no
I'm
saying
not
you
as
release
lead,
but
the
release
team.
It
is
everyone's
responsibility
to
help
out
with
this.
You
know,
I
think
that
I
mean
that's
part
of
the
reason.
I
bring
this
up
before
you
jump
into
code.
Freeze
right:
we've,
we've
got
a
month
and
change
out
from
the
release.
I
think
it's
enough
time
to
give
some
consideration
about
how
the
process
can
be
improved.
Moving
forward.
E
Yes,
you
know
as
chairs
it
is
I,
guess
our
ultimate
responsibility
to
Shepherd
long-term
improvement.
So
I
can
understand
you
know
until
you
know,
release
day
plus,
probably
three
or
four
to
drain
from
the
stress
of
getting
the
release
out
the
door
as
the
release
manager
to
not
really
expect
any
any
participation
there.
That's.
A
That's
fair,
but
as
chairs,
we
are
also
responsible
for
being
the
voice
of
the
release
teams
and
the
associated
sub
projects
right.
So
we
want
to
make
so
I.
I
say
that
to
say,
I
want
to
make
sure
that
your
voice
is
counted
in
the
decisions
that
we
make
or
try
to
make.
So
if
you
have
opinions
on
this
process
and
ways
for
to
improve
the
process,
we
want
to
know
about
it
and.
E
I
think
I
guess
I
heard
a
couple
in
there
one.
It
would
be
helpful
to
have
additional
descriptions
of
the
requirements
required
to
be
successful
in
the
role
and
perhaps
some
way
of
allowing
candidates
to
provide
that
information.
You
know
like
a
CV
and
if
there
was
another
normal
kind
of
job
interview
before
they
engage.
F
I
E
I
guess
I
mean
I,
guess
we're
trying
to
specifically
lick
limit
a
bit
of
that
enthusiasm
or
it's
temper
it
a
bit
with
some
reasonable
requirements
that
shows
that
you
are
capable
of
fulfilling
business
rule,
because
there's
overhead
to
evaluate
people,
fitness,
horrible
and
I-
mean
I
agree.
I
mean
it
is
great
to
see
how
successful
the
shadow
box
has
been.
It's
just
that
we,
it
seems
that
we
are
now
once
again
exceeding
our
interest
is
exceeding
our
ability
to
manage
it.
So.
I
What
we
did
this
cycle
is
we
let
each
lead
pick
their
shadows
and
they
picked
the
amount
that
they
thought
they
could
handle
on
that
varied
by
the
roll
and
I
would
say
talking
to
the
other
shadows
and
needs
that
it
seems,
like
that's,
been
pretty
successful
and
they've
gotten
a
lot
of
help
from
a
lot
of
people
who
might
not
have
even
necessarily
had
any
experience
yet
at
all.
Okay,.
A
So
how
about
how
about
we
do
this?
Since
we've
we've
gone
two
minutes
over,
we
we
parked
this
discussion.
Let's
go
to
the
people,
the
release
team.
We
will
show
up
for
some
release
team
meeting
and
and
have
a
discussion
about
how
we
can
improve
the
process.
Moving
forward
sounds
good.
Everyone
I
would.