►
From YouTube: Backdrop Weekly - April 18th
Description
Today’s development agenda: http://bit.ly/2XmmSMj
A
All
right
we
are
on
air,
it
is
Thursday
April
18th,
and
this
is
a
meeting
to
check
in
on
active
development
tests
for
backdrop
CMS.
For
starters,
we
have
an
updates
from
the
PMC
section
of
the
meeting,
but
this
is
again
an
update
for
the
PMC
there's
a
bunch
of
issues
there
that
need
votes
on
them.
One
of
them
in
particular,
is
something
I.
A
Just
I
want
to
put
an
update
on
the
roadmap
and
really
cycle
pages
about
Drupal,
7,
end
of
life
and
backdrop
1.0
end
of
life,
but
I
want
to
get
consensus
from
the
camp,
see
on
the
right
language
to
use
for
that.
So
I
put
a
recommendation
in
the
queue
for
that,
but
I
want
to
go
to
look
at
that
before
we
make
a
public
statement
to
make
sure
that
it's
correct
and
we
might
need
we
might
need
to
discuss
that,
so
that
one
is
urgent.
A
The
other
ones
are
not,
but
there
are
issues
so
I
will
also
send
an
email
to
PMC
today
to
try
and
get
people
who
aren't
watching.
This
meeting
aren't
on
it,
but
I
did
want
to
call
that
to
your
attention.
A
community
we
have
a
new
backdrop
kinship
member
fossa,
we
all
named
Attila.
We
want
to
say
thanks
reporting
the
mad.
Now,
fire
module
and
Gargano
you've
been
working
with
the
tow
a
lot
and
wanted
to
say
thank
you
for
responding
to
all
of
your
feedback
as
well.
Yeah.
B
He's
done
an
amazing
job
like
he
added
the
drop
downs,
he's
working
on
adding
asset
but
similar
to
the
admin
bar,
the
one
that
we
have
in
admin
bar
and
have
it
working
with
the
drop
downs
and
and
also
add
the
notification
path
when
we
have
errors.
So
it's
gonna
be
more
comparable
to
that
someone.
Some
issues.
Some
small
small
issues
have
come
up
and
this
might
be
correlated
as
well.
B
We
cannot
get
parity
with
whatever
functions
we
are
using
with
the
menu
that
gets
produced
by
admin
bar,
so
at
some
point,
I
thought
that
maybe
and
I'll
file
a
ticket
for
that.
Maybe
the
admin
bar
should
have
a
like
a
should
be
using
a
system
function
that
that
generates
the
menus,
so
that
other
menus
like
med,
sorry
other
modules,
never
I
can
use
the
same
thing
like
produced
the
same,
the
exact
same
meaning
because
we're
doing
some
funky
stuff
with
admin
bar
yeah
doesn't.
A
Just
take
a
system
menu
which
is
probably
what
you're
running
into
is
that
there's
like
a
hook,
admin
bar
link,
definition
and
so
any
module
that
wants
to
add
something
into
admin
bar
implements
it
directly
against
admin
bar.
So
you
can't
get
it
out
with
any
other
system,
but
there
probably
is
a
way
that
we
could
expose
the
completed
list
if
there
isn't
already
so
that
something
wants
to
grab
it.
I'm
sort
of
in
calling
like
the
menu.
B
A
Do
that
so
just
refresh
my
number
nav
bar
is
the
one
that
moves
the
top
menu
to
the
side
bar
instead
yeah.
B
Either
either
automatically
or
it
actually
likes
yeah,
it
actually
mimics
exactly
what
happens
in
d8.
Okay,
so
it's
that
plus
there's
a
additional
module
that
adds
the
drop-down
menus
they're,
considering
to
merge
it
in
the
d7
version
of
add
member.
But
we
have
done
it
that
already.
So
it's
like
more
like
comparing
it
to
d8
sites
that
my
agency
is
building
and
we
always
using
those
using
that
brings
all
that
experience
out
of
the
books
with
that
single
portable,
so
great
great
work
for
until
I,
like
thank.
A
Okay,
moving
on
backdrop,
semester,
org-
we
mentioned
this
in
the
outreach
meeting
to
now
has
a
new
box
on
the
homepage,
with
information
about
upgrading
from
Drupal
7,
just
some
kind
of
big
high-level
points
about
modules,
readiness
and
that
sort
of
thing
we're
gonna,
add
links
to
that,
but
other
than
that,
it's
sort
of
done.
So,
if
you
have
anything
back
on
that
opened
an
issue
and
the
back
tipsiness
at
work
queue,
we
had
a
couple
of
other
things.
We
talked
about
in
the
outreach
meeting
related
to
the
website.
C
All
right,
so
it's
been
two
weeks
since
we
last
had
a
meeting
triple
comments
last
week,
and
so
we
didn't
kind
of
meet
quorum
for
doing
a
meeting,
but
there
was
a
lot
of
stuff
that
happened
over
the
interim
two
weeks.
First
of
all,
yesterday
there
was
a
security
release,
Drupal
766
was
released
and
it
was
a
security
release,
primarily
accommodating
an
update
to
jQuery
jQuery
3.4
that
came
out
that
had
a
minor
security
fix
in
it.
So
this
resulted
in
Drupal
creating
new
releases
but
interesting.
C
Both
versions,
both
Drupal
8
and
Drupal
7,
are
not
running
a
new
enough
version
of
jQuery,
and
so
there
was
some
work
to
backport
the
security
fix,
while
keeping
the
same
version
of
jQuery
available
on
the
individual
sites.
So
back
to
our
part
of
the
same
fix,
there
was
has
a
little
bit
of
an
oopsie
with
ordinary.
It
was
a
little
bit
of
a
surprise,
but
but
we
managed
to
get
our
backdrop
version
within
an
hour
two
of
the
Drupal
7
version
being
released.
B
C
B
C
It
seems
like
it's
almost
both
the
efforts
of
a
single
person,
but
the
fact
that
it
was
called
that
in
the
release,
notes
as
being
a
suitable
alternative
makes
it
kind
of
official
yeah
when
I.
What
would
have
made
this
more
tenable
to
stay
on
one
dot.
X
for
longer
would
be
if
an
individual
or
organization,
again
kind
of
send
me
officially
started
making
new
jQuery
updates.
C
You
know,
even
if
they
had
to
add
another
semantic
versioning
number
like
if
it
were
one
dot,
12.6
dot
one
or
something
on
you're,
not
saying
that
they
started
applying
security
fixes.
On
top
of
it,
then
that
would
have
been
a
much
easier
way
for
us
to
solve
this
problem.
You
know
we
could
have
just
updated
to
a
new
semi
supported
version
of
jQuery,
rather
than
doing
what
we
did,
which
is
port
from
Drupal
7,
which
adds
a
second
JavaScript
file
that
fixes
the
one
function
that
exists
inside
of
jQuery,
but.
B
I
think
at
some
point
we'll
have
to
just
bite
the
bullet.
I'm
think
that
the
only
two
reasons
that
has
been
holding
us
back
is
ie8
support,
because
that
is
sort
of
like
a
joke
now
and
then
also
the
work
that
needs
to
be
done.
There's
a
lot
of
manual
testing,
so
we
don't
break
things
and
we
have
to
decide.
B
C
B
A
C
C
Yeah
but
unfortunately,
I
think
that
it's
prevalent
throughout
both
our
core
code
base
and
throughout
can't
rip,
because
that
was
kind
of
the
link
for
a
long
period
of
time.
Okay,
yeah,
fair
enough
anyway.
Yes,
we
do
have
an
issue
for
figuring
out
jQuery.
Just
in
general,
though
Jim's
a
version
number
issue,
number
handy
by
chance,
I
will
steal.
B
C
A
So
when
we
do
a
security
release,
we
are
supposed
to
request
a
specific
security
vulnerability.
Identification
number
from
I,
don't
know
authority,
it's
called
there's
someone
who
issues,
fancy
numbers
and
somewhat
worse,
less
used
to
request
one
so
that
anyone
who
is
referring
to
upon
the
grading
software
will
be
able
to
reference
it
by
this
particular
number.
A
So
now
in
the
future,
when
we
do
a
security
release,
anyone
is
able
to
do
so,
there's
a
form
that
needs
to
be
filled
out
and
a
couple
of
the
fields
in
there
sort
of
always
have
the
same
answers
for
us
and
so
I
put
all
of
the
questions
that
have
predictable
answers
or
where
to
find
them
in
that
documents,
and
hopefully,
next
time
we
have
a
security
release.
Anyone
can
take
on
the
task
of
requesting
a
CBE.
Yesterday,
I
request
one
for
the
first
time,
we'll
see
how
it
goes.
B
C
Yeah
yeah
I
do
I
kind
of
think
that
we
should
try
to
go
get
all
the
way
to
3x,
rather
than
like
moving
to
2
dot.
X
just
seems
like
we'll
have
two
times
that
will
break
things
rather
than
one
time
that
will
break
things
and,
of
course,
break
thanks
being
you
know,
there'll
be
an
API
change,
but
we'll
maintain
compatibility
so
they'll
be
kind
of
like
an
opt-in,
I,
think
type
situation
and
move
on
to
3,
dot,
X
I
think
that's
what,
but
you
should
hope
for
it
within
the
within
the
version.
B
C
D
A
Yeah
yeah
is
there
a
way
in
jQuery
to
provide
backwards,
compatibility
layer
between
virgins,
like
we
do
between
backdrop
and
Drupal
like
if
we
had
a
like
jQuery
like
file
that
include,
you
know
cash,
a
mind
and
wrapped
it
like
bind
wraps
whatever
the
new
alternative
is,
or
does
that
not
work?
Yes,.
B
Sir,
so
I'm
Donna
research
last
August,
so
May
and
this
posted
it
there
in
that
to
a
thing,
there's
a
migrate,
something
yeah
decorator
migrate,
module
that
you
can
use
that
provides
backwards,
compatibility
functions,
but
then
they
say
remove
this
at
some
point:
I'm
not
sure
anyways
I'll
do
awesome,
resets
again
and
see,
but
there
was
something
there
was
something
in
place.
So.
A
I
feel
like
if
we
can
get
the
backwards
compatibility
and
we
could
put
that
in
the
one
that
ex-french,
which
would
use
your
own
maintenance
if
there's
not
or
we're,
not
sure
we
can
guarantee
that
it
don't
work.
This
might
be
something
that
we
could
pushed
it
to.
I
also
haven't
finished.
Writing
up
the
issue
yeah,
but
I'm
opening
an
issue
in
the
pants
EQ
about
what
backdrop
to
means,
because
I
think
we
need
to
like
every
time
we
talk
about
it.
A
Really,
we've
got
three
options
and
I
think
we
should
like
commit
to
one
so
that
everybody
who's
moving
to
backdrop.
One
knows
what's
in
store
for
that
job
to
and
designing
the
kinds
of
things
we
want
to
break
in
major
version
changes.
It's
gonna
be
important.
I,
really
like
our
backwards
compatibility
policy
for
PHP,
but
there
are
a
bunch
of
things
like
this.
That
might
be
something
where
you
could
say.
This
is
what
you
can
expect.
A
Well
could
be
an
issue
and
moving
to
backdrop
to
like,
maybe
your
jQuery
custom
jQuery
stuff
will
need
to
be
updated
or
you
know.
Maybe
your
HTML
markup
is
gonna,
be
different
in
your
CSS
identifiers.
Aren't
going
to
match
and
you're
gonna
have
to
update
your
theme,
just
kind
of
setting
some
like
ground
rules
about
like,
even
though
we
say
we're
API
compatible.
We
have
major
version,
changes
and
stuff
is
gonna
shift
just
so
that
we're
upfront
about
an.
B
A
C
On
the
other
hand,
is
an
interesting
recollection
is
that,
even
though
governments
are
stuck
on
some,
some
environments
are
stuck
using
Windows,
7
and
98
or
whatnot
I.
Think
it's
Windows
XP
by
the
way
notes.
Knutson
it's
become
pretty
conventional
for
people
that
are
in
that
situation
to
just
use
two
web
browsers.
B
B
A
Like
it,
if
there
is
a
like
a
significant
portion
of
the
backdrop
community
that
is
stuck
on
these
computers,
they'll
probably
come
up
with
like
a
jQuery
down
grade
module
or
something
yeah,
it
would
do
the
things
that
we
did
with
the
jQuery
update
module
in
order
to
solve
that
front
like
this
is
something
that
can
be
solved
in
gym,
trim,
I,
don't
think
it
will
be
I,
don't
think
it's
I,
don't
want
to
worry
about
it.
Yeah.
A
C
That
issue
had
a
patch
for
a
long
time,
but
it
was
lacking
tests
we
got
tests
written
and
that
it's
now
merged
and
fixed
contextual
links
for
views.
Sometimes
the
contextual
link
for
a
view
would
end
up.
Like
way
underneath
the
admin
menu,
the
contextual
link
for
views
would
moved
down
into
the
wrapper
of
the
view
rather
than
being
on
the
entire
page,
and
so
that
one
has
been
merged
and
is
in
one
12:6
as
well.
C
And
lastly,
sometimes
core
self
updates
might
fail,
because
when
it
pulls
down
the
archive,
it
reads
all
the
info
files
to
make
sure
that
type
is
specified
and
sometimes
it
would
crash
when
it
encountered
a
profile
that
didn't
include
it
type
and
it's
studying
the
file.
So
we
just
added
type
because
profile
that
all
of
the
info
files
from
profiles-
that's
3553.
C
So
that's
great,
that's
four
of
our
issues
that
we
used
that
we've
been
bringing
up
for
over
a
month
and
all
four
of
those
have
been
fixed
entering
one
folk,
six,
one.
Twelve
seven
is
now
the
next
bug
fix
release
and
some
issues
that
we
still
have
lingering.
There
includes
an
RTL
issue
with
CK
editor
icons
issued
3504
currently,
as
did
needs
review,
I
think
that
we're
getting
really
close
there
to
get
that
one
wrapped
up
supporting
multiple
equivalent
security
releases
issue,
35
24,
you
know
with
the
111
9
that
just
came
out.
C
B
It's
been
out
to
be
seed,
it's
the
one
that
we
needed
to
adjust
the
regular
expression
that
picked
up,
which
files
the
file
names
of
the
dot
p
o--
files
that
we
added
so
that
it
can
be
included
in
the
drop
down.
When
you
install
backdrop,
oh
yeah,
and
all
the
file
the
pull
request.
So
this
has
been
al
to
be
seen
by
head.
B
C
Okay,
great
yeah
that'll
help
with
the
Installer
for
people
installing
backdrop
and
other
languages
and
also
speaking
of
the
Installer
installing
in
other
languages,
there's
the
most
embarrassing
link
because
it's
the
very
first
link
you
see
once
the
very
first
word
you
see
when
you
installed
backdrop
is
like
install
backdrop
in
another
language
and
it
links
over
to
Drupal.
That
word,
that's
embarrassing.
So
we've
got
thirty
five.
C
Sixty
that
switches
that
link
over
to
a
new
documentation,
page
on
vector
of
CMS,
towards
saying
how
to
install
backdrop
in
another
language
which
is
super
awesome,
so
that'll
be
great
one
12:7.
Those
are
the
issues.
We've
got
a
call-out,
although,
as
always,
we
have
a
large
bucket
of
other
issues
that
are
underneath
that
same
milestone.
C
113
113
is
the
next
minor
version
of
backdrop.
It'll
be
coming
out.
May,
15th,
2019
and
feature
freeze
is
less
than
2
short
weeks
away.
Future
priests
will
be
made
first,
so
we've
got
some
work
to
do.
I
think
what
113
is
looking
a
little
light
as
far
as
a
new
functionality.
I
know
that
there's
they
have
a
couple
of
issues
that
have
been
merged
into
one
thirteen,
but
they're
not
really
like
headline
like
features
things
that
are
coming
along
pretty.
Well,
though,
adding
back
field
for
matters
a
lot
from
Drupal
6
is
issue.
C
B
So
the
status
of
the
module
is
really
good,
like
I
can
go
in
there's
just
a
few
minor
issues
with
the
UI
just
some
labels,
some
things
that
do
not
work
as
expected,
but
it's
in
good
shape
in
general,
and
the
decision
was
that,
with
regards
to
features
that
were
requested
with
new
blocks
that
can
be
added,
these
can
be
done.
Iteratively
in
future
versions,
even
even
I
mean
they
might
not
even
be
considered
features
and
might
be
done
in
bug-fix
releases.
If
it's
fixes.
B
Yeah,
the
most
annoying,
the
most
annoying
thing
it
was
that
I
came
across
was
that
we
are
actually
this
function.
That
provides
the
listing
for
the
available
updates
thing
and
there's
a
block
that
provides
the
all
the
available
updates.
But
we
are
sort
of
like
polluting
that
function
with
with,
but
by
adding
some
classes
into
the
arrays
that
it
generates
it
produces.
C
Great
yeah
I
even
looked
at
it
recently
since
since
icons
are
added
and
started
looking
a
lot
nicer,
yeah,
it's
a
little
bit
of
a
fire
hose,
but
but
I
do
think
it's
likely
better
than
the
really
terrible
pattern
that
we
have
of
showing
you
user
slash
one
when
you
log
in
and
just
tell
you
anything
except
for
how
long
you've
got
a
member
or
its
login
behavior
yeah.
B
This
this
issue
has
been
one
of
the
oldest
issues
that
we
have,
and
then
I
mentioned
in
the
previous
meeting.
That
I
was
watching
a
presentation
for
the
Lightning
distribution
and
they
also
include
a
dashboard,
didn't
have
the
chance
to
actually
check
what
that
is.
But
our
advantage
is
that
we
are
using
layouts
and
we
allow
people
to
just
add
blocks
there
and
do
it
like
utilize.
It
again.
It
gets
more
more
intuitively
yeah.
A
B
C
495
is
in
good
shape
and
that,
in
that
case,
like
two
weeks
before
committing
is
plenty
of
time,
and
we
we
do.
You
know,
really
strive
to
commit
stuff
when
it's
like
to
a
point
that
we
know
that
we're
not
kind
of
major
change
those,
but
it
might
not
be
perfect
yet
and
then
iterate
on
it,
and
that
will
definitely
be
the
case
for
this
module
that
we'll
probably
be
seeing
lots
of
minor
changes
to
it.
B
You
do
yeah
one
of
the
most
sort
of
like
I,
guess
obvious
features
that
we
want
from
WordPress
as
well
ways
to
communicate.
Changes
to
people
like
this
desperate
is
going
to
be
used
by
administrators,
so
we
might
want
to
communicate
and
we
have
automatic
updates
coming
on.
So
we
might
want
to
say:
hey
your
site
has
been
updated.
This
is
what
the
main,
if
the
major
things
that
have
changed.
So
it's
a
it's
a
good
yeah
or
news
from
curated
news
from
Latrobe
world
yeah
yeah.
C
A
C
C
C
So
as
that
needs
review
on
the
first
set
of
config
files
that
get
these
translated
strings
package.
Signing
in
the
category
of
automatic
updates
is
issued.
1992
john
franklin
posted
a
whole
series
of
updates
about
a
month
ago
and
I've
slowly
been
working
through
reviewing
all
the
work
that
he's
been
doing.
I
got
caught
up
in
working
on
project
module.
C
John's
work
has
been
really
comprehensive,
like
he
hasn't
just
written
contribs
or
add-on
modules
that
can
be
added
to
core
and
he's
also
been
working
on
project
module
to
deal
with
the
providing
portion
of
or
the
the
signing
portion
of
the
operation,
and
it's
looking
really
great
I
appreciate
that
he's
working
with.
In
many
cases.
This
might
not
be
a
good
thing,
but
he's
working
within
the
monolithic
model
of
backdrop
that
backdrops
EMS
org
is
currently
where
the
packaging
happens
and
the
approach
days
taking
is
is
make
it
so
that
dr.
C
of
CMS
org
weight
gained
a
new
module
that
would
give
it
the
capability
to
sign
things
that
are
created
by
project
module
and
he's
building
out.
New
API
is
into
project
module
so
that
the
package
here
right
now
is
just
exists
within
a
a
chunk
of
custom
code
on
backdrop,
CMS
org
and
because
now
there's
going
to
be
other
things
interacting
with
the
packaging
process,
including
adding
signatures
is
building
out
the
capability
for
these
things
to
interact
with
each
other,
and
so
it's
all
of
looking
really
great.
C
It's
pretty
unlikely
that
a
update
module
will
actually
start
or
that
then
we'll
get
all
of
this
in
for
113.
But
it
is
totally
possible
that
we
could
at
least
make
backdrop
CMS,
org
start
signing
packages
and
in
click
the
signature
information
in
the
feeds
in
the
near
future.
So
we'll
have
the
feed
set
up
with
signatures,
but
core
probably
won't
be
capable
of
actually
validating
them
for
a
little
while
yet
well,.
B
C
Amazing
and
I
mean
this
is
the
amount
of
incredibleness
on
this
is
pretty
overwhelming.
He
also
wrote
two
alternative
ways
of
signing
stuff
with
SSL
or
with
GPG,
and
we
basically
get
to
not
choose.
You
know
which
one
do
we
want.
It
really
depends
on
which
one
is
the
most
widely
available
or
most
compatible
I.
Think
it
also
really
like
the
implementation.
I'd
started
that
used
sodium
was
very
direct
and
very
non
pluggable.
It
gives
us
the
opportunity
if
we
want
to
use
sodium.
Like
you
know
we
could.
C
C
Actually,
the
best
decision
right
now
probably
won't
be
the
best
decision
two
years
from
now.
Okay,
because
GPG
is
probably
the
right
decision
now
and
that's
one
one
John
is
leaning
towards
because
it's
the
most
universal,
it's
like
what
all
Linux
distributions
used
to
validate
all
of
their
packages,
for
example.
However,
a
GPG
will
probably
never
be
a
part
of
PHP
core
which
sodium
already
is
in
PHP
7.2
I,.
B
C
C
C
A
C
Okay
and
I
think
that
that's
something
that,
when
you
do
evaluate
is,
is
do
a
run
through
your
hosts
and
see
what
is
typical
and
say,
I'm
sure
that
well
actually
just
because
it's
also
strange
just
because
they
have
s
open
SSL,
which
every
server
will
have
because
they
have
to
you,
have
it
for
HTTP
doesn't
mean
that
they
have
the
PHP
extension
that
works
with
openness
or
so,
and
so
I
think
GPG
is
going
to
be
our
most
likely.
It's
going
to
be
widely
available
solution,
okay,.
C
A
What,
if
we,
so
you
definitely
to
find
the
use
case
for
having
to
be
pluggable
and
I,
think
that
that
also
leaves
us
time
to
say
like
okay,
wolf,
you
know
today.
This
is
our
exclusion
this
little
yesterday
and
we'll
keep
an
eye
on
sodium
and
if
it
becomes,
you
know
that
most
servers
now
offer
PHP
7.2
and
therefore
have
sodium
or
are
planning
on
moving
to
PhD,
77
to
and
I've
added
sodium
and
PHP,
71
or
70,
or
whatever
else
they're
running
that
could
become.
A
B
C
Yeah
and
I'm
not
quite
sure
how
we'll
manage
this
in
court
John's
modules
right
now,
there's
a
module
called
code
sign
and
looks
like
code
sign.
He
has
filed
a
pull
request
against
cor.
I,
haven't
gotten
to
the
point
of
evaluation
that
I
that
I've
looked
at
that
segment
yet,
but
I
have
to
wonder
like
if
that's
part
of
core
like
should
that
just
be
like
a
hidden
module,
because
it's
like
really
like
highly
technical,
what
that
service
would
actually
be
providing.
You
know,
yeah
yeah,.
A
It
should
just
be
I
think
like
so
it
could
be
a
hidden
module.
It
could
be
required
by
installer
module
or
something
so
that,
if
you're
trying
to
do
automatic
updates
or
manual
UI
updates
or
whatever
it's
in
there
and
it
does
the
background
job.
But
if
you're
not
doing
those
things,
if
you
don't
have
to
have
it
on
right.
A
C
C
Yeah
yeah
I
think
it's
really
discussing
that,
but
yeah
there's
a
lot
of
stuff
to
look
at
there
and
we
are
moving
forward,
especially
on
the
backdrop
see
my
start
or
side
of
things.
It's
really
exciting
and,
lastly,
telemetry
module.
Speaking
of
things
that
require
a
backdrop,
CMS
organization
issue,
285
the
idea
being
that
we
start
collecting
more
information
from
installations
of
backdrop
via
an
opt-in
process,
to
like
tell
us
your
PHP
version
and
my
sequel
version
and
what
modules
you're
running
more
granular
information
than
we
currently
get
from
project
module.
C
A
D
A
A
B
C
C
A
Things
one
thing
we
start
talking
about
before
you
got
here:
Nate
was
that
there
seems
to
be
some
chatter
in
the
back
job
world
about
separating
security
fixes
from
other
bug-fix
releases
and
I
know
that
that's
something
they've
started
to
do
in
Drupal
as
well,
where
there
will
be
one
release,
that's
only
the
security
fix.
Then
there
will
be
another
one.
It
can
take
a
bunch
of
other
stuff
I.
Personally,
don't
like
the
separation
of
them,
because
I
feel
like
it
makes
more
work
for
me
as
the
maintainer
of
a
million
Drupal
7
sites.
A
That
I
have
to
do
like
one
update
one
week
and
then
I
have
to
do
another
update
the
next
week
and
it's
frustrating
that
I
have
twice
the
work
when
I
could
have
just
had
one
updating
all
of
them,
and
so
it
would
be
interesting
to
think
about
what
what
problem
this
solution
is
trying
to
solve
and
sort
of
reimagine
the
problem
space.
So
I'm.
A
Time
to
get
into
a
big
discussion
about
this
today,
but
Grenadians
throw
some
ideas
around
about
like,
rather
than
having
more
releases
that
we
have
to
update
more
often
if
we
had
like
a
tested,
safe
rollback
option
so
that
if
it
did
break
everything,
you
would
have
like
an
unobvious
P.
That
would
be
able
to
like
reverse
the
things
that
happened
in
update
attached
to
PHP,
so
that,
if
you
like
applied
an
update,
didn't
realize
it
broke,
something
got
a
whole
bunch
of
new
content
later
realized,
something
that
was
broken.
You
could
down
date
instead.
A
A
C
C
Let's
say
there
I'm,
not
sure
that
these
versions
are
actually
correct,
but
one
12/5
came
out
and
say
one
twelve:
five
had
a
bunch
of
bug
fixes
in
it,
but
one
twelve
six
came
out.
Imagine
it
was
the
security
only
fix,
but
my
site
is
still
running
112
four,
because
that
was
the
security
fix.
So
I
have
to
go
through
a
bug,
fix
release
that
includes
non
security
fixes
in
order
to
get
the
security
fix,
and
that
happens
to
me
pretty
much.
Every
time.
C
I
update
that
it's
like
you
already
have
to
be
on
the
latest
bug
fix
release
in
order
to
get
a
security,
only
fix
we're
not
going
to
make
a
security
only
fix
for
every
bug,
fixed
version
that
there
is
so
the
likelihood
of
you
having
a
site
that
only
gets
a
security
fix
and
doesn't
have
anything
else
whatsoever.
I,
don't
know
maybe
I'm,
maybe
I'm,
projecting
too
much,
because
you
know
maybe
some
people
are
more
keen
on
doing
things
like
all
the
time,
but
even
when
we,
you
know,
add
automatic
updates.
C
We
talked
about
some
kind
of
like
security
only
fixes,
but
there
won't
be
really
the
option.
I
think
I
think
we
actually
talked
about
how
security
only
fixes
are
almost
impossible.
Because
of
this
problem.
We
can't
just
apply
security
fixes
because
we
have
to
go
through
other
bug,
fix
versions,
and
so,
instead
in
automatic
updates,
we
talked
about
having
it
be
automatic
updates
within
the
minor
version
or
automatic
updates
within
the
major
version,
and
then
that's
the
level
of
granularity.
You
have
there's
no
security,
only
option,
there's
bug,
fixes
only
vs.
bug,
fixes
and
features.
B
For
those
sites
that
are
not
regularly
updated
with
content,
the
smaller
sites
I
mean
than
the
ones
that
have
less
traffic,
we
also
have
a
follow-up
for
backing
up
things
before
we
do
the
upgrade.
So
there
will
be
a
package
there
with
the
database
and
people
can
resent
its.
It's
not
gonna,
be
implemented
as
part
of
the
auto-updates.
We
guess
it's
a
follow-up
issue,
but
it
still
is
there
yeah
super.
A
C
B
We
couldn't
apply
the
security
fix
and
it
didn't
apply
to
the
backdrop
version
because
it
wasn't
updated
since
2016,
so
we
are
trying
to
bring
it
up
to
date,
but
this
came
up
and
was
that
in
the
meantime,
we
only
had
a
one
hook
up
tight
for
1000,
which
is
the
hook
that
we
use
to
grab
the
firewalls
and
then
convert
him
to
config
and
then
delete
the
Vagos.
In
the
meantime,
there
were
two
other
settings
or
variables
that
have
been
added
in
the
7.6
seventh
of
X
version
and
they're.
B
A
So
our
update
hooks
need
to
account
for
not
only
the
people
who
did
the
initial
migration
and
that
are
updating
the
backdrop
module,
but
people
who
are
coming
in
anytime
from
7:00,
and
so
that
makes
the
upgrades
a
little
messy,
because
the
initial
and
you
have
to
say
hey,
you
need
to
have
been
at
least
on
version
X
on
Drupal
7.
But
then,
after
that,
you've
already
met
that
initial
requirement,
and
so
every
update
hook
needs
to
check
and
see
if
the
update
needs
to
be
run
before
it
runs
itself.
A
I
know:
I've
run
into
this
a
lot
with
some
of
the
modules
I've
been
trying
to
maintain.
We
run
heavily
Co
maintainer
on
Drupal
7,
who
will
do
things
and
I'm
like?
Oh,
we
need
to
pull
this
in
and
then
I'm
like
oh
I,
need
to
handle
my
updates
too,
and
it
does
get
sloppy
so
I
think
having
some
very
explicit
instructions
on
how
to
handle.
That
would
be
really
useful.
I
think.
B
Yeah
I
think
that
documenting
it
as
well,
if
we
have
a
specific,
so
that
can
be
upgrade
thing.
But
the
point
is
that,
because
we're
trying
to
get
the
security
update
for
which
is
not
actually
a
security
problem
at
the
moment,
because
we,
it
doesn't
apply
to
the
current
version,
but
but
in
order
to
move
things
with
this
specific
module
is
the
correct
solution
to
create
a
new
hook
and
then
add
for
those
two
variables
that
were
added,
add
a
viable
grab.
A
D
C
It's
sort
of
thinking
that
is
the
way
that
a
lot
of
JavaScript
development
happens
that
instead
of
doing
browser
checking
like
are
you
running
a
year
or
are
you
running
Firefox,
which
is
unreliable?
Instead,
you
do
feature
detection
and
say
if
this
thing
exists
in
the
first
place
then
deal
with
it.
You
know
or
then
enhance.
This
feature
then
make
it
available.
I
think
that's
the
safest
way
to
approach
things
instead
of
assuming
a
particular
state
check.
A
C
B
B
C
Yeah
Jen,
also
put
in
here
there's
a
special
hug
hug
update
last
removed
that,
as
an
alternative,
I
would
say
perhaps
less
robust
way.
Your
module
could
also
decide
that
it
only
allows
updating
from
the
very
latest
version
of
the
Drupal
7
equivalent
and
that
forces
the
module.
When
you
run
the
update,
it
has
to
be
running
the
latest
version
of
the
Drupal
7
module.
Oh
yeah,
it
does.
You
know
please.
C
And
so
it
looks
for
an
update
from
Drupal
7
under
the
7000
number.
That
says
that
it
has
to
have
at
least
that
version
before
it
will
run
any
updates
and
backdrop
is
it's
a
little
again,
it's
a
little
bit
weird
that
we
have
to
deal
with
the
versioning
thing,
but
Bangkok
will
run
7,000
updates,
it'll,
consider
them
before
1000
updates.
So
when
you
say
hook
update
last
removed-
and
you
say
7010,
it
considers
7000
intent
to
be
before
update
1000,
okay,
yes,
yeah
and.
A
D
A
D
A
A
A
So
I
just
saw
your
thing
about
updates
and
it
triggered
I
saw
comments
from
olaf
about
the
issues
who
is
having
upgrading
from
Drupal
7,
and
there
are
a
bunch
of
like
similar
modules
in
Drupal
7
can
trim
to
what
we're
doing
in
back
to
our
core.
That
I
think
it
might
be
worth
adding
update
hooks
for
so
things
like
menu
block
module
right.
A
You
don't
need
my
new
block
module
and
backdrop,
but
if
you
had
menu
book
module
in
Drupal
7
and
you
uninstall
it
you're
gonna
lose
all
the
configurations
on
your
blocks
and
when
you
move
into
backdrop,
you're
gonna
have
to
reconfigure
those
blocks.
We
could
provide
an
upgrade
path
for
a
menu
block
that
would
define
the
same
settings
on
a
core
block
for
backdrop.
A
So
I
just
had
a
note
here
about,
like
I,
would
like
to
invest
time
in
doing
these
kind
of
updates,
but
I
wanted
to
get
kind
of
like
consensus
as
to
whether
we
should
and
I'll
go
ahead
and
create
an
issue
for
each
one
will
be
like
here's,
a
partial
upgrade
from
menu
block.
Those
are
the
things
were
upgrading
and
these
are
the
things
are
not
because
we
don't
want
all
the
features
that
are
in
your
book
and
that
way
people
can't
heard
of
this
in
the
future
and
see
what
kinds
of
things.
B
B
A
This
is
a
good
question
too.
It
really
depends
on
if
I
need
that
data,
in
fact
up
or
not
right,
because
if
you
uninstall
a
module,
it's
gonna
delete
all
your
variables.
It's
gonna
throw
your
database
table
and
if
you
need
that
data,
you
don't
want
to
install
that
module
first.
So
in
those
cases,
I
also
want
to
write
an
update
hook.
That
will
say,
like
hey,
you
have
X
module
installed
in
Drupal
7.
A
Let's
turn
it
off
for
you
and
because
we're
repurposing
the
menu
block
data
for
core
blocks,
we'll
turn
off
the
menu
block
module
in
your
system
table.
So
you
don't
have
to
delete
it
and
you
don't
lose
the
data,
but
then
I
think
we
also
need
to
have
in
that
list
of,
like
modules
moved
into
core
whatever
we
need
to
have
like
this
one
provides
an
upgrade
path.
This
one
does
not
so
that
if
you
uninstall
a
module,
you
know
you're
gonna
lose
the
data.
You're
gonna
have
to
move
the
data
on
yourself.
A
So
I
think
this
is
the
kind
of
thing
where
we
need
to
specifically
state
people
are
upgrading
uninstall
menu
block,
don't
run
in
so
many
buttons,
one
or
the
other,
so
that
they
know-
and
this
is
also
gonna
happen,
like
every
site
that
gets
upgraded,
is
gonna.
Have
more
of
these
questions
to
start
abusing
different
modules
and
it'll
be
good
to
you
know
anything
that
would
put
similar
functionality
in
core
make
sure
that
we
either
have
an
upgrade
path
or
state
that,
like
you're
gonna,
have
to
reconfigure
it
one
way
together.
You.
C
It's
hang
on
does
it.
It
deletes
the
variables
once
they're
moved
over
yeah.
In
the
backdrop
case,
it
deletes
it
from
the
system
table.
Oh
it
does
that
oh
I
see
it
does
that
either
way
so
because
we
wrote
these
at
the
same
time,
1000
will
execute
in
1,001
will
execute
at
the
end
of
1,001.
It
deletes
from
the
system
table
the
path,
auto
entry
line
so
effectively
it
uninstalls
it.
C
B
And
it
depends
on
a
huge
case
whether
the
module
that
you're
in
question
has
been
migrated
to
contributory.
We
based
the
feature
cat
much
about
directly
into
core,
without
quoting
the
module
in
our
contribute
first,
so
it
is
per
used
case,
but
yeah.
It
also
and
also
see
how
that
function
saved
as
well
the
what
forgot
the
name
of
the
function
now
with
the
options.