►
From YouTube: Backdrop Weekly - Sept 13th
Description
Today’s development agenda: http://bit.ly/2Cs5D6D
A
A
We
have
a
open
ticket
number
for
42
for
the
backdrop
CMAs
at
work
website
that
is
about
improving
modulus
thinking
layouts.
That
issue
hasn't
had
any
momentum
in
a
while
it
needs
some
attention.
So
if
anybody
has
any
timeline
just
working
on
effective
team
support
as
they
would
love
to
focus
effort,
so
I'm
not
gonna,
say
much
more
about
that,
because
we
plugin
last
meeting,
but
it
is
an
ongoing
and
shooting
live
up
to
itself.
I,
don't
know
if
there's
any
updates
on
translation
study,
I
haven't
talked
to
a
lot
recently.
B
A
C
C
We
still
have
not
released
one
that
end
up
to
you.
We've
got
a
huge
bucket
of
fixes
that
are
now
in
that
bug.
Fix
release
for
1.10
city
looks
like
well
pretty
huge,
there's
third
30
issues
that
have
been
merged
into
one
at
10:00
and
then
there's
a
good
looks
like
27
additional
issues
that
we
could
potentially
get
into
that
minor
version.
But
almost
everything
is
is
currently
has
a
pull
request,
but
does
not,
but
all
of
them
need
work
at
this
point
so
so
1
to
10.
C
Love
our
immediate
bug
fixes
that
we're
trying
to
attempt
that's
where
they're
all
stored,
so
there's
29
issues
in
that
particular
queue.
But
if
you
look
in
the
1.11
queue
which
is
all
just
basically
features
or
folks
related
to
the
new
features,
there's
only
three
or
four
issues
and
the
1.11
queue
which
is
which
is
awesome,
you
know
that's
that's
where
we
want
to
be
so.
C
It's
all
just
kind
of
you
know
little
punks
and
things
that
that
need
to
be
resolved
in
the
current
bug-fix
release,
so
we're
in
a
great
position
as
far
as
cutting
that
last
bug-fix
release
we're
also
in
a
great
position
for
1.11.
Like
it
just
said,
there's
only
four
issues
in
the
1.11
issue
tractor
right
now,
we'll
make
a
one
dot
11.1
milestone
pretty
shortly
here,
because
anything
that
doesn't
get
into
one
but
ten
will
end
up
getting
bumped
into
one
don
eleven.
C
But
for
now
there
isn't
a
bug-fix
milestone
on
that.
The
two
issues
that
I'd
like
to
call
out
that
would
be
nice
to
get
resolved,
have
to
do
with
the
colorizing
of
the
basis
theme
there's
issued
3209
in
which
we're
trying
to
add
predefined
color
schemes
for
bases
just
giving
some
out-of-the-box
color
options
for
basis
and
then
an
issue.
That's
related
to
that
one
is
3286,
which
is
adding
the
ability
to
make
it
so
that
the
primary
tabs
in
basis
have
a
separate
color,
picker
I,
think
that's
what
that
one
is
and
I
imagine.
C
These
two
issues
are
related
that
potentially
we
had
someone
that
was
trying
to
make
color
schemes
for
basis
and
then
realized
that
they
were
having
a
hard
time
making
ones
that
looked
good
because
of
this
lack
of
a
discreet
color
for
the
primary
tabs,
and
so
we
ended
up
with
that
issue
being
created,
probably
in
response
to
an
attempt
to
make
color
schemes.
So
both
of
those
issues
are
related
to
color
module
and
basis
is
colorization
in
particular,
and
those
are
the
two
issues
that
we'd
like
to
probably
see
resolved
before
one
to
eleven.
A
C
That's
actually
it
kind
of
for
1.11
we're
in
the
like
nice
actually
kind
of
chill
zone
like
the
calm
before
this
door,
because
everything
pretty
well
put
away
for
the
next
release.
It's
now
just
kind
of
letting
the
clock
tick
by
and
tell
what
would
be
Saturday
is
when
we'll
be
doing
the
release,
dude
or
a
calendar
based
release
cycle
and
on
Saturday
the
15th.
That's
when
we'll
be
cutting
these
two
releases
so
Jeff
are
you
gonna
be
around
on
Saturday
anybody,
Jen
I,
think
so,
okay,
excellent!
Thank
you.
A
C
Well,
we
normally
start
in
what
would
be
the
west
coast
morning
like
around
10:00
or
11:00
a.m.
and
then
we
like
to
be
done,
but
for
4:00
p.m.
Pacific
I.
Think
generally,
that's
the
way
it
goes.
We've
had
some
that
have
happened
within
an
hour,
actually
we've
kind
of
gotten
it
into
thanks
to
our
process
checklist.
Where
we
go
through
each
individual
item,
it's
actually
turned
into
a
pretty
smooth
running
machine.
So
what
we'll
do
at
the
very
beginning
of
the
days
will
open
up.
C
A
So
I'm
gonna
post
a
link
in
together
for
where
our
procedure
documents
or
start
there
in
the
issues
copepods
Traci,
we
have
the
specter
of
issues
repository
that
has
code
associated
with
it
wasn't
actually
I
mean
code,
so
reason
not
for
documentation
for
the
issue
queue.
So
we
have
one
here
for
a
fix
release
and
we
have
another
one
or
a
minor
leagues,
and
there
are
handful
things
on
here
where
I
have
names
assigned
to
various
people.
Like
writing
a
blog
post
to
highlight
all
the
fantastic
changes
that
went
into
what
our
latest
version
is.
A
Anyone
can
write
the
blog
post.
Ideally
it
will
be
done
before
Saturday
so
that
we
could
have
like
a
draft
up
and
all
we
have
to
do
when
we
release
and
publish
it.
So
that's
definitely
something
that
you
know.
We
don't
really
need
anyone
with
any
like
merging
ability
to
do
that.
You
just
have
to
kind
of
go
to
the
sandbox
for
the
call
requests
and
take
a
screenshot
as
a
new
feature
and
then
write
a
paragraph.
That's
like
we've
added
this
new
thing
and
then
a
paste
in
the
screenshot
and
it's
pretty
straightforward.
A
Yeah
tweeting
updating
the
front
page
on
vectrex,
a
messed
up,
org,
there's
a
handful
of
things,
they're
just
kind
of
busy
tasks
that
we
would
love
to
get
more
bored.
So
if
you
want
to
do
any
of
those
things,
just
I
would
say.
Let
me
know
and
I'll
add
your
name
to
the
list
of
people
who
would
like
to
have
these
tasks
assigned
to
them
and
then
that
way
for
every
release.
If
you're
available
and
like
Gregory
isn't,
we
can
use
you
instead
of
members
and
so
I'll.
A
D
C
Awesome:
okay!
Well,
that's
that's
the
big
thing
you
know.
Of
course,
we've
got
these
new
releases
coming
out
day
after
tomorrow
and
that
that's
the
key
item
on
our
agenda.
We've
started
bucketing
things
for
1.12,
which
will
be
the
next
money
release
and
that
will
come
out
next
year,
woo
January,
15th,
2019
and
items
that
we've
got
for
1.12
right
now,
mostly
just
consist
of
things
that
got
bumped
from
one,
not
11.
We
want
to
continue
working
on
core
automatic
updates.
C
The
meta
issue
is
2018,
a
recap
of
that
kind
of
reminders
that
we
did
make
it
so
that
you
can
update
core
via
the
user
interface
in
1.11,
but
that
functionality
is
disabled
out
of
the
box
and
you
have
to
go
in
and
turn
it
on
manually
by
editing
a
config
file
right
now,
hopefully,
for
1.12,
we'll
be
able
to
expose
that
option
directly
in
the
user
interface
to
make
that
available
for
everybody.
We
also
have
some
other
issues
related
to
core
updates
that
I
won't
won't
recap.
C
Now:
let's
see
tanks
for
modules,
issue
number
37
got
bumped.
It
has
a
pull
request,
though
it
currently
needs
review.
We
had
a
real,
strong
sprint
right
at
the
end
of
1.12.
Oh
sorry,
1.11,
you
know
the
current
release
cycle
for
putting
options
element
in
core
issue
1005,
and
this
one
looks
really
strong.
C
So
that's
been
an
issue
that
has
stuck
around
for
a
while,
and
everybody
seems
to
agree
that
it
would
be
a
great
improvement,
but
we
haven't
actually
revisited
it
anytime
recently,
so
it
currently
needs
work,
but
it's
in
really
great
shape
and
also
an
area
that
received
a
lot
of
attention.
This
release
cycle
was
feel
double
file,
types
or
file,
bundles
issue,
26
32,
and
that's
a
huge
lots
of
functionality
that
takes
a
lot
of
of
the
file
entity,
module
and
media
module.
It
puts
it
into.
C
Court
currently
needs
work,
but
not
from
a
technical
standpoint,
mostly
just
a
user
experience.
Standpoint
like
the
port
from
Drupal
7.
Although
almost
perfect
in
its
conversion
over
to
backdrop,
at
least
as
far
as
my
technical
review
is
gone,
looks
great,
there's
just
some
inherent
inherited
issues
that
we
got
as
far
as
the
UX
is
concerned.
C
Moving
that
functionality
in
the
core,
so
I
think
that
we
need
to
find
some
ways
to
better
integrate
it
into
court
or
at
least
provide
description
text
on
how
certain
things
are
used
and
how
they
different
from
options
in
backdrop,
court
currently
make
it
a
little
less
bolted
on
and
more
integrated.
Basically,
so
those
are
four
issues
that
we
have
that
have
been
bumped
from
1.11
and
yeah.
We're
we're
in
a
great
place
for
those
we'll
see
after
the
release.
C
One
of
their
items
were
targeting
for
1.12
we're
actually
open
to
suggestions
at
this
point
in
time.
It's
not
uncommon
for
us
to
take
requests
basically
for
things
things
that
could
potentially
receive
attention.
It's
also
a
good
time
to
go
back
and
look
at
the
items
that
we've
attempted
in
previous
releases
that
didn't.
A
C
Let's
see
we
do
have
a
roadmap
on
backdrop,
CMS
org
backdrop
seeing
that
storage
such
roadmap-
that
we'll
probably
need
to
get
updated
kind
of
as
soon
as
possible,
because
that
is
actually
also
one
of
the
tasks
in
the
in
the
checklist,
I
believe,
is
to
update
the
roadmap
and
right
now
for
1.11,
like
we
don't
have
anything
huh-oh,
our
roadmap
wasn't
even
updated
for
the
current
release.
That's
not
good!
C
So
anyway,
we
need
to
add
some
things
that
Lewis
says
what
we
did
in
one
double
oven
and
kind
of
where
we're
headed
towards
one
by
twelve,
because
from
the
looks
of
things
right
now,
I
mean
when
we
started
this
project.
We
had
so
many
things
that
needed
to
be
done.
It
was
obvious
where
we're
headed
and
now
that
we've
done
all
of
the
the
things
that
we
sent
it
to
do
in
the
early
releases.
C
C
B
D
C
Okay,
let's
see
next
up,
we've
got
some
general
discussion
in
Q&A.
Looks
like
one
item
that
has
come
up
is
issue
number
62,
which
isn't
an
old
issue.
That
may
be
time
to
be
revisited
and
that's
dropping
support
for
some
old
versions
of
PHP.
Right
now
backdrop
still
supports
PHP
5.3,
which
is
let's
say,
I-
think
that
there,
oh
I,
it's
not
actually
listed
in
this
particular
issue,
but
I
think
that
there
5.3
in
theory
is
actually
still
supported
by
sent.
Os
I
think
is
the
last
holdout
until
2020.
C
A
A
So
that
means
that
people
who
don't
know
any
better
using
something
like
blue
tomorrow
swimming
so
I'll
back
to
out
to
again
initial
failure
because
the
PHP
version
it
gets
you
it's
not
the
right
one
and
you
can
like
dig
around
in
there
and
find
the
PHP
version
settings
and
change
it.
I.
Just
think
that
that's
until
HP
5/3
goes
away,
it
might
be
good
to
not
have
support
for
maybe.
B
C
That
that's
really
the
key
thing
is,
you
know
it
knew
if
it
seemed
impossible.
These
five
three
on
a
new
site
like
it's
getting
the
point
that
it's
getting
hard
honestly
like
it's
difficult
to
even
maintain
a
server
that
has
PHP
5
3,
because
the
operating
system
is
moving
forward
like
it's
not
even
possible
and
a
lot
of
them
to
install
such
an
old
version
of
PHP
like
the
package
managers,
basically
will
just
refuse
to
do
it
because
of
the
dependencies
the
dependency
chain
on
it.
C
C
C
Change
the
requirement
speak
the
yeah
it's
more
than
the
requirements
page.
We
actually
have
a
kill,
switch
in
the
very
top
of
bootstrap.
That
says.
If
your
version
of
PHP
is
not
new
enough,
then
it
totally
white
screens
on
you
and
just
as
your
version
is
too
old
and
right
now.
That
version
is
PHP
5.3
point
2,
if
you're
lower
than
that
backdrop
just
refuses
to
function
essentially.
C
E
That
we
didn't
know
we
should
upgrade,
but
at
larger
institutions
and
I'm
guessing
the
hosting
providers
are
the
same
way.
There
ends
up
being
a
lot
of
moving
parts.
It's
not
just
the
CMS
that
impacts
the
version
of
Red,
Hat
or
cen
OS
that
you're
running
and
so
having
Bing
is
big
and
trying
to
be
as
forward-looking
as
possible.
The
fact
that
we
only
got
off
of
it
nine
months
ago
might
give
you
some
indication
of
how
prevalent
it
still
is
so
yeah,
I,
I,
don't
know
deprecating.
E
C
Yeah
well
yeah.
Let's
continue
discussing.
Oh
you
know
what
else
is
a
good.
A
good
benchmark
is
WordPress
support
for
old
versions
of
PHP,
so
WordPress
has
job
support.
Then
you
know
it's
one
of
the
most
backwards
compatibility
oriented
projects
out
there
and
once
they
jump
support
it's
like
well,
that's
the
tipping
point
for
a
lot
of
shared
hosts.
Basically,
as
far
as
like
the
chicken
and
the
egg,
like
just
saw
updated,
the
server's
get
updated.
I
think
that
WordPress
has
actually
aren't
done
that
that
no
more
it
was
a
bad
version.
2.4.
A
C
Yeah
I
know
there
was
some
how
about
about
dropping
some
old
PHP
versions,
but
it
might
be
in
the
next
version
of
WordPress,
the
one
that
is,
you
know
a
long
time
coming,
but
in
which
they
do
that.
That
shift.
That's
probably
when
I
would
guess.
Oh
yeah,
that's
funny.
Yeah
they're
there
requirements
page
doesn't
actually
show
you
the
requirements.
It's
actually
just
like
recommendations.
D
C
A
A
What
that
is,
and
then
Jeff
I
added
you
as
being
responsible
for
one
and
two,
but
I
wasn't
sure
which
things
me
did
and
which
things
you
do
so
I'm
going
to
get
to
a
beach
at
about
like
changing
the
version
number
so
that
you're
not
both
changing
the
renumbered
and
your
different,
releasing
at
the
same
time,
but
in
general
I
took
a
seven
for
class
assignments,
but
you
know
that's
wrong.
Yeah.
C
C
A
C
Okay.
Well,
we've
only
got
two
days
left,
there's
not
not
a
whole
lot
to
tackle,
but
you
know
it's
always
good
to
you
know,
work
through
a
backlog
of
bugs
that
we've
gods
that,
like
I,
said
the
one
but
10.2
milestone,
is
the
key
place
to
look
also.
The
1.11
queue,
which
only
has
this
for
issues
and
particularly,
is
to
related
to
color
module,
would
be
great
to
get
those.
D
C
E
C
You
know
it
would
be
good
for
us
I
think
we
should.
We
should
document
that,
probably
in
the
pantheon
upstream
itself,
like
at
least
in
the
github
repository,
it
describes
the
fact
that
we
have
that
delay
in
there,
because
yeah
I,
don't
I,
don't
think
it
is
widely
documented.
It
is
just
the
way
that
we've
done
every
release
thus
far,
though,
that
the
minor
releases
haven't
have
a
delay
on
them,
but
fix
releases
come
up
immediately.
It's
only
the
miners
that
we
we
leave
a
little
grace
period
on
okay,.
C
Okay,
all
right!
Well,
thanks
everybody
yeah
a
great
release
cycle.
It
might
be
too
early
to
celebrate
entirely
next
week.
Well,
you
know
we'll
do
the
high
fives
so
okay!
Well
thanks
everybody
for
joining
again,
thanks
to
everybody
out
there
for
watching
and
we'll
catch,
you
guys
on
the
other
side
of
the
release.
So
hey
guys.