►
From YouTube: Backdrop Weekly Jan 4th
Description
Today’s development agenda: http://bit.ly/2lezgNH
A
B
A
Since
our
last
meeting,
we
have
a
new
contributed
community
member
new
contributor,
Jerry,
Hudgens,
ported,
token
filter
and
I'm,
currently
working
with
them
in
the
issue,
queue
to
get
the
history
preserved
from
Drupal
7,
but
I'm
not
expecting
that's,
take
very
long
and
then
we'll
get
a
new
project
and
I
can
do
repo.
So
thanks
Jerry
for
doing
all
the
work
on
token
filter
and
welcome
to
backdrop.
A
I
removed
the
issues
from
the
agenda
about
backdrop
CMS
to
work
in
the
forum
site
because
we
talked
about
those
a
lot
last
week.
We
also
talked
about
them
earlier
today
in
the
design
meeting.
So
if
your
inner
students
in
hearing
about
a
few
minor
design
issues
that
were
working
on,
you
can
definitely
watch
the
recap
of
that
meeting.
A
Basically,
the
only
news
is
that
we
have
the
new
drop-down
menu
on
both
sites,
we're
working
on
cleaning
up
active
state
and
if
you
have
any
feedback
on
design
issues,
let
us
know
we're
always
happy
to
take
in
feedback
and
improve,
but
nothing
pressing
on
either
of
those
topics.
So
Nate
I'd
like
to
turn
it
over
you
to
talk
about
backdrop,
CMS
release,
stuff,
okay,.
B
All
right,
so
man,
lots
of
things
have
happens
january
1st
was
our
feature
freeze
for
backdrop,
1.9
and
so
the
functionality
that
we
have
in
the
one
point
x
branch
is
basically
going
to
be
what
1.9
is
plus
or
minus
some
additional
bug
fixes
if
we
can
still
complete
those
things
before
january
15th,
On
January
1st,
we
haven't
cut
a
preview
release
yet,
but
we
did
cut
the
one
point:
8.1
release
yay.
So
finally,
you
know
now
there
were
only
10
days
up
from
1.9
release,
who
finally
released
a
bug-fix
release
for
1.8.
B
The
good
news
is
there:
is
that
really
the
kind
of
good
news
is
that
it
really
contains
a
really
pretty
small
number
of
fixes,
there's
about
a
dozen
small
items
that
were
fixed
in
one
point
8.1,
and
so
that
is
out
there.
There
is
still
a
couple
of
minor
items
that
need
to
be
done
to
fully
complete
that
task
of
making
that
release
issue.
B
29
31
is
our
tracking
for
making
sure
that
all
of
the
steps
are
completed
for
finishing
the
release
and
the
items
that
are
missing
include
things
like
updating
the
docker
images
pushing
out
to
the
panthéon
repository,
updating,
Wikipedia
and
also
tweeting.
We
didn't
actually
tell
anybody
that
one
point
8.1
is
out
there
at
least
via
tweets,
but
of
course
it's
on
backup,
CMS,
org
and
update
mantra
will
tell
everybody
that
there's
new
version
available,
so
that's
great
that
that
got
put
out
there
and
it's
available
for
download.
B
Now
one
point
eight
point:
two:
we
will
still
release
a
one
point.
Eight
point
two,
including
any
bug
fixes
that
happen
between
now
and
January,
15
and
one
point
eight
point
two
will
come
out
at
the
same
time
as
backdrop,
one
point:
9.0
items
that
I'd
like
to
see
at
one
point
eight
point
to
include
these
cross
ports.
These
cross
ports
from
Drupal
had
just
been
dragging
along
for
a
long
time.
A
B
Wow,
that's
excellent,
yeah
sure
enough
this
a
couple
days
ago,
that's
fantastic!
So
those
issues
are
issue
numbers,
twenty
thirteen,
2774
2775,
twenty
seven,
seventy
six,
so
that's
great
okay,
looks
like
that's
back
on
my
plate
to
get
those
things
reviewed.
Of
course,
anybody
wanting
to
do
those
testings
or
code
reviews
marking
things
are
TBC
is
highly
appreciated.
B
Okay,
one
point:
nine
one
point:
nine
is
coming
out
in
11
days:
January
15th
2018.
So
let's
see
that
is
looks
like
that's
a
Monday
which
is
a
great
day
for
making
releases.
So
there's
no
holidays,
no
special
occasions
around
January
15th,
so
I
believe
that
it,
but
there
won't
be
any
unexpected
changes
in
schedule.
B
What's
going
to
be
in
1.10
well,
it
looks
like
the
primary
thing
that
we
did.
Finally,
accomplished
is
the
ability
to
edit
files,
sorry
manage
files,
and
so
you
can
go
to
the
manage
files
listing
page,
which
has
already
been
there
and
in
addition
to
the
delete
functionality
which
had
already
existed,
we
now
have
a
manage
link
on
individual
files,
allowing
you
to
replace
that
file
or
modify
its
properties,
the
obvious
follow-up
to
that
of
making
it
so
that
you
could
upload
a
file
independently
of
other
content,
which
is
issue
2633.
B
We
didn't
get
done
so
that's
fine
that
just
gets
bumped
to
the
next
release.
So
that
looks
like
you
know,
editing
the
existing
file.
You
know
that's
not
like
the
biggest
feature
in
the
world,
but
that's
probably
going
to
be
the
item
that
is
kind
of
like
featured
as
far
as
the
1.9
functionality
goes.
I
think,
there's
a
couple.
Other
minor
items
I
think
there's
a
couple:
API
additions
that
have
been
added
through
the
1.9
release,
but
functionality
wise.
That's,
probably
what
users
are
going
to
see.
That's
a
big
difference,
so
that's
it
1.9.
B
We
still
have
time
to
do
user
experience,
improvements
and
bug
fixes
before
1.9
comes
out,
so
keep
an
eye
on
those
things
that
are
in
the
queue
being.
Tags
is
1.9,
we'll
probably
start
going
through
the
1.9
features
and
bumping
all
of
those
to
1.10
here
in
the
next
couple
of
days,
so
yeah,
that's
it.
For
the
month
point
9
update.
B
1.10
1.10.
Yes,
what
a
funny
number
one
point:
10
we've
had
some
discussions
back
and
forth
about
rolling
from
1.9
to
2.0,
but
there's
some
repercussions
that
would
come
with
that
change
given.
If,
if
we
don't
reach
a
decision
about
going
to
2.0,
which
at
this
point
we
wouldn't
do
any
like
API
Briggs
but
calling
it
2.0
and
not
having
it
Frank
api's.
B
B
Barring
any
changes,
that's
probably
what's
going
to
end
up
happening,
so
what's
going
to
be
in
1.10,
so
the
most
obvious
candidates
include
these
two
items
that
were
marked
as
high
priority
for
1.9
that
didn't
get
completed.
Uploading
a
file
manually
and
making
files
feel
double
issues:
26,
33
and
26:32.
B
Both
of
those
have
for
requests
they're
not
too
far
off
from
being
complete
and
are
good
candidates
for
being
included
at
one
point.
10
other
items
in
1.10
there's
been
a
good
amount
of
progress
made
during
the
1.9
cycle
that
we
mentioned
every
now
and
then
but
I've
never
really
been
in
our
like
high
priority
list
regarding
translation
capabilities
and
there's
a
lot
of
work
happening
in
this
related
to
the
backdrop
for
good
project
which.
B
B
Sorry
I've
no
idea
what
happened
there:
okay,
thanks
yeah
I
hate
to
say
that
might
be
the
problem.
Okay,
I
was
last
talking
about
backdrop
for
good
I.
Think
that
you
guys
get
to
that
part.
Yeah.
C
B
We
heard
that
okay,
yeah
and
so
there's
been
a
lot
of
items
that
they've
been
coming
out
of
that
project,
because
they're
trying
to
internationalize
their
website
and
there
they
from
to
some
issues
with
that.
So
what's
coming
out
of,
that
has
been
some
nice
work
config
a
translation
issue.
704
has
seen
some
progress
Jeff,
so
deputy
has
gone
through
and
stuffed
out
kind
of
some
proof
of
concept
and
there's
some
other
suggestions
and
that
common
thread
about
how
we
can
implement
config
translation.
B
So
the
ball
is
rolling
on
that
issue,
which
is
great
and
issue.
225
saw
some
exciting
movement
this
week
as
well,
but
there
was
a
a
poor
request
made
a
long
time
ago.
All
the
way
back
in
2014
looks
like
yeah
I
know
it's
crazy,
we're
getting
that
point.
Bye,
Cree
boo,
not
sure
how
else
to
pronounce
that
but
Creepo
filed.
B
So
Olaf
did
some
code
review
on
that
or
functionality
review
on
that,
and
that
was
awesome,
Thank
You
Olaf,
and
if
anybody
else
would
like
to
try
it
out,
there
is
the
live
sandbox
it's
on
the
pull
request.
An
issue
at
225
would
be
great
to
get
some
more
feedback,
both
code
feedback
and
UX
feedback
on
how
well
that
many
translation
capability
works.
B
B
Okay,
well,
that's
all
that
I
want
to
mention
for
1.10
the
real
items
for
these
next
couple
of
weeks.
Of
course,
we'll
be
getting
1.9
polished
without
the
door,
but
it's
never
too
soon
to
start
thinking
about
the
next
release.
So
yeah
I'm
excited
to
see
our
one.
My
tent
takes
us
and
get
started
on
that
release.
Once
1.9
is
up
there.
B
C
B
Saw
I
know,
I
know
where
you're
heading
with
this
I
haven't
tried
it
yet
have
you
had
any
experience
yet
like
not.
C
What
backdrop
yet
I
have
experience,
fixing
some
PHP
errors
on
a
Drupal
7
site
and
then
I
managed
to
lost
my
entire
development
environment
for
doing
Drupal
8,
because
Drupal
8
has
some
core
functions
that
don't
work
in
PHP
7.2
that
they're
not
actually
fixing
until
8.5,
so
I
just
had
to
tell
a
client.
Sorry
I
can't
actually
work
on
your
Drupal
8
site
right
now,
because
I'd
have
to
recreate
a
whole
new
development
environment
but
yeah
so
I'm.
C
B
C
B
It's
your
cutting
edge
and
that's
that's
where
things
are
changing
like
what
what
happened
here
is
that
I
hope
I
can
explain
this
accurately.
Is
that
inherited
classes?
The
signatures
for
methods
has
to
match
identically.
You
can't
change
signature
between,
like
a
child
like
an
inheriting
class
that
has
a
method
and
its
parent.
That,
as
a
method,
has
to
be
exactly
the
same.
Signature
and
Drupal
eight
introduced
some
code
where
the
signature
changes
in
between
different
child
classes,
that
inherit
from
a
parent
class,
and
so
in.
C
It
and
it's
mostly
like
leaving
off
like
a
variable
that
you
don't
need
passed
into
your
version
of
the
function.
So
it's
like
it's
kind
of
it's
really
annoying,
because
there's
a
bunch
of
little
things
that
don't
break
anything.
That
PHP
has
normally
been
very
good
at
just
sort
of
ignoring,
and
you
know,
sort
of
knowing
your
intentions
but
just
became.
It
just
became
very
intolerant
of
any
any
PHP
issues
which
which
seems
contrary
to
like
that
poll,
PHP
projects
being
for
you
know
more
intermediate.
Programmers
but
yeah.
B
Yeah,
it's
a
sad
to
say
it's
a
surprising
shifts
that
previously
previously
in
old
PHP,
they
would
have
given
new
years
for
a
change
like
this
in
between
like
okay.
This
now
throws
a
warning,
but
you
can
suppress
it
in
the
PHP
setting
or
it's
even
turned
off
by
default.
The
warning
is
turned
off
by
default,
but
the
next
version
they
turn
on
the
warning
and
then
the
next
version
after
that
and
make
it
an
error.
B
C
A
A
B
B
B
Okay,
well,
I
think
that's
it
for
our
on-air
discussion.
We're
gonna
chat
afterwards
a
little
bit
about
bloc
translation
but
yeah.
Let's
keep
this
meeting
short
and
sweet
focus,
mostly
on
1.9.
We've
got
11
days
before
that
happens.
So
let's
make
the
best
of
those
days
and
see
what
other
minor
things
we
can
still
make
in
the
release
to
make
it
to
making
sure
gasps.
So
alright,
thank
you.
Everybody
we'll
talk
to
you
guys
again.
Next
week,
hi.