►
From YouTube: Backdrop Weekly Mar 15
Description
Today’s development agenda: http://bit.ly/2FpAjGH
A
All
right
we
are
on
the
air,
it
is
Thursday
March,
15th,
thanks
everybody
for
joining
and
watching
this
meeting.
This
one
is
a
check-in
on
active
development
tasks
for
doctor
of
CMS.
Before
we
get
into
active
tests,
I
did
want
notes.
We've
got
a
couple
of
new
projects
in
King
trip.
This
week,
comment
closer,
which
is
a
part
of
a
Drupal
7
module
that
happens
to
be
a
core
feature
in
WordPress.
It
allows
you
to
specify
a
period
of
time
for
every
post.
That
comments
should
be
open
versus
when
the
comments
will
close
automatically.
A
So
it's
a
great
today
I'm
prevention
tool
and
it's
something
that
we
should
maybe
consider
for
core
and
backtrack,
but
now
that
we
have
in
contribute
something
that
people
can
use
and
we
can
count
the
statistics
on
usage
there.
One
thing
to
note
for
something
like
that,
though,
is
that
I've
never
used
the
comment
closer
module,
but
if
that
feature
was
in
the
core,
I
would
probably
is
at
all
time.
So
there
are
things
like
that.
Maybe
our
statistics
on
usage
might
not
be
an
accurate
measurement
of
how
valuable
that
feature
would
be
to
people.
A
So
just
need
to
use
a
little
common
sense.
There
other
new
modules
we
have
our
references
dialog
in
node
reference,
URL
widget.
So
these
are
both
modules
that
extend
reference
modules.
You
have
some
work
going
on
around
reference.
The
contribute
role
as
well
so
they'll
probably
be
great
examples
for
making
sure
that
the
API
is
that
we
include
in
the
reference
module.
That's
slated
for
core
can
do
the
same
things
that
the
AAP
is
that
are
currently
in.
These
modules
can
do
to
make
sure
that
these
controls
will
continue.
A
Working
even
requires
a
little
adjustments
there
to
to
make
sure
that
they
can
work
with
a
new
field.
Oh
great
I
mean
it's
pointed
out
that
there's
an
issue
for
a
comment
closer
in
core
its
issue,
3001.
So,
if
anyone's
interested
in
having
that,
please
weigh
in
there
I
think
that
would
be
valuable
to
have
feedback.
A
Okay
website
related
issues.
This
is
perfective,
see
mister
org,
we're
currently
working
on
improving
the
modules,
themes
and
layout
pages.
There's
an
issue
for
that
and
the
vector
of
CMS
or
Q.
It's
number
four
42
and
if
you're
interested
in
seeing
the
designs
that
we
implement
for
those
pages,
we
did
do
a
screen
share
of
those
during
today's
design
meeting.
A
B
Yeah,
okay,
so,
let's
see
first
of
all,
it's
March
15th,
March
15th,
a
notable
date
because
it
is
exactly
two
months
from
May
15th,
which
is
the
release
of
backdrop
1.10
according
to
our
scheduled
release
policy.
So
that
means
we
have
exactly
two
months
for
one
point:
ten
or
actually
one
and
a
half
months
before
feature
freeze
for
one
point:
ten,
which
always
happens
at
the
first
of
the
month.
B
So
yeah
we're
continuing
to
rock
along
here
items
for
backdrop:
1.9.3,
that's
the
next
bug
fix
release
is:
let's
see
we
got
one
large
issue
that,
if
fixed,
we
would
make
a
the
1.9.3
1.9.3
release
and
that
is
issued
2904,
which
is
a
regression
problem
with
database
credentials
that
at
one
point,
special
characters
could
not
be
used
in
database
credentials,
at
least
when
done
via
the
installer.
So
a
URL
encoded
those
special
characters
but
then
broke
the
percent
symbol
as
kind
of
a
side
effect,
because
the
presence
of
was
used
in
URL
encoding.
B
Reporting
on
that
particular
issue
before
it
is
committed,
also
issue
29
71,
which
looks
like
it's
a
problem
regarding
upgrade
path
that
new
lines
in
emails
when
upgraded
I
think
this
happens
from
all
triple7
sites.
The
emails
actually
have
literally
a
backslash
in
printed
out
in
the
emails
rather
than
a
new
line
character.
B
Let's
see
it
looks
like
there's
a
number
of
issues
here
that
a
couple
of
them
are
going
needs
review
state,
but
most
of
these
items
in
the
1.9.3
label
or
release
have
been
reviewed
and
they're
all
Indian
needs
work.
State
like
it
looks
like
about
I'd,
say
about
like
26
of
like
30
issues
or
O&I
needs
work
state.
So
there's
a
good
number
of
issues
there
feel
looking
to
make
some.
You
know,
probably
relatively
quick
adjustments
to
backup
to
make
minor
improvements.
B
B
Ok,
1.10
1.10
will
be
coming
out.
May
fifteenth,
two
thousand
eighteen.
We've
got
a
pretty
heavy
focus
on
translation
improvements
for
this
particular
release.
Issued
225
is
an
issue
to
make
menu
items
translatable.
The
status
of
that
one
is
that
it's
been
viewed.
It
actually
was
hard
to
BC
even
at
one
point,
but
there's
some
terminology
changes
there.
B
Config
translation
is
issue,
704
I'm,
not
sure
if
it's
time
II
and
to
start
making
call
us
about
what
gets
in
and
what
does
it.
But
this
one
needs
some
love.
We
have
a
proof
of
concept,
pull
request,
but
we
need
to
go
beyond
that
and
actually
get
it
to
actual
implementation
and
get
it
to
a
point
that
it
is
actually
usable
for
you
know
being
a
starting
point
to
get
into
court.
B
B
B
B
B
A
B
B
A
Going
on
in
the
existing
for
requests
and
I
think
trying
to
keep
them
both
like
on
top
of
what
the
other
ones
doing
might
be,
might
slow
them
both
down
so
I'm
gonna
take
a
step
it
get
in
the
first
one
cleaned
up
and
then
seeing
what
it
would
take
to
just
add
that
so
the
first
pull
request
we
have
one
for
the
modules
grouping
actually
removes
all
the
way
packaging.
So
I
need
to
put
that
back
in
and
then
once
it's
back
in
it
should
be
fairly
straightforward
to
just
fix
the
search.
A
B
So
that
issue
is
issue
1517
and
that's
just
adding
the
basic
capabilities
and
then
later
we
would
expand
that
out
to
actually
leverage
leverage
the
sprint
shots
in
various
places.
Yeah
also
see
the
github
issue
tracker
for
1.10
issues,
there's
a
number
of
other
items
that
are
kind
of
on
the
wish
list
for
1.10,
but
we
will
not
go
over
all
of
them
here,
so
that's
it
for
the
1.10
status.
Update.