►
From YouTube: 12 6 Kickoff Distribution
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
A
Ok,
so
this
is
the
epics
roadmap
view
of
some
of
the
high-level
things
that
we're
going
to
be
working
on
over
the
next
couple
of
months.
I'm
going
to
start
on
this
top
one
here,
which
is
the
EBI
images
that
we've
been
working
on.
Over
the
last
couple
of
months,
we've
been
working
on
building
Red
Hat
based
EBI
based
images.
Most
recently
in
the
12.5
milestone.
A
Next
up
is
geo.
Sport
for
home
I'm
really
excited
to
announce
this
one.
This
is
one
of
the
limitations
that
we've
had
in
the
home
chart
for
a
while.
We
have
been
working
in
the
12.5
milestone
to
add
support
for
geo
into
the
home
charts.
We
have
the
Geo
secondary
to
a
point
where
you
can
configure
it
through
the
home
charts,
we're
working
on
the
primary
and
also
documenting
how
to
get
this
all
set
up.
A
A
Also
on
Homme
charts
we've
been
investigating
what
it's
going
to
take
to
upgrade
from
home
to
to
home,
3
and
helm.
3
did
become
generally
available
within
the
last
week.
I
think
it
was
so
now
that
it's
generally
available,
we
can
wrap
up
some
of
that
research
and
create
some
issues
for
the
work
that
needs
to
be
done
on
our
side
to
actually
support
home,
3
and
finally,
for
the
home
tatts.
A
So
Pima
is
something
that
we've
been
working
on
for
a
while
in
get
lab,
calm
and
in
omnibus
and
it
we
have
found
that
it
provides
better
performance
as
a
web
server
than
unicorn
and
in
omnibus
and
calm.
Both
the
Pima
and
the
unicorn
options
exist,
but
they
do
not.
Pima
is
not
available
in
home
charts.
So
to
close,
this
gap
in
the
difference
between
omnibus
and
home
charts
will
be
working
on
adding
optional
support
for
Puma
in
12.6.
A
So
what
we
want
to
do-
and
this
is
kind
of
a
long-term
thing
that
we
plan
to
work
on-
is
an
infrastructure
as
code
initiative,
where
we
are
creating
scripts
to
automate
a
lot
of
that
configuration
and
then
making
that
automation
available
in
the
product
for
you
to
use
I'd
really
like
to
get
feedback
on
this
one.
So
if
this
is
something
that's
relevant
to
you,
please
jump
into
this
epic
and
provide
something
back.
A
The
first
step
that
we're
going
to
take
in
12.6
is
to
configure
Geo
so
to
deploy
and
configure
geo
notes
on
Google
cloud
platform,
and
mostly
the
audience
for
this
is
going
to
be
our
internal
geo
team
so
that
they
can
automate
the
environment
that
they
need
to
test
new
features
and
test
upgrades
Regios
involved,
and
then
we
want
to
roll
this
out
so
that
it's
publicly
available.
We
would
like
to
be
in
a
position
where
we
are
supporting
the
second
and
third
most
recent
versions
of
PostgreSQL.
A
A
There
are
a
lot
of
great
features
in
post
eleven
that
we
want
to
benefit
from
such
as
partitioning,
and
so
the
plan
is
documented
here
it
to
give
you
an
overview.
It
involves
adding
support
for
PostgreSQL
11
as
soon
as
we
can
continuing
to
support
nine
point.
Six
and
ten
until
we
get
to
get
lab
thirteen
point
O
at
which
point
we'll
remove
both
of
those
and
then
so
PostgreSQL
eleven
becomes
the
minimum
requirement.
Forget
lab
thirteen
point
O
and
then
aim
to
add
twelve
in
get
Loeb
thirteen
point
three
as
an
opt-in.