►
From YouTube: Backdrop Weekly - Sept 20th
Description
Today’s development agenda: http://bit.ly/2p5DMzL
A
B
All
right:
well,
we
had
a
very
exciting
weekend.
Saturday
was
the
15th
of
September,
which
means
it
was
released
day
for
us
and
we
put
out
two
releases
of
backdrop.
We've
finished
up
the
one
10.2
release,
which
was
the
last
release
in
the
1.10
Minor
branch,
and
that
includes
everything
that
we
had
all
of
the
bug
fixes
that
we
had
in
that
branch
for
the
last
two
months.
B
Basically,
and
we
also
simultaneously
released
1.11,
which
was
the
new
minor
release
which
includes
a
boatload
of
new
functionality,
including
an
image
browser,
rabbit,
hole
like
functionality,
improved
color,
module,
contact,
module
improvements
and
a
lot
a
lot
of
other
really
awesome
features.
You
can
read
up
more
about
the
1.11
release
in
our
blog
post,
which
you
can
get
to
from
the
home
page
of
a
backdrop,
CMS
dot
org.
So
that's
very
exciting.
B
B
First
of
all,
the
really
awesome
news
is
that
it's
been
five
days
now:
we've
had
people
updating
their
sights,
but
the
backdrop
issue
queue
has
been
like
completely
silent
on
new
problems
with
1.11,
which
is
fantastic,
so
that
shows
that
we've
had
a
thus
far.
It
looks
as
though
we've
got
a
really
stable
release
in
1.11.
B
Usually
really,
we
release
a
bug-fix
released
two
weeks
after
the
initial
release
to
address
any
problems,
but
sometimes
there
aren't
any
so
we'll
see
how
that
happens.
I
know
I
think
it
was
last
release.
We
didn't
end
up
with
a
bug-fix
release
after
two
weeks,
because
we
we
didn't,
have
any
substantial
problems,
and
so
we
just
decided
after
two
weeks
to
like
push
the
Pantheon
up
streams
and
everything
like
that
after
two
weeks,
without
a
bug-fix
release
at
all.
B
B
Because
people
seem
to
find
that
accessible,
like
maybe
they're,
not
comfortable
with
github
or
not
have
a
github
account,
and
so
they
filed
a
problem
on
the
forum
and
then
there
were
some
responses
back
and
forth
on
that,
and
it
looked
like
for
the
first
reporter,
at
least
they
had
to
clear
their
caches
and
after
doing
cache,
clear
everything
was
fine.
So
that
actually
is
kind
of
great.
That
may
be
actually.
A
A
great
issue
from
that
anyway,
because
he
did
run
the
database
updates
and
that's
supposed
to
clear.
The
cache
and
I've
also
had
some
problems
with
calling
backup
cache
clear,
all
in
a
module
update
function
and
having
the
cache
not
be
cleared
so
I
think
there
might
be
some
like
race
condition
there,
where,
like
the
cache,
is
cleared
before
the
update
is
done.
Sort
of
so
that
might
be
worth
looking
into
trying
to
figure
out
without
it.
So
I'm
gonna
create
an
issue
about
that.
Okay,.
B
B
We
hope
we
usually
make
first
book
fix
released
after
two
weeks.
The
only
item
that
we've
got
known
that
we
want
to
tackle
as
soon
as
possible
is
that
we
have
all
this
new
ability
and
color
module
in
1.11,
including
basis
is
now
color
risible,
but
we
didn't
include
any
predefined
color
schemes
out
of
the
box
and
as
a
UX
enhancement,
we
would
like
to
improve
or
provide
some
color
schemes
out
of
the
box
and
ship
them
with
basis,
and
because
this
is
a
UX
thing,
we
allow
those
InFocus
releases.
B
B
Let's
see
yeah,
we
also
had
a
note
in
the
form
that
there
might
be
a
problem
with
the
color
preview
in
Safari.
That
is
yet
to
be
confirmed
and
will
file
a
ticket
for
that.
If,
if
it
turns
out
to
be
a
reproducible
problem,
let's
see
so
that's
it
for
1.11,
we'll
continue
making
bug-fix
releases,
of
course,
as
always
for
the
next
four
months.
But
let's
talk
about
one
dot
12,
which
will
be
the
next
release
coming
at
January
15th.
B
So
the
first
item
on
here
is:
we
have
this
meta
issue
for
automatic,
slash,
core
updates
in
issue
2018
and,
first
of
all,
let's
talk
about
what
happened
in
1.11
and
that
we
did
enable
the
ability
to
do
core
up
sorry,
we
included
code
that
allows
core
to
update
itself
through
the
user
interface
in
1.11.
However,
that
functionality
is
hidden
from
the
front-end
display
to
end-users,
unless
you
manually
edit
the
config
file
to
turn
it
on,
and
so
it's
not
really
a
publicly
advertised
feature.
B
It's
just
laying
some
groundwork
to
allow
for
us
to
provide
core
self
updates
in
1.12.
So
in
1.12
we
have
a
new
issue
that
we
created
3271
to
enable
the
user
interface
for
core
updates,
and
then
we
also
have
the
same
issues
from
before
that
we
didn't
get
done
in
one
da
levin,
which
includes
package
signing
issue
1992
and
then
the
actual
automatic
update
part,
which
is
let's
see
here.
B
414,
we
also
have
a
bit
of
an
issue
for
removing
or
deprecating
authorize
of
PHP,
which
is
not
widely
used,
not
compatible
with
installer
and
wouldn't
work
for
automatic
updates.
So
with
all
of
those
compounding
issues,
there's
the
general
consensus
that
removing
it
is
easier
than
maintaining
it,
essentially
and
also
more
in
line
with
the
direction
that
we're
heading.
So
that
issue
is
got
a
poor
request
that
I
started
to
deprecate,
but
not
actually
remove
all
of
that
functionality,
and
that
looks
like
that's
going
to
be
a
likely
thing
for
1.12.
B
So
that's
all
exciting
automatic
updates
kind
of
moving
along
I.
Don't
think
that
we've
had
anybody
yet
test
like
the
whole
complete
package
of
the
core
updates
via
the
user
interface.
Now
that
we
have
a
release
that
is
newer,
it's
much
easier
to
test,
but
I
guess
we
still
actually
have
a
caveat.
That
1.12
is
the
only
version
that
has
a
release
and
it
won't
be
until
one
dot.
B
12.1
comes
out
that
there's
a
newer
version
from
which
there's
a
previous
version
that
has
the
ability
to
update
court
so
I
guess
we
actually
may
need
to
wait.
Just
a
little
bit
longer
in
order
to
test
the
whole
the
whole
ecosystem
together,
but
at
least
the
functionality
is
then
there
for
the
next
release
when
it
when.
B
Let's
see
other
issues,
tags
for
modules
is
issued
number
37.
This
didn't
get
revisited
quite
in
time,
and
the
Objectivist
of
this
issue
is
just
to
make
it
so
the
tags
are
possible
to
add
to
modules
and
other
projects
so
that
we
can
better
categorize
them
both
on
the
modules
page
and
on
backup,
CMS
org.
B
Let's
see
this
came
up
at
the
very
tail
end
of
their
release.
Actually,
I
guess:
we've
seen
it
a
a
while
back,
but
now
the
pull
request
is
looking
really
good,
and
that
is
issue
1005,
which
adds
the
options
element
into
core.
It
also
adds
the
functionality
for
having
options,
element
work
on
work
on
all
of
the
fields
that
are
core
so
anytime.
You
create
a
select
list
and
core
and
adds
a
new
widget
for
inputting
the
select
list
options.
B
It
looks
really
pretty
awesome,
really,
there's
also
some
styling
updates
that
make
it
look
more
backdrop,
II
kind
of
modernizing
it
just
a
little
bit
and
having
it
line
up
with
the
the
new
set
in
theme
and
backdrop,
so
that
issue
is
well
worth
looking
at.
It
currently
needs
work,
there's
just
a
little
bit
more
integration
that
could
be
done
to
make
it
act
as
though
it's
a
part
of
core,
rather
than
something
tacked
on
top
of
core,
but
it
looks
really
good.
B
So
we
would
like
to
just
tie
you
things
up,
maybe
it's
as
simple
as
having
more
description
text
and
changing
some
terminology
in
places,
but
that
also
looks
like
it's
in
really
great
shape.
That
allows
us
to
have
different
file
types
like
video
versus
image,
for
example,
and
also
to
add
additional
fields
onto
those
different
types
of
files.
So
it's
very
nice
collection
of
functionality
still
needs
a
little
bit
of
work,
but
it
is
in
great
shape,
for
you
know
having
an
entire
release
to
get
it
completed.
B
We
don't
have
any
other
things
yet
prioritized
for
1.12
other
than
those
items
which
are
all
buffs,
basically
from
1
to
11,
although
if
you're
looking
to
push
for
a
particular
initiative
like
now,
it's
the
time
to
you
know
get
out
there
and
say:
hey
I've
got
this
great
idea
for
the
next
version
of
backdrop
and
we'll
look
at
it.
Give
it
some
consideration
to
give
it
priority
for
in
the
next
release.
B
A
I'll
ask
my
safari:
he
found
it
in
though
so
many
browsers
open
thanks
for
running
through
all
the
updates.
Nate,
that's
great!
Let's
see
it
so
next
up
we
have
rock
drop
for
good
I'm,
not
sure.
If
there's
any
particular
updates
for
that
here
in
the
document
it
says
you
can
check
out
the
issue
of
you.
If
you'd
like
to
participate
anything
else,
there
Jeff
yeah.
D
I'll
Aaron
did
a
bunch
of
stuff
and
he's
looking
for
ideas
about
how
to
Coralie
business
nodes
with
business,
savvy
CRM
entities,
but
there's
been
some
progress
and
that
the
one
I
just
mentioned
is
you
know,
a
fairly
difficult
problem,
but
it's
more
about
what
path
do
we
take?
So
if
anybody
has
any
ideas
there
and
Larry
threw
out
some
ideas
in
that
issue.
If
you
want
to
in
one
so
they
could
take
a
look
and
make
some
recommendations.
Okay,.
A
A
Okay?
Well,
we
just
had
a
meeting
in
the
last
hour
about
community
outreach
and
Tim
was
there
and
he
had
a
fantastic
recommendation.
I
want
to
drop
here,
which
is
that
for
the
next
backdrop,
release
which
is
January
15th,
he
recommended
that
we
try
and
coordinate
at
least
five
happy
birthday
backdrop
parties,
just
after
the
release
where
we
can
help
spread
awareness
about
backdrop,
have
a
little
kind
of
celebration.
It'll
be
back
from
fourth
birthday.
January
15th
is
also
Drupal's
birthday.
A
So,
if
you're
interested
in
doing
a
backdraft
drupal
thing
together,
that
could
be
an
option,
but
we've
got
only
really
fun
to
do
five
distinct
locations,
just
a
little
party
like
five
people,
or
something
where
we
can
celebrate
everything
we've
done
and
if
you
can
bring
new
people
and
show
them
what
backdrop
is
done?
That's
even
better,
so
I
just
want
to
drop
the
idea.
Here.
We
are
gonna
post,
something
in
the
forum.
We're
gonna,
try
and
put
events
up
on
the
events
page
for
backdrop
CMS.