►
From YouTube: Platform Sync: 2020-09-12
Description
- kubecon booth
- Release Planning
- Move from ZenHub to Milestones
- pack subcommands config
A
A
A
Cool
all
right
seems
like
we
still
don't
have
all
the
signatures
on
the
document,
if
you
don't
mind
sending
the
document,
but
we
can
get
started
with
status
updates
I'll
kind
of
give
a
little
brief.
From
my
perspective
kind
of
ties
into
the
release
planning
right
now,
pack
we're
trying
to
release
going
to
feature
complete
for
oh
13-0.
I
believe-
and
a
lot
of
that
has
to
do
with
updating
the
platform,
api,
204
and
the
lifecycle.
A
B
Think
so,
although
there's
a
booth
builder
link
that
that
the
people
who
set
up
the
booth
can
log
into-
but
I
think
it's
like
through
the
normal
conference
stuff,
like
you-
go
to
the
conference
and
you
show
up
to
the
booth
as
a
conference
attendee,
but
that's
why
it's
why
they
wanted
the
email
to
be
the
same
as
the
registration,
so
that
when
you
go
as
a
as
a
normal
attendee,
you
look
like
a
moderator
or
something
like
that.
You
can
do
more
things,
I'm
pretty
sure
how
that
works.
B
They
didn't
for
folks
who
got
the
original
email.
I
don't
think
they
had
any
instructions
for
what
to
do
in
the
email
itself.
But
if
you
look
at
the
training
material
at
the
bottom,
I'm
guessing
the
training
material
tells
you
how
to
show
up.
Does
it.
I
can
reach
out
to
yeah
our
event
person
who
set
everything
up
if
you,
if
you
want
me
to-
and
we
were
talking
about
it
yesterday-
actually
I
asked
hey:
am
I
supposed
to
be
able
to?
B
A
B
C
A
D
I
can
go
next
for
me:
I've
been
more
or
less
heads
down
on
wrapping
up
some
last
minute
changes
to
the
github
actions.
That's
going
to
be
used
to
consume
new
github
issues
that
represent
registered,
build
pack
requests
to
add
new
bill
packs
to
the
registry.
It's
looking
pretty
good
and
it's
in
a
point.
A
D
C
I'm
checking
out
what
I
did
the
past
few
days
right
now.
I
just
finished
up
a
pr
on
working
on
the
platform
api
and
specifically
how
fixing
image
inspect
so
that
it
now
displays
the
correct
default
process
types
before
that,
otherwise,
during
this
week,
just
been
general
bugs
trying
to
make
sure
it
was
finish
things
up
for
the
new.
C
B
B
A
Cool
all
right
next
is
release
planning.
I
think
I
kind
of
delve
into
this
a
little
bit
we
are
going
through
with
feature
complete
and
hoping
that
the
lifecycle
produces
another
patch
release,
at
least
that's
the
game
plan
for
now
and
we'll
be
able
to
address
that
anything
else
for
release
planning.
A
A
A
You
know
important
issues,
whether
it
be
bugs
or
high-level
features
that
we
want
to
include
in
certain
releases
and
have
a
flexibility
of
providing
both
the
planning
aspect
of
it
and
also
you
know
kind
of
statements
of
what
we're
actually
going
to
release.
So
I
mean
in
a
general,
you
know
like
from
a
practical
standpoint.
I
think
the
idea
is
just
no
longer
using
senhub
and
using
milestones
as
a
way
to
depict
what
work
is
going
to
be
done
at
a
certain
point
in
time.
C
A
A
A
All
right
there's
nothing
else
there.
The
other
thing
I
have
is
pack
sub
commands.
So
this
is
a
very
what
was
hopefully
going
to
be
a
small
rfc.
It's
making
a
drastic
change.
Nonetheless,
so
we
want
to
make
sure
to
get
it
right,
and
I
think
joe
has
one
of
his
last
statements.
Where
he's
not
a
huge
fan
of
the
currently
proposed
config
sub
commands
and
the
each
the
discussion,
I
guess
comment
I
just
linked
to
is
one
of
the
finalized
proposals
or
the
latest
proposals
for
how
config
could
work.
A
A
C
Just
kind
of
getting
a
sense
of
milestones,
I
think
we
talked
about
this
individually
but
surface
over
here.
So
if
people
want
to
think
that
things
should
be
done,
they
should
just
let's
say
tag
it
with
iso.
At
this
point
you
know
zero
14,
milestone
and
just
so
to
keep
people
in
the
loop
on
what
they
think
should
be
done,
or
what
they're
currently
working
on.