►
From YouTube: 20230216 SIG Arch Enhancements
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
Hello:
everyone
oops,
oh
sheesh,
that
was
a
loud
notification.
It's
Thursday
February,
16
2023.
This
is
a
Sig
architecture,
enhancement
sub
project
meeting.
We
are
under
the
kubernetes
code
of
conduct,
so
be
good
to
each
other.
If
you
have
any
problems,
please
feel
free
to
reach
me
off
of
the
call,
and
we
can
talk
about
it.
So
we
have
I'm
Kirsten
I'm,
an
enhancement,
sub
project
owner,
and
we
have
basically
one
topic
on
the
agenda
for.
A
A
Let's
I
think,
let
me
can
we
do
sergey's
topic
first
and
I.
Think
we'll
just
make
it
a
separate
one.
C
Question
oh,
like
yeah
in
the
past,
I,
came
to
to
the
meeting
and
asked
about
updating
the
template
to
remove
the
mention
of
dynamic
mobile
config
and
before
that
there
were
another
removal
like
or
addition
perhaps
like
during
the
127
release.
We
also
I
also
asked
for
agents
a
question
about
node
resources,
and
this
question
was
added
in
the
middle
of
the
release
process.
So
many
people
got
affected
by
that
which
is
not
ideal
positive
side.
C
Is
we
get
very
good
replies
on
this
question,
so
it
helped
a
little
bit
I
think
it
made
kubernetes
template
better,
so
but
I
mean
process
wise,
definitely
wasn't
the
key
like
it
was
in
the
middle
of
process
and
you
didn't
update
existing
caps
like
people
just
didn't
know
what
to
look
for.
They
didn't
know.
There
is
a
new
Pro
new
question
and
like
when
release
managers
would
look
at
the
template.
They
will
find
it
and
they
will
erase
the
alert
and
it
will
be.
A
C
Ketchup
PR
so
not
ideal,
From
perspective,
so
for
removal,
Dynamic,
couplet
config
feature
it's
just
removal
of
just
like
very
small
like
if
you
look
at
the
pr
I
posted
there.
There
is
a
small
commit
actually
removing
the
question,
but
then
I
also
folded
up.
This
update
to
all
the
bulk
update
of
all
other
types
of
existing
caps
and
a
good
challenge
for
me
was
I,
didn't
want
to
update
all
the
calcs
because
some
of
them
are
already
implemented.
C
So,
if
we'll
do
some
versioning
case,
Mark
purpose
or
like
in
any
way
like
whatever
we
do,
we
either
need
to
make
it
responsibility
of
cap
owner
to
to
catch
up
with
new
questions,
or
we
need
to
make
a
process
of
updating
like
bulk
updating
of
caps
a
little
bit
more
easier.
C
I
don't
know
what
time,
if
you
can
come
off
this,
but
at
least
show
warning
to
something
that
it
wouldn't
build.
Yeah.
A
Right
so,
there's
like,
like
I,
think
that
the
thread
from
what
I
can
tell
between
your
topic
and
Mark's
topic
is
like
there's,
there's
part
of
a
communication
issue
right
because,
like
on
one
hand,
the
the
template,
maybe
should
be
updated,
but
the
real
question
is
like:
how
often
should
the
template
be
be
updated
like
how
critical
is
the
update?
A
And
how
can
we
do
that
in
an
effective
way
like
yours
is
more
straightforward,
I
think,
because
you
know
in
your
own
way,
you're
like
well
I
can
remove
this
no
longer
needed
portion
of
the
template
and
I
can
also
unilaterally,
like
bulk,
update
these
caps,
which
doesn't
really
I,
don't
know.
It
doesn't
seem
to
like
cause
that
much
problem
like
the
pr
that
you
have,
whereas
Marx
is
that
something
was
added
to
the
template
which
shouldn't
have
been
added
to
a
template,
and
people
were
getting
confused
about
it.
A
So
I'm
kind
of
I
kind
of
think,
like
first
of
all,
there's
there's,
there's
like
the
primary
like
thing
is:
how
is
this
communicated
like
I
see
that
there's
a
pull
request
in
the
enhancements
repo
but
I
do
kind
of
think
that
those
types
of
PRS
should
go
into
the
flat
channel
so
that
people
know
about
it.
A
I
also
kind
of
have
concerns
about
piecemeal
updates
to
the
cap
tablet,
because
I
think,
like
so
Mark,
has
this
other
issue
and
I
guess
we're
kind
of
discussing
them
at
the
same
time,
because
these
are
two
distinct
issues.
But
then
they
kind
of
come
to
the
same
topic.
A
Where
the
question
is,
how
do
we
best
make
updates
to
the
Caps
template
right?
Like
that's
the
whole
question
and
I?
Think
in
the
past,
like
there
were
lots
of
little
piecemeal
updates
and
then
we
kind
of
held
off
making.
A
You
know
like
updates
to
the
template
for
about
a
year
and
that's
why
I
think
that
the
pull
request
that
Mark
referenced
really
took
me
off
guard
a
little
bit,
because
I
actually
had
no
idea
that
that
merged,
because
I,
if
I,
would
have
stopped
if
I
would
have
seen
it
I
wouldn't
have
let
it
merged
as
well
so
I'm.
Sorry,
I
drank
a
lot
of
coffee.
C
A
Trying
to
get
myself
I'm
trying
to
get
my
thoughts
together.
So
yes,
right,
like
I,
think
that
versioning
the
cat
template
is
something
that,
like
we've,
talked
about
for
a
long
time
and
I
think
that
the
actual,
adding
a
version
to
a
temp
to
a
template
is
like
a
very
small
piece
of
actual
solution.
Right,
because
adding
a
version
doesn't
really
do
much
like.
If
people
aren't
aware
of
the
changes-
and
we
also
don't
want
to
be
just
updating
versions
of
a
cap.
A
Template
like
every
every
release,
I
mean
that
that's
a
lot
of
churn
for
PR
authors,
I,
think
to
always
be
updating
a
template,
and
so
I
think
that
the
real
question
is,
which
was
something
that
I
wanted
to
actually
go
to
the
prr
meeting
next
week
and
find
out.
You
know:
how
can
we
better
manage
like
some
of
these
genius
that
are
coming
into
the
cap,
template
and
like
thinking
about
in
a
larger
scale,
not
just
VR
changes
but
like
what's
a
good
Cadence
for
those
changes?
And
then
how
can
we?
B
To
like
a
little
bit
of
the
hat
that
I'm
wearing
when
I
filed
this
issue,
I'm,
not
an
enhancements
lead
for
the
127
release
and
a
big
like
I
think
that
if
we
could
somehow
add
the
version
to
the
cap
template
but
then
also
check
like
have
a
PR
check
to
make
sure
that
if
people
are
updating
the
kef
templates
they're
on
the
right
version,
that
could
save
a
lot
of
the
manual
process.
That
some
of
the
enhancements
team
has
to
do
and
also
just
provide
an
earlier
signal
to
the
the
cap
owners.
B
Because
then,
as
soon
as
they,
you
know
open
a
PR.
Something
could
check
and
say,
hey
you're,
not
using
the
latest
version
of
the
cup
template
and
they
don't
have
to
wait
for
somebody
from
the
enhancements
team
to
go
and
look
at
the
like
start
tracking,
their
enhancement
issue
and
look
at
the
pr
and
then
comment
and
say.
Oh
this.
This
part's
missing
I
think
it's
just
a
quicker
feedback.
Loop.
A
For
everybody,
well,
I
think
I,
I,
think
and
I
I
was
on
the
release
team
for
time
so,
except
the
not
I'm,
not
wearing
the
release.
Hat
on
it.
I
think
that
the
version
I
don't
think
that
it's
probably
going
to
end
up
in
the
markdown
file,
because
I
think
that
that's
going
to
be
like
harder
to
parse
like
programmatically
I,
think
that
we
could
put
it
in
the
yaml.
A
If,
if
the
sole
purpose
is
to
say
like
hey,
you
didn't
update
your
template
right,
but
I
think
that,
even
if
somebody
does
update
the
template,
there's
still
that
question
for
the
enhancements
people
to
say
like
hey
like
did
you
actually
fill
it
out,
did.
B
A
But
I
think
that
what
happened
from
what
I
can
tell-
and
you
can
correct
me
if
I'm
wrong
PR-
went
in
to
make
a
change
to
the
cup
template
while
people
were
doing
their
enhancements
it
created.
You
know
another
question
that
they
had
to
answer
that
they
hadn't
been.
You
know
aware
of
I
I,
actually
wasn't
aware
of
it
at
all.
It
wasn't
communicated
in
any
like
real
way
like
there
wasn't
an
announcement
or
anything.
A
It
happened
in
the
middle
of
a
release
as
opposed
to
before
release,
and
it
basically
took
people
by
surprise.
They
had
to
go
back
and
update
their
cap
and
it
was
just
an
all-around
drag.
There
was
some
confusion
for
the
enhancements
team
as
well,
because
they
didn't
really
they
didn't
really
know
and
they're.
Getting
a
lot
of
mixed
signals
right,
like
I,
think
that
that
yeah.
A
A
It
thank
you
review,
so
I
think
that
that
was
probably
like
a
mistake
and
I.
Don't
think
that
the
intention
was
to
confuse
people,
but
I
think
that
the
fact
that
the
mistake
happened
was
a
problem
right
because,
like
in
your
in
your
issue,
you
referenced
the
test
plan
section
update,
but
when
that
happened,
I
think
that
was
like
a
year
ago.
That
happened
before
the
release
and
an
email
was
sent
out
to
kadev
and
to
the
Sig
leads.
A
To
the
release
team,
so
everybody
was
more
or
less
on
the
same
page
like
does
that
mean
that
everybody
follows
directions?
No,
but
that
means
that,
like
you
know,
people
were
let
know
ahead
of
time.
So
I
think
that
you
know
a
version
wouldn't
have
helped
us
in
this
case.
You
know
like
of
like
because
there's
like,
like
I,
think
versioning.
The
cap
is
definitely
important,
but
that
wouldn't
have
helped
us
in
this
case
right
because.
C
A
B
B
The
release
start
and
enhancements
freeze,
yep,
but
I
I
do
kind
of
feel
that
it
would
be
helpful
to
have
a
PR
check
somehow
to
make
sure
that
the
the
authors
are.
You
know
targeting
the
right.
B
The
right
person
template
because
I
do
see
cases
too,
where,
like
sometimes
the
PRS
that
are
updating
the
marked
up,
like
the
markdown
files,
stay
open
for
several
releases,
because
they're
trying
to
progress
a
feature
to
a
certain
State
and
all
the
discussions
are
happening
in
the
pull
request.
And
then
it
slips
from
One
release
to
the
next
so
being
able
to
have
that
reminder
of
like
when
they
push
updates
rerun
the
pr
checks
and
make
sure
it's
on
the
latest
version
of
the
cap.
Template
I
think
could
still
be
beneficial.
A
Right
right,
no
I
I
actually
agree
with
that.
I
think
like
from
previous
discussions,
because
I
actually
proposed
something
similar
to
this
like
in
the
past.
So
it's
not
the
first
time
so.
I
I
think
that,
like
there's
a
couple
problems
here
like
there's
like.
A
Of
how
do
changes
like
this
is
like
almost
like
an
incomplete
solution
like
in
a
way
like
just
putting
a
version
on
the
cap,
because
the
question
is
really:
how
do
we
update
the
cap,
template
and
there's
like
these
competing
there's
competing
interest
right
because
it's
like
well,
the
template
will
need
to
get
updated
at
points
in
time
right
and
there
are
people,
maybe
the
prr
team,
maybe
other
people
who
have
these
ideas
that
they
think
are
a
good
idea
to
implement
and
we
don't
want
them
to
just
have
PR's
like
outstanding
forever,
because
it's
not
the
right
time.
A
B
A
Know
they
also
need
to
kind
of
be
aware
of?
What's
expected
of
them,
so
part
of
it
is
you
know
it
might
be
branching.
It
might
be
I
think
before
I
propose
just
like
having
a
draft
cap
template
where
we
put
all
of
the
changes
in
and
then
that
kind
of
gets
squashed
into
like
the
version
which
would
allow
people
to
like
work
on
the
cast.
It
would
allow
people
to
in
some
way
like
diff
the
cast
versions,
because
that's
like
a
big
deal
like.
A
You
have
to
be
able
to
see
what
the
difference
is
and
if
you're
kind
of
constantly
merging
into
the
mate
into
main,
instead
of
another
Branch
or
just
like
a
separate
directory,
you
really
lose
the
ability
to
easily
say
these
are
all
of
the
changes.
So
that's
like
kind
of
what
the
versioning
like
it's
it's
it's
a
little
bit
harder
than
just
like
slapping
a
version
on
the
template
and
calling
it
a
day
and
I
kind
of
just
want
to
talk
to
like.
A
A
The
idea
of
like
kept
templates
cannot
be
updated
all
the
time
and
the
problem
with
that
is
like
the
ownership
of
like
different
directories
and
everything
else
in
GitHub
yeah,
but
also
not
having
like
a
clear
process
and
not
wanting
to
block
some
updates.
So,
let's
make
it
to
do
actually
because,
like
I
I
think
that
these
are
like
this
is
really
important
and
so
like
we
want
a
version.
The
cap
template
but
like
we
don't
want
to
want
to
block
change
like
opposed
changes
to
the
template,
I'm
just
spreading.
B
So
I
I
know
I
kind
of
maybe
disagree
a
little
bit
about
blocking
the
proposed
changes,
at
least
for
a
timeline,
because
another
thing
that
came
up
too
is
and
like
I
think
we
need
to
to
establish
some
boundaries
around
when
the
kept
templates
can
change.
Yeah.
A
Yeah
I
mean
I
think
that
what
we're
really
talking
about
in
general
is
like
a
a
tablet.
Versioning
policy
yeah
like
so
it's
like
you,
can
slap
a
version
on
it,
but
the
question
was
really
like:
what
does
that
represent
and
part
of
those
questions
are
going
to
be
like
how
often,
how
often
do
we
do?
We
roll
changes
to
the
template.
A
A
You
know
versus
like
a
major
thing
that
you
might
want
to
Target
at
a
specific
release
of
changes,
so
I
think
we're
talking
about
like
I'm,
just
taking
some
notes
here,
because
I'm
excited
that
other
people
are
talking
about
this,
because
I
was
proposed
this
and
talked
about
this
like
more
than
a
year
ago
and
people
weren't
very
interested
were.
A
There
was,
there
was
a
lot.
There
was
a
lot
of
like
churn.
There
was
like
the
Cadence
cap,
there
was
the
pandemic
and
then
there
was.
A
Process
that
was
kind
of
outstanding,
so
it
just
didn't
feel
like
the
right
time,
I
think
to
pursue
it,
but
now
that
I
think
we
have
like
a
more
established
enhancements
collection
process
relatively.
B
B
A
As
the
enhancements
lead,
like
I
mean
we
have
like
the
prr
reviewers,
and
they
do
quite
a
lot
of
like
review
of
the
cats,
but
the
enhancements
team
also
like
we're
not
seeking
to
fully
automate.
You
know
like
all
of
their
work
like
they
still
are
reading
the
Caps
to
make
sure
that
there
are
sufficient,
like
yeah
answers
to
some
of
the
questions.
I
mean
that
that
also
provides
something
of
a
filter
on
the
quality
that
ends
up
going
to
like
the
pr
reviewers.
So.
B
C
I
want
to
put
plus
one
on
like
more
Automation
and
in
reality,
like
being
authoring
a
lot
of
caps.
There
are
so
many
sorts
of
frustration
that
one
more
sort
of
frustration
doesn't
really
bother
me
as
long
as
it's
automated
source
of
frustration.
So
I
want
to
know
that
my
cap
is
up
to
date
with
the
latest
like
what
I
require
like
whatever
template
is
required.
Just
let
me
know
I
will
update
my
questions.
I
will
like
reformat
it
the
way
I
need
it.
I
don't
want
to
know,
learn
about
it
last
minute.
C
So
as
long
as
it's
not
last
minute
and
I,
don't
need
to
learn
a
process
about
versioning
my
cap
with
regards
to
template
right,
then
I
will
be
golden,
so
if
there
will
be
a
process
of
Wars
Nick,
let's
not
put
it
as
a
burden
of
learning
about
versioning
to
cap
authors
like
just
let
them
know
like
this
is
what
is
what's
your
PR
like
what
you
kept
supposed
to
look
like
if
it's
different
then
like
I
will
update
it
like
I'll
fix
it,
but
I
don't
want
to
learn
about
like
okay,
I
I
will
change
the
version
of
my
cap
to
this
previous
version
because
it
it
didn't,
have
this
question
so
I
don't
want
that.
A
C
To
version
template,
but
it
shouldn't
be
a
burden
on
cap
authors
to
learn
about
versioning
and
know
about
it
anything
except
I'm,
not
yeah.
My
PR,
like
my
cap,
is
not
doesn't
missing
this
kind
of
questions
and
such
so.
A
Yeah
I
think
that's,
that's
infinitely.
I
think
reasonable
and
I
think
that
one
thing
to
aim
like
just
we're
just
like
spitballing
and
throwing
ideas
out
there,
but
one
thing
to
aim
I
think
is
to
whatever
we
decide
on
how
to
version
it
and
whatever
the
threshold
for
releasing
the
new
kept
version
is
I.
Think
you
really
want
that
solidified
before
the
start
of
the
release,
because
you
need
to
you
know
really
let
the
enhancements
team
know
you
need
to
know,
you
need
to
make
sure
that
any
required
automation
is
in
place.
A
And
then
you
need
to
know
that
on
that
first
day
that
the
release
opens
the
enhancement
lead
who
sends
out.
You
know,
the
hay
of
enhancements
are
now
being
collected
or
whatever
they
send
out
can
also
let
people
know
exactly.
The
template
has
a
template.
Sorry,
the
template
has
changed.
These
are
the
changes.
If
you
have
any
questions,
let
me
know
but
FYI.
This
is
what's
happening
and
so
I
think
like
this
all,
has
to
be
done
before
the
first
day
of
the
release,
because
you.
A
Want
the
enhancement
theme
like
scrambling
to
find
out
like
they
need
to
know,
and
then
that
would
also
preclude
any
changes
during
the
release
cycle.
For
the
authors
like
it
like,
you
definitely
can't
make
changes
to
the
template
during
the
release,
like
that's
I'm,
just
taking
it
as
a
mistake
that
it
merged,
but
I
think
that
we
can
do
a
better
job
at
preventing.
That
mistake,
like,
in
a
general
sense.
C
Many
caps
are
surviving
many
releases
so
like
if
this
communication
may
not
necessarily
help
like
it's
a
like.
Let's
say:
I
have
a
feature
going
from
beta
to
GA
and
I
generally
wait
two
releases
before
I
go
to
ga
to
reduce
the
minimum,
so
I
would
miss
one
notification
for
sure.
Second
notification,
maybe
I'm
working
on
this
right
now
but
I
mean
maybe
like
three
releases
later
I
gave
the
feature
and
like
cap
has
definitely
changed
a
lot
so
kept
up
late.
So
I.
C
Will
those
notifications
not
necessarily
helpful
for
me,
but.
C
A
No,
that's
really
helpful,
so
we
don't
want
to
over.
We
don't
want
to
have
just
a
PR
check.
We
want
to
have
a
PR
check,
but
we
also
want
to
have
a
widespread
communication.
We
want
to
have
the
enhancements
team,
no,
they
can't
not
know
about
the
change
and
we
want
to
basically
block
those
merges
to
the
template.
C
A
A
Being
a
little
more
thoughtful
about
how
those
changes
are
rolled
out
because,
like
I,
think
that
Mark
in
his
issue
actually
said,
like
it'd,
be
really
helpful
to
have
a
gif.
You
know.
B
A
Mean
because
that's
like
I
mean
I,
don't
know
if
I
don't
know
how
to
do
that
and
I
can
find
out.
But
I
think
that,
like
if
you're
looking
like
because
you're
exactly
right
like
there
are
like
the
big
things
that
change
but
then
there's
little
things
that
change
it
you're
never
going
to
catch
like
Star
days,
teens
right
there,
where
he
like,
removes
something
that.
B
A
Longer
exists
and
that's
not
something
that
you
would
necessarily
catch
if
you
were
just
you're
just
checking
headers
or
something
like
that,
so
I
think,
like
the
the
full.
The
full
diff
would
be
nice.
C
Yeah
I
mean
there
is.
There
may
be
concerns
that
people
changing
questions
just
a
little
bit
of
pharmaceutical
question.
I
I
saw
people
just
making
them
in
a
whole
line
or
anything,
but
you
will
say
say
to
them,
like
your
change
will
fail
validation,
you're
looking
for
exact
substring.
Yes,
it's
frustrating,
but
like
just
deal
with
that,
people
will
deal
with
that
like
I.
Don't
think
it
will
be
a
problem.
C
So
as
long
as
we
have
a
rules
clear
and
it
this
rule
is
really
helping
in
a
long
game
like
it
really
helping
you
to
get
your
PR
merged,
then
people
will
follow
I,
don't
think
it
should
be
a
problem
to
just
search
for
substrings
yeah.
B
B
C
A
Okay,
I
think
that
I
totally
agree
with
you
guys
so
I'm
excited
that
somebody
cares
about
this
right
now.
Okay,
cool
I'm,
gonna
I.
Think
I'm
gonna
try
to
make
like
a
document
of
ideas
for
this,
because
I
think
that
this
evolves
more
than
just
like,
as
we've
just
discussed
like
slapping
a
version
onto
something
and
calling
it
a
day
and
maybe
I
can
put
some.
A
B
A
B
A
A
A
C
A
Pr
author
was
like
oh
I,
didn't
intend
for
that
to
happen,
like
I
didn't
want
people
to
actually
update
the
same,
but
basically
people
are
iterating
on
the
actual
template,
which
I
think
is
also
like
a
problem
so
yeah.
So
that's
like
three
General
buckets
I
think
the
automation
is
basically
checks
on
open,
PRS.
A
A
Etc
and
then
like
I,
guess
this
one
should
go
before
that
right
like
well.
What
is
the
new
version
yeah
and
then,
when
is
a
version
cut
right
because
we're
not
going
to
cut
a
version
for
every
tiny
change
to
the
cap.
Template
like
there
has
to
be
an
idea
of
like
a
critical
mass
of
change,
or
maybe
a
really
important
change
that
everybody
agrees
is
important,
but
there
has
to
be
some
sort
of
like
standard
for
what
a
version
is
and
where
that
kind
of
draft
template
lives,
because.
A
Say
like
oh
like
because
then
then
it
just
ends
up
being
like
this
weird
like
what
happens
to
the
Caps
right,
like
everybody
has
everybody
has
their
PR's
open
forever,
and
you
can't
really
see
what
you
have
so
you
kind
of
want
those
merged
somewhere.
It
could
be
a
different
branch,
it
could
be.
You
know
like
a
staging
directory
or
something,
but
then
I
think
that
would
allow
us
to
also
do
a
diff,
which
would
be
nice.
A
Draft
can
get
us
to
template
branch,
separate
character,
Etc
the
short
allow,
a
gift,
though
that
was
diff
better.
A
Because
the
thing
is,
if
we
had
Automation
and
we
had
a
diff,
that
would
actually
be
pretty
good
too
okay,
so
those
are
the
three.
A
Hey
that's
like
a
triage
step
where
all
the
rest
of
it
gets
figured
out,
I
kind
of
said,
less
of
a
problem
with
serbius
thing,
because
it's
like
so
self-contained.
C
Yeah
the
question
for
my
PR
is:
who
gonna
approve
it
right
now?
John
belarmarek
has
permissions
to
all
these
folders,
so
they
can
approve
it
and
he
promised
at
some
point
to
do
that,
but
then
like,
if
you
do
similar
changes
in
future.
A
A
But
we
means
more
in
the
prr
side
and
I
think
that
I
would
say
just
off
the
cuff
like
this
is
totally
off
the
cost
at
any
changes
to
the
template
should
be
like
brought
to
you
enhancements
of
project
meeting
and
the
enhancement
Channel,
just
so
that
there's
that
second
or
third
set
of
eyes
who
can
think
through
the
timing
and
all
of
the
other
kind
of
issues
that
we
talked
about
today,
because
I
think
that
that
was
part
of
the
problem
that
got
that
Mark
ran
into
was
that
something
was
approved
that
you
know
probably
needed
a
little
bit
more
thought
like
in
in
the
way
of
General
enhancement
like
the
template
thoughts.
A
Yeah,
like
should
we
should
we
roll
this
out
now,
as
opposed
to
post
like
but
I'm
going
to
template
changes,
but
I
think
that
if
we
can
solve
the
third
bucket
of
sort
of
like,
when
is
a
version
Cut,
you
know,
and
how
do
we
store
those
changes?
I
think
that
it'll
be
a
little
bit
easier
to
figure
out
like
who's
approving
it
and
whether
or
not
all
of
the
eyeballs
are
actually
on
it
right,
because
if
we
have
like
a
I,
don't
know
I'm
just
making
it
up.
A
If
we
just
have
like
a
staging
branch,
and
all
those
changes
are
going
into
the
staging
branch
and
then
at
some
point
we
feel
like
well,
there
haven't
been
changes
to
the
template
in
a
while,
but
you
know,
maybe
this
is
a
good
time
to
for
the
next
release
roll
out
these
changes.
That's
something
that
we
can
have
like
a
lot
of
internal
communication
with
enhancements
prr
everybody
else.
A
Let
the
release
team
know
make
sure
everything
makes
sense
and
then
merge
that
approve
it
approve
it
merge
it
and
then
communicate
it
along
with
all
the
like
automation,
checks.
So.
B
B
A
A
But
but
I
think
that,
like
there's,
some
of
the
technical,
automated
steps
that
can
happen,
I
think
that
all
of
this
can
kind
of
be
done
in
tandem
as
well,
so
but
I
think
for
a
first
step,
I'm
just
going
to
figure
out
the
best
way
to
just
like
not
make
any
more
changes
to
the
active
template,
because
I
think
that
we
have
to
figure
out
some
of
the
other
questions
before
we
make
any
further
changes.
A
Because
I
think
that
might
be
a
little
trickier
than
like
a
yaml
I
mean
we
can
update
the
kept.yaml,
and
that
could
be
like
a
pretty
like
once
we
decide
when
what
a
version
is.
That
could
be
a
pretty
clear
thing
of
like
well,
you
need
a
cup.yaml
to
have
the
newest
version,
and
that's
going
to
be
like
a
signal,
might
not
be
the
most
polished
signal
to
the
author
with
a
diff
and
all
of
that.
But
that's
going
to
be
a
signal
that
you're
not
using
the
right.
A
A
Cards
especially
exploring
what
is
possible
for
markdown
parsing,
because.
C
A
That's
kind
of
gonna
be
a
little
bit
limiting
for
what
we
can
do,
but
we
can
do
the
animal.
So,
okay
does
that
sound
okay,
I'm
kind
of
babbling
and
I
I'm
a.
C
A
Yeah
see
I
thought
that
was
an
interesting
sub
issue
like
when
we
say
like
what
changes
do
we
allow
to
the
template
like
do
we
like?
Do
you
want
to
withhold
clarifying
instructions
right
like
because
there's
a
difference
between
setting
new
requirements
or
changing
requirements
versus
clarifying
instructions,
or
you
know,
fixing
a
markdown
error
or
you
know
whatever?
That
is.
A
Anything
yeah
so,
but
let's
make
sure
that,
for
let's
make
sure
that
for
that
change
we
kind
of
roll
it
out
together
and
we
don't
merge
it
without
just
making
sure
of
what
it
is.
B
A
Mean
I'm
more
open
to
merging
like
instruction
clarifications
than
any
sort
of
new
requirement,
because
I
think
it's
a
new
requirement
that
really
gets
people
confused
and
I
think
the
instructions
are
also
something
that
could
insist
like
assist
the
enhancements
team
in
rolling
out
the
enhancements
for
the
release.
Okay,
so
I'm
just
gonna.
B
A
B
C
B
Html
meta
tag
that
you
can
put
in
markdown
files
that
doesn't
it
causes
it
to
most
most
like
rendering
engines
will
not
render
that,
including
like
the
GitHub
UI,
but
it
you
can
still
use
HTML,
like
document
parsers,
to
pull
that
out.
So
that
might
be
a
good
way
to
if
we
wanted
to
stick
a
version
tag
or
like
a
version
right
actual
markdown
is
to
use
the
The
Meta
like
HTML,
okay,.
A
So
yes,
I
will
do
that
over
the
long
weekend
and
we'll
see
and
I
think
that
some
of
these
things
should
probably
get
started
and
then
some
things
are.
We
can
immediately
kind
of
just
talk.
C
B
A
To
the
enhancements
meeting,
because
I
think
that's
where,
like
the
conversation
would
happen
where
me
or
somebody
else
might
be
like
hey,
this
might
not
be
a
great
idea
to
roll
out
right
now.
A
So
that's
kind
of
like
a
Lo-Fi
solution
to
the
to
the
issue
as
well.
So
okay,
cool
I
actually
have
to
go
to
another
meeting.
I'm
probably
gonna
answer
me,
but
is
that
okay
I'm
gonna
I'll
I'll?
Let
you
guys
know
when
I
get
the
board
and
everything
else
going,
and
then
we
can
just
feel
free
to
make
new
cards
or
clarify
cards
or
write
thoughts
on
them
or
something
maybe
write
them
up
in
different
ways,
but
yeah.
This
has
been
really
great.