►
From YouTube: Backdrop Weekly April 26th
Description
Today’s development agenda: https://bit.ly/2vwJosM
A
All
right
we're
on
air.
It
is
Thursday
April,
26th
one
day,
post
med
security
update.
Thank
you
all
for
being
here.
Let's
see,
we
have
one
new
member
of
the
backdrop
contribute
this
week.
Best
of
imported
CSS
injector
got
approved
earlier
this
week
and
there's
already
a
release
out.
So
thanks
so
much
for
joining
contributor
ports.
Since
last
week's
meeting,
we
had
another
new
release
of
module,
which
is
maintenance
page.
A
So
if
anyone
was
a
nurse
in
that
module
from
4-7,
we
now
have
a
version
for
backdrop,
which
is
great,
there's
a
bunch
of
other
stuff
that
are
getting
updates
too,
but
I
didn't
bother
to
add
them
to
the
agenda.
Okay,
so
for
our
web
properties
backdrop
CMS,
org,
hopefully
we'll
be
getting
an
update
to
the
display
of
modules,
themes
and
layouts
pages,
as
well
as
some
minor
changes
to
functionality
like,
for
example,
search
results
need
to
do
a
better
job
of
returning
the
results
you
want
when
you
search
for
them.
A
We
have
a
bunch
of
issues
in
the
backed
up
CMS
that
work
around
being
able
to
find
modules,
themes
and
layouts
on
our
website
and
hopefully
does
look
at
some
attention
as
soon
as
the
110
releases
out,
maybe
even
port
during
code
freeze,
the
forum
site
is
waiting
for
search
box.
I
thought
about
playing
with
it,
while
I
was
doing
the
security
updates
yesterday,
since
I
was
on
there
anyway,
but
I
thought
better
of
it
since
I
had
a
lot
of
other
things
update,
but
it
will
come
soon.
A
B
All
right,
thank
you.
I
haven't
gotten
all
the
things
updated.
Yet
I
was
afraid.
That
would
happen,
but
lots
of
lots
of
things
are
happening.
It's
been
a
really
crazy
week,
I'm
sure
I'm
in
the
land
of
Drupal,
because
it's
aaand
a
backdrop
because
of
corresponding
updates
and
also
this
is
our
last
week
before
feature
freeze
for
one
point:
ten,
which
is
May
first,
which
is
this
coming
Tuesday,
so
less
than
a
week
left
to
get
done.
Many
of
the
things
that
we
would
like
to
do
and
we've
got
large
ambitions
for
those
things.
B
That
kind
of
mess
has
always
happens,
we're
coming
up
on
like
the
the
slam
where
it's
like
everybody
is
like
trying
to
get
in
there
their
future
before
the
next
release,
which
you
know
getting
in
or
not.
It's
really
awesome
to
see
this
level
of
activity
in
the
backdrop
as
YouTube.
So
let's
go
through
the
items
that
we
have
on
the
agenda,
although
sad
to
say
I
doubt
will
be
comprehensive,
just
because
there's
so
many
things
that
have
been
happening.
B
That
was
a
security
update
for
variations
on
the
Drupal,
get
into
attacks
that
are
out
there
and
we
are
fairly
certain
in
the
backdrop
community
that
those
exploits
are
actively
hitting
sites
out
there,
including
backdrop
websites.
So
it's
imperative
that
you
get
updated
to
the
latest
version
of
backdrop,
1.9
point
five
or
if
you
would
like,
we
also
did
a
1.8
dot
for
release
if
you're
still
in
1.8
other,
really
with
upgrades
between
minor
versions
being
really
pretty
seamless.
In
in
backdrop
really
just
updating
to
the
latest
version
is
highly
highly
encouraged.
B
One
point
nine
point:
six
will
be
the
next
bug
fix
release
and
we've
got
a
good
20
or
so
issues
that
are
all
tagged
for
one
point,
nine
point,
six
and
being
tagged
in
the
next
bug.
Fix
release
really
just
means
that
they
are
kind
of
higher
importance,
bugs
that
need
be
corrected
as
soon
as
possible.
The
one
that
will
call
out
during
these
meetings
is
the
same.
One
we've
been
doing,
which
is
2904
all
1.9
release.
B
B
So
I
feel
like
there's,
probably
other
196
issues
that
I'd
like
to
bring
up
because
there
are
a
bunch
of
them
but
I'm
not
going
to,
because
we
have
a
lot
of
other
things
to
cover.
So
please
take
a
look
at
the
one
point.
9.6
milestone,
there's
a
bunch
of
really
great
issues
in
there.
Several
almost
all
of
them
have
pull
requests
of
some
kind
and
maybe
a
quarter
of
them
or
any
needs
review
state.
B
1.10
one
point:
ten
is
our
next
minor
version
like
I,
said
future
phrases,
May
first,
followed
by
release
on
May
15th
things
that
we
are
improving
for
this
release
include
another
round
of
user
experience,
improvements,
first,
impression,
improvements,
translation
improvements
and
improvements
to
installing
modules,
themes
and
layouts.
So
first
impression
improvements.
It's
funny,
because
I
feel,
like
we
added
all
of
these
just
like
two
weeks
ago
to
the
agenda,
and
all
of
these
are
now
merged.
So
that's
really
exciting.
B
The
first
one
is
issued
30
32,
which
is
set
the
time
zone
based
on
browser,
JavaScript
API,
so
browsers
now
have
a
just
timezone
information,
which
is
a
relatively
new
feature,
and
that
makes
it
so
that
if
you
live
in
a
non
popular
timezone,
I
guess
like
a--.
If
you
live
on
the
example
I
keep
using
is
Arizona
because
Arizona
previously,
if
you
lived
there,
we
used
to
only
use
offset
from
GMT
and
so
half
the
year.
B
You
would
be
put
into
the
Los
Angeles
Times
own
and
the
other
half
of
the
year
you'd
be
put
into
the
Denver
timezone,
neither
of
which
is
accurate
for
somebody
that
lives
in
Arizona
which
doesn't
observe
daylight
savings
so
now
using
the
new
JavaScript.
If
you
live
in
Arizona
or
any
time
zone,
that
is
not
like
the
quote
primary
time
zone
or
the
first
time
zone
in
in
the
list
that
matches
that
offset.
B
Select
a
time
zone
instead
of
using
the
site
default.
It
now
correctly
sets
the
time
zone
per
user
as
well.
My
hope
had
actually
been
to
remove
the
time
zone
from
the
Installer,
but
you
can
read
the
discussion
there
in
issue,
30
32,
where
I
conceded
you
know,
maybe
just
fixing
the
time
zone
is
good
for
you
and
maybe
later
we'll
remove
the
time
zone,
but
for
now
there's
no
issue
tracking
that
so
also
in
the
Installer
password
field
updates.
B
Whenever
you
encounter
a
password
field
instead
allow
the
password
to
be
entered
only
once
and
then
have
a
visibility,
toggle
field
that
lets.
You
see
the
password
that
you
typed
in,
and
that
makes
it
so
that
you
can
still
get
the
error
correction,
that
you
would
get
from
having
a
confirmation
by
having
the
user
visually
confirmed
that
what
they
typed
is,
what
they
wanted,
but
save
them
the
trouble
of
needing
to
actually
go
to
the
process
of
typing
them
in
twice
that
issue.
B
It's
issued,
20
or
so
to
97,
and
that
has
been
merged
follow
up
on.
That
is
that
we
need
to
update
the
form
API
Docs,
because
now
password
fields
have
new
properties
and
conveniently
we
separated
out
password
confirm
from
password
strength.
So
now
you
can
have
password
strength
on
any
password
field
and
password
toggle,
as
it's
called
on
any
password
field,
and
you
don't
need
you
is
the
password
confirm
element.
Password
confirm
element
is
still
in
court,
but
it's
no
longer
used
anywhere,
except
for
in
our
tests.
B
B
Let's
see
during
the
installer,
we
had
this
problem
that
was
raised
by
one
second,
while
I
load
the
issue
that
was
Rick
raised
by
a
Drupal
East
Oh
Drupal
East
Oh
made
the
suggestion
that
when
he
was
trying
to
install
backdrop
using
localhost
as
the
database
connection
string
doesn't
work
for
him,
but
127.0.0.1
did,
and
the
history
of
this
issue
is
really
pretty
interesting.
You
can
read
it
in
issue:
25
20
thats,
a
lot
of
times
using
the
localhost,
doesn't
work
and
more
frequently
127.0.0.1.
B
Does
work
but
sometimes
it's
reversed.
Sometimes
the
IP
address
works
and
sometimes
localhost
doesn't
oh
wait.
The
other
way
around,
sometimes
the
IP
address,
doesn't
work
and
the
localhost
does,
and
so
the
suggestion
that
we
had
there
is
merely
to
try
both
if
you're,
using
localhost
or
the
IP
address,
try
the
one
that
is
entered
by
the
user
first
and
then,
if
that
one
doesn't
work,
then
flip
and
try
the
other
one,
and
since
that
host
option
is
hidden
by
default,
it
makes
which
I
think
it's
a
good
assumption.
B
B
B
B
Okay,
just
general
positivity,
okay,
I'm
excited
too
okay.
Let's
talk
about
translation
improvements.
I
haven't
taken
a
look
at
this
one
yet
so
issue
225
making
many
items
translatable
has
been
just
chilling,
I
got
it.
We
have
a
plan,
we
have
a
pull
request
that
is
so
close,
but
it's
just
not
complete.
It
just
needs
some
terminology
rerolls,
and
we
just
haven't
gotten
around
to
updating
that
so
issue.
225
still
once
again,
like
I
think
we
can
make
that
in
for
one
point
10,
it
just
needs
a
little
bit
of
a
little
bit
of
work.
B
Let's
see
issue
29:56,
which
is
blocked
translation.
It's
also
in
a
really
really
good
state.
We
went
through
a
couple
of
rounds
of
code
review
a
couple
weeks
ago,
bjorn
st
has
gone
through
and
addressed
all
feedback
and
updated
his
PO
request
and
functionality-wise
that
one
has
been
marked
our
TBC
a
couple
of
times,
because
the
functionality
is
there
and
it
works
and
it's
well
implemented.
B
However,
it's
missing
tests
and
we're
stuck
on
that
point.
Our
contributor
there
is
not
written
tests
before
and
so
that's
an
area
where,
like
we
could
use
some
assistance.
Just
stopping
on
some
tests
for
that
pull
request,
and
then
we
can
get
that
merged
in
once
again
really
optimistic
about
that
possibility
that
it's
pretty
much
ready
functionality
wise
just
what
we
have
to
get
test
coverage
for
such
an
expansion
of
functionality.
B
Also
in
translation
improvements-
one,
that's
not
going
to
make
it
for
one
point:
ten.
It
looks
like
at
this
point
I'm
just
going
to
say
it's
not
going
to
make
it
for
one
point
and
that's
config
translation
issue:
704
is
the
expansion
of
how
locale
module
works
to
make
it
so
that
it
handles
translating
config
files
consistently?
We
already
translate
things
that
are
stored
in
config,
like
the
content,
type
title
and
content
type
descriptions
and
any
administrative
labels.
B
All
of
those
things
are
run
through
locale
macho
right
now,
but
the
strings
are
not
managed
in
a
way
that
they're
discoverable,
and
that
makes
it
so
that
the
Pio
TX
module
can't
extract
those
strings
and
then
have
them
translated
like
in
the
out
of
box
experience
for
poor
backdrop
and
if
you
were
using
a
downloaded
translation
of
backdrop,
because
the
strings
are
impossible
to
find
right
now.
So.
B
That
one,
we
there's
still
really
great
discussion
and
we
still
have
a
really
great
plan,
but
the
implementation
is
not
there
and
so
that
one's
definitely
going
to
be
punted
to
1.11.
At
this
point,
okay,
that's
it
for
translation
of
improvements.
You
guys
have
any
feedback
or
commentary
on
additional
translation
functionality.
A
Sorry
this
is
Jen
I
just
wanted
to
say
really
quickly
that
usually
we
would,
if
something
had
slipped
more
than
one
milestone.
We
were
to
remove
the
milestone
entirely,
but
because
I
think
in
fake
translation
is
important,
I
just
pushed
it
to
1:11
I
hope.
Everybody
agrees
with
that,
but
I'd
love
to
see
that
make
some
progress.
What's
up.
C
And
I
just
had
a
curiosity
question.
This
is
Lehren
these.
The
translation.
Implementations
are
different
than
what's
done
in
Drupal
7
right,
so
I'm
just
curious
when
the
time
comes
to
create
a
multilingual,
Drupal
7
site.
Will
it
fit
into
this
scenario
or
what
is
that
something
that
will
be
more
of
a
manual
thing?
No.
B
It
actually
it's
it's
highly
compatible
with
Drupal
7
and
the
issue
there.
The
reason
that
we're
taking
the
approach
that
we
are
is
entirely
because
it's
compatible
like
if
we
compare
our
implementation
to
Drupal
8
Drupal
8
made
a
third
segment
of
translations.
There's
content,
translation,
localization,
locale
module,
which
is
user
interface
strings,
and
then
they
added
a
third
category
for
config,
translation
and
config
translation.
Drupal
8
is
a
is
a
third
type
of
translation
is
entirely
different
from
anything
that
was
available
in
Drupal
7
a
backdrop.
B
Config
translation
will
be
an
extension
of
locale
translation
or
user
interface
translation
that
we
will
continue
to
do
exactly
what
we're
doing
today.
We're
config,
essentially
like
certain
config
strings,
like
the
label
for
a
content
type,
will
continue
to
be
run
through
T,
just
like
it
is
today
and
just
like
it
wasn't
Drupal
7,
but
we're
adding
a
mechanism
to
make
it
so
that
translatable
strings
within
config
files
are
discoverable
by
the
translation
extractor.
B
B
B
The
first
one
that
we
have
here
is
the
UX
improvement
issue,
2973,
that
the
instant
filter
on
the
modules
page
should
include
the
category
names
as
well
as
the
module
name
and
description,
and
that
issue
2973
has
been
merged
and
special
thanks
to
Opie
for
doing
not
only
multiple
reviews
on
that
pull
request,
but
then
afterwards
filing
another
poll
request,
because
we
didn't
get
it
quite
right
to
his
satisfaction.
So
he
filed
another
pull
request
to
fix
things
that
we
also
emerged
in.
So
thank
you
all
be
our
star
review
or
I.
B
Let's
see
showing
screenshots
for
themes
when
you're
using
the
Installer
module.
It
would
be
really
great
if
you
can
see
what
a
theme
was
going
to
look
like
before
you
installed
it
and
since
themes
already
have
screenshots
both
on
backdrop
CMS
org
and
after
you
have
installed
it
issue.
30
40
has
made
it
so
that
we
start
showing
that
screenshot
in
the
listings,
when
you're
installing
your
themes
through
the
Installer
module.
That
issue
has
been
urged,
which
is
very
exciting,
Thank
You
Jen
for
putting
that
together.
I
think
it.
B
Actually,
it
shocked
me
that
all
of
the
infrastructure
was
already
there
for
that,
and
we
just
had
to
output
it
one
of
those
things
that
was
really
great,
that
when
you
look
at
how
difficult
a
problem
was-
and
it
turned
out
not
to
be
difficult
at
all.
In
fact,
all
infrastructure
was
already
there
and
we
just
needed
to
actually
theme
it
essentially.
B
1517
looks
like
Jen
just
bumped
it
before
this
meeting
during
this
meeting
to
1.11
and
that's
expanding
the
functionality
of
screenshots,
so
that
themes
can
have
multiple
screenshots
and
things
like
modules
and
layouts
can
have
a
screen
shot
to
begin
with,
because
right
now
only
layouts
yeah
can
I
just
range
shots
and
that
there
would
be
multiple
of
them
yep.
So.
A
That's
good
in
working
on
that
theme,
screenshot
issue,
I
also
added
the
infrastructure
to
backdrop
CMS
to
work
to
support
a
single
screenshot
for
layouts
and
modules,
so
as
layouts
and
modules
get
updated
in
half
new
releases,
if
they
have
screenshots
we'll
be
able
to
pull
them
into
backdrop
CMS
to
org.
So
that
means
in
the
future.
A
B
Of
a
harder
conversation
yeah
and
it's
worth
noting
that
the
way
you
add
screenshots
to
themes
and
the
way
that
these
giant
screenshots,
two
layouts
and
modules,
is
through
the
module
code
itself.
So
if
you
upload
a
screenshot
to
your
theme,
that
is
the
screenshot
that
or
show
up
on
backup,
CMS,
don't
work
and
it's
the
screenshot
that
will
show
up
in
the
Installer.
Oh.
A
A
We
need
to
talk
about
like
if
we
want
to
start
allowing
multiple
screenshots
at
larger
sizes.
Maybe
we
should
have
the
packager,
then
remove
those
screenshots
from
the
module
that
gets
installed
in
someone's
site
so
that
we're
not
bogging
down
the
file
size
of
backdrop
with
massive
the
images
rather
than
the
code.
That's
actually
needed
to
run
the
modules
in
the
layouts
yeah
yeah.
B
B
B
Okay,
other
features
for
1.10
I
feel
like
there's
another
one
in
here
that
needs
to
be
mentioned.
I
can't
remember
what
it
is.
First
of
all,
let's
talk
about
issue
3001,
which
is
automatic
comment,
closing
which
I
think
Abdul
has
been
leading
the
charge
on
is
that
I'm
gonna
pull
it
up?
Yes,
herb
duel
has
been
leading
the
charge
and
he's
been
doing
an
awesome
job
like
if
this
thing
is
really
really
fantastic.
There's
lots
of
reviewing
that's
happening
right
now.
B
We're
we're
tied
down
in
semantics
or
tied
down
in
naming
things
on
this
issue,
I
think
but
functionality-wise
we've
had
lots
of
reviewing
and
everybody
is
very
excited
about
the
functionality.
It
looks
really
fantastic
and
this
adds
the
ability
to
per
content
type
and
on
a
per
node
basis.
You
can
say
close
this
close
comments
on
this
post
after
like
30
days
or
something
like
that,
and
it
makes
it
so
that
it
will
close
that
you
know.
B
As
that
deadline
gets
past,
then
comments
will
automatically
be
shut
off
by
crunch
on
something
it's
very
cool
about
this.
Also
that
I'm
excited
about
will
need
some
follow-up
issues.
Is
that
that's
a
new
column
to
the
node
table,
so
in
addition
to
created
and
updated
when
the
nose
created
and
when
the
nose
is
updated,
it
has
a
column
for
published
and
what
the
name
of
that
column
is.
B
Talking
about
the
next
issue-
Oh-
am
I
oh
yeah.
I
am
that's
the
one
that
was
exciting.
Sorry,
okay,
take
all
of
that
back
comment.
Closure
is
in
really
great
shape,
even
has
tests,
and
it's
not
held
up
by
semantics.
So,
let's
get
that
one
in
three
thousand
one
is
super
close.
Let's
just
knock
it
out
and
make
it
happen.
B
B
You
know
I
had
the
idea
of
like
touched
the
created
date
to
update
it
to
be
the
time
that
it
was
published,
which
is
all
a
little
bit.
I
mean
it's.
It's
wonky
logic,
trying
to
figure
that
out
like
like,
because
then
the
last
published
or
last
edited
time
is
actually
before
the
last
created
or
the
creative
time.
It's
a
big
mess.
What
this
means,
though,
is
that,
as
follow-up
wishes
to
this,
we'll
need
to
make
it
so
that
the
published
column
gets
full
views.
B
Support
and
starts
being
used
is
like
this
submitted
by
day,
because
what
you
should
see
like
you
know
when
something
you
know
Wednesday
like
Alliance,
was
submitted
by
username
at
date,
I
still
I
think
shows
created
date
and
not
for
this.
It
should
start
showing
published
date.
Jen.
Can
you
correct
me
on
that?
Does
it
does
that
be
enough?
David,
that's.
A
F
F
B
So
there's
concern
around
the
word
published,
even
though
it's
would
match
you
know,
created
updated
published
because
published
makes
it
sound
like
it's
a
boolean
flag
like
0
1,
instead
of
being
a
timestamp,
so
I
don't
know.
Let's
continue
discussing
that
one
in
the
issue.
It
doesn't
seem
like
a
huge
hang
up.
Well.
A
Yeah
I
mean
I
think
the
issue
is
for
like
people
who
aren't
already
familiar
with
the
system,
don't
know,
there's
a
status
and
I
like
how
do
I
find
out.
If
this
note
is
published
or
not,
they
look
the
note
and
they're
like
oh
there's
a
note
published
value
and
then
they'll
grab
it
and
they'll
be
like.
Is
it
true
and
if
it's
a
date
it'll
be
yes.
A
A
There's
something
we
could
do
like
with
anode
property
like
we
could
add
a
node
scheduled
if
it's
not
published
and
then
use
node
publish
to
zero,
but
in
the
database
the
column
the
publish
column
will
always
contain
the
date.
Even
if
it's
in
the
future
and
the
notes
not
published
so
I
mean
that
we
can,
we
can
maybe
clean
it
up.
But
would
you
wait.
D
E
B
I
think,
the
time
being,
what
this
will
mean
is
scheduled,
unpublishing
will
get
kicked
to
contribute
or
for
for
backdrop,
and
that
probably
means
that
module
need
to
I
would
probably
say
that
module
be
deprecated
and
then
I
knew
like
scheduled
on
publish,
unpublished.
Scheduler
would
be
like
a
smaller
scope
module
because
it'll
be
a
lot.
Some
point
out.
B
A
B
So
things
like
that,
we
actually
encourage
you,
know
iterative
development
as
much
as
possible,
but
inner
development
and
maintaining
the
backwards
compatibility.
Sometimes
those
two
things
should
be
difficult
to
do
at
the
same
time,
so
we
like
to
make
sure
that
we
don't
break
the
backwards
compatibility
going
forward.
But
iterating
is
it's
great,
so
I
think
we're
nearing
that
point,
that
you
know
we'll
reach
a
decision
and
then
we
can
build
off
of
that
foundation.
B
Okay
last
one
for
user
feature
improvements.
This
one
actually
intended
to
be
in
the
future
parity
with
WordPress
section
yeah.
They
can
do
this
in
WordPress,
okay,
it's
the
ability
to
upload
files
into
the
rich
text
editor
the
same
way
that
you
can
upload
images
into
the
rich
text
editor
in
a
similar
fashion.
B
So
when
you
use
the
image
button,
you
can
upload
images
and
conceptually
want
to
make
it
so
that
if
you
use
the
link
button,
you
can
upload
a
file
and
have
the
the
newly
created
link
link
to
the
file
that
you've
just
uploaded
so
kind
of
an
extension
of
the
way
images
are
managed
make
it
handle
other
remaining
types
of
files.
In
a
similar
fashion,
this
one
currently
needs
some
feedback,
but
I
think
actually
gram
72
has
been
leading
the
charge
on
this.
One
has
also
been
requesting
javascript
help
on
that.
One
he's.
A
Got
the
JavaScript
working
he
wanted
to
code
review,
which
I
thought
maybe
Opie
could
help
with,
but
there's
also
a
couple
of
other
issues.
One
of
them
as
like
is
the
user
interface
intuitive
enough.
So
if
we
could
just
get
people
to
like
give
it
a
test
and
see
if
it
makes
sense,
that
would
be
good
and
then
the
other
one
is
around
permissions
right
now
we
have
a
separate
permission
for
allowing
people
to
upload
images
in
the
rich
rich
text.
E
B
B
Stuff,
like
that,
it's
it's
on
the
text.
Format
configuration
so
when
you,
when
you
enable
the
image
button.
It
also
shows
you
options
for
restricting
the
types
of
images
that
can
be
uploaded
and
where
they
should
be
uploaded
into,
and
things
like
that.
So
permission
wise.
Is
it's
actually
a
lot
like
controlled
in
some
ways
by
having
access
to
a
particular
text
format,
but
then,
on
top
of
that,
then
there's
another
permission
for
uploading
so
that
you
could
have
access
to
the
image
dialog
to
insert
images,
but
you
might
not
have
access
to
upload.
It's.
A
B
B
Anyway,
that
one
it
needs
work,
Kim
said
like
functionality
wise.
This
is
another
one
where
it's
like
we're
like
we're
in
alignment
now,
I
think
the
functionality
is
great.
The
implementation
is,
is
pretty
solid
and
we're
just
like
just
getting
through
those
last
hangups.
So
thanks
again
to
Graham
72
for
all
of
your
effort
on
that
especially
I
know,
it's
been
a
little
bit
of
a
long
slog
even
reaching
consensus
that
we
should
even
add
that
feature
so
I'm
glad
to
I
appreciate
your
persistence
in
talking
everybody
through
that
and
bringing
everybody
around.
B
B
You
know
things
are
still
on
the
table
as
long
as
they
can
get
into
an
our
TVs
see
States
this
week,
I'm
doing
my
best
to
keep
on
top
of
those
and
Jeff
has
been
merging
a
lot
of
things
as
well.
So
again,
like
cross
reviewing,
is
one
of
the
most
important
things
we
can
do
right
now
to
accelerate
things
to
make
it
so
that
we
can
get
them
the
most
functionality
and
make
it
so
that
1.10
is
totally
awesome.
So
that's
it.
B
C
It
on
there
but
I,
don't
really
have
anything
to
really
add,
except
just
just
to
ask
where
that's
at,
because
I
know
there
was
some
flurry
of
discussion
and
then
it
kind
of
went
away,
and
after
the
last
you
know
month
and
a
half.
Obviously
it
was
probably
the
number
of
people
interested
I
think
it
would
be.
I
didn't
put
it
on
there,
just
because
I
would
really
like
it,
but
I
think
that
it
would
be
a
great
marketing
tool
for
backdrop,
and
it
would
draw
a
lot
of
people,
especially
the
small.
A
Feel
like
I
would
really
like
it,
but
I
think
it's
a
great
tool
that
would
directly
benefit
our
target
audience
like
our
audience
are
people
who
are
not
going
to
be
necessarily
staying
on
top
of
every
update
of
the
software
going
forward
and
having
something
that
can
help
protect
them.
We
think
it's
good.
We
just
need
to
figure
out
a
way
that
we
can
do
that.
That
puts
them
at
the
least
amount
of
risk
of
everything
breaking
with
automatic
updates.
A
Maybe
we
should
have
a
process
that
would
like.
If
we
had
automatic
updater,
we
might
be
able
to
say,
like
the
automatic
updater
won't
update
you
in
the
next
major
version.
If
we
have
security
or
you
maybe
there's
option
that
would
let
you
say
like
I'll
only
off
to
be
into
security
updates
and
then
it
would
keep
you
on
whatever
version
you're
on
or
maybe
like
a
manual
button.
That
would
say,
like
ok,
now,
I'm
ready
to
update
to
the
next
version.
You
can
push
it.
A
You
can
test
things,
but
yeah
I
think
it
is
a
conversation.
We
should
have
to
figure
out
what
kind
of
experience
we
want
our
users
to
have
in
backdrop
to
for
managing
updates
going
forward.
There's
also
a
technical
conversation
for
how
we're
going
to
do
it,
but
just
in
terms
of
what
we
wanted
to
do,
I
think
is
a
good
first
step
to.
B
Muted
notes,
but
so
Mike
Banton
has
done
a
lot
of
thinking
around
this
I
think
you
see
that
we
have
the
link
to
his
thoughts
in
that
issue.
He
also
has
worked
on
on
a
standalone
PHP
project
that
conceptually
it's
supposed
to
make
it
so
that
it
could
be
like
a
CMS
updater
like
third-party
project,
where
it
would
be
responsible
for
doing
the
updates,
trying
to
figure
out
what
the
name
of
that
is,
but
I
keep
forgetting
it.
It's
not
in
his
little
document.
Do
you
know
what
it
is?
B
Maybe
that
would
be
good
I
think
he
mentioned
that,
like
his
project
is
something
like
with
all
of
its
dependencies,
because
it's
composed
a
driven
project
is
his
project
to
something
like
twice
the
size
of
backdrop
itself
like
as
far
as
code
weight
is
concerned,
he's
like
I'm,
not
sure
how
you'd
feel
about,
like
you
know,
tripling
the
size
of
backdrop
to
add,
auto-updating
ability
and
I'm
like
I'm,
not
sure
either.
You
know
it
would
really
depend
on
it.
E
B
Like
for
us
to
pursue
another
parallel
track
to
that
at
least
that
is
probably
like
you
know,
let's
look
at
what
WordPress
does
because
I'm
sure
it's
much
simpler,
it's
probably
a
little
bit
of
a
higher
risk,
depending
where
it's
problem
play.
You
know
like
oh
just
unzip
the
files
and
then
replace
them
like
that's
what
I
imagine
WordPress
does
because
WordPress
is
always
like
Occam's
razor,
like
every
single
problem
for
better
or
worse
and
so
I
feel
like.
There
are
simpler
solutions
out
there,
but
they'll
come
at
the
cost
of
you
know,
potentially
catastrophic.
B
But
and
but
still
like
the
world
that
we're
living
in
right
now
like
it
would
have
been
really
nice
had
we
had
automatic
updates
because
risking
catastrophic
failure
was
worth
it
because,
right
now,
if
your
sites
are
not
updated,
you're
suffering
from
catastrophic
failure
anyway,
and
so
the
the
inaction
is
just
as
catastrophic,
maybe
even
more
so
than
having
catastrophic
action.
That
was
that
was
caused
by
an
automatic
update.
So
look.
E
A
A
green
I
think
there's
a
way
that
we
can
do
that
by
supporting
more
minor
versions
and
issuing
releases
for
each
of
them
with
what's
just
the
bug,
fix
really
or
to
the
security
fix
release,
and
then
the
automatic
updater
could
pull
the
patch
from
our
history
and
apply
that
to
existing
sites.
So
that
way,
if
you
were
developer-
and
you
were
running
back
drop
one
five
for
some
reason
and
you
couldn't
update
to
one
six-
you
can
still
get
updates
through
the
normal
process.
A
The
updater
would
pull
just
the
patch
version
for
its
automatic
process
and
everyone
will
kind
of
get
the
kind
of
protection
they
need
that
way.
We
would
just
need
to
figure
out
like
because
we
are
looking
at
moving
on
to
you
know,
factor
up
110.
How
hard
is
it
to
take
fixes
for
one
nine
and
create
patch
versions
all
the
way
back
to
one
zero
like?
Should
we
have
some
cutoff
point
where
it's
like?
B
E
A
I
think
like
adopting
a
policy
of
supporting
more
than
one
minor
release,
I,
don't
think
we
should
keep
supporting
every
minor
release,
but
I
think
like
if
we
could
say
you
know,
for
the
last
few
releases,
we've
supported
two
versions
of
backdraft.
If
we
were
to
say
from
now
on
we're
always
going
to
support
two
and
then
starting
in
backdrop,
two
we're
always
gonna
support.
A
E
B
E
It
doesn't
happen
continue
to
happen
right
so,
and
you
know
I
think
I
think
the
automatic
updater
if
we
actually
just
started
it
off
on
the
security
update
thing
like
you
know,
maybe
that
might
be
interesting
instead
of
figuring
out,
like
the
general-purpose
update
the
whole
system
for
every
updater.
If
we
just
started
off
as
a
security
update
system
that
might
be
interesting,
yeah.
A
E
A
A
B
Or
doesn't
wait
or
replace
files?
You
know
other
I
don't
know.
Patching
patching
is
difficult
because
not
patches
not
installed
on
all
systems
like
the
command-line
patch
is
not
installed
on
all
systems
and
there's
no
way
that
we
would
want
to
attempt
to
patch
with
PHP
implementation
of
you
know,
then
you
just
have
a
whole
new
set
of
problems.
B
B
B
B
I'll
jump
into
the
issue
and
say:
what
are
we
doing?
We're
experimenting?
That's
what
we're
doing
so,
any
any
opportunity
approach
like
if
you
think
that
maybe
it's
viable
then
then
try
it
out.
You
know
see
how
things
go
and
I
really
do
think.
We
could
learn
something
by
taking
a
look
at
WordPress,
this
auto
updater
and
the
the
various
fails
that
have
happened
around
it.
You
know
for
better
and
worse.
D
B
D
D
B
D
E
B
B
But
but
they're
still,
I
mean
like
that
kind
of
that
gets
into
server
like
maintenance
territory,
which
is
not
the
same
as
a
developer.
Territory
like
a
lot
of
devs
might
not
know
how
to
configure
Apache,
probably
don't
wanna
configure
Apache
if
I
played
you
know
PHP
inside
and
out.
So
let's
see
where
the
value
is.
A
Can
we
have
a
backdrop
like
we
could
even
have?
Theoretically
there
could
be
a
setting
that
would
use
your
update
status
to
say
Oh?
Is
there
a
security
update
for
core?
If
yes
write
this
value
into
settings,
type
PHP,
which
sucks
the
site
down
like
you,
could
even
have
like
super
extreme
measures
for
the
site
could
turn
itself
off
if
it
felt
like
it
was
in
danger.
How.
B
Okay:
let's
talk
about
that,
I
I!
Think
it's!
If
you
know
it's
a
discussion
that
we
should
have
a
LOF.
If
you
made
an
issue
for
that
yeah,
okay,
yeah
yeah,
go
ahead,
go
ahead
and
do
so
and
then
and
then
we
can
brainstorm
in
there
because
it
sounds
like
we've
got.
Lots
of.
You
know
variations
as
to
how
impressive
we
could
be
with
that.
I
have
a
couple
other
ideas
as
well.
That
I
can
tell
us
all
right
down
there
kind
of
middle
ground,
but
let's,
let's
take
into
the
issue
queue.
B
B
A
I
don't
know
if
we
need
to
come
up
with
a
policy
today,
but
I
think
it
would
be
good
like
just
because
the
last
few
releases
we've
done
if
we
weren't
able
to
tell
people
and
the
so
releases
ago.
We
did
three
I,
checked
usage
statistics
this
week
and
most
of
the
people
who
were
on
one
seven
before
the
last
release
are
no
longer
around
one.
Seven
we're
down
to
like
ten
sites
or
something
I
should
check
that
again.
Today
it
doesn't
ever
change
daily,
but
I.
A
It
seemed
like
it
was
safe
to
only
do
eight
and
nine,
but
I
don't
know.
If
we,
if
we
had
a
policy,
it
was
like
we're
always
gonna,
do
three
seven,
eight
nine.
We
would
have
more
people
feeling
confident
about
remaining
on
older
versions.
I,
don't
know
if
that's
a
good
thing
or
a
bad
thing.
Confidence
is
good.
All
the
region's,
not
good
so
I,
don't
know
if
we
need
a
policy
where,
like
even
like
today,
we
could
say
well
always
do
two
and
then
now
from
now
on,
every
security
release
comes
down.
A
B
Don't
know,
let's,
let's
table
it,
for
this
meeting
I
think
we're
we're
well
over
our
mark
here
for
our
weekly
meeting.
Although
it's
been
an
exciting
weekend,
this
is
the
last
meeting
before
feature
freeze,
so
I'm
really
happy
to
see
everybody
who
came
in
during
this
meeting
and
thank
you
all
for
the
great
discussions,
let's
wrap
it
up,
though.
So,
where
should
I
open
an
issue
about.