►
From YouTube: Kyma Core SIG community meeting 20181107
A
Reckons
computer
great
so
hi.
Everyone
welcome
on
our
fourth
core
meeting
and
today
I'll,
be
your
moderator
and
Ahmed
is
helping
me
with
taking
notes
and
the
first
topic
will
be
announced
about
announcing
about
and
commit
the
release
done
by
Haase
and
then
Ahmed
will
presently
proposal
about
the
future
gates.
Functionality
and
last
but
not
least,
Marja
schinsky
will
give
us
some
updates
about
the
committee
stuff
and
of
course,
as
always,
please
place
your
name
on
the
list
and
at
the
end
of
the
meeting,
will
have
a
standard
slot
for
the
Q&A.
B
You
yeah,
okay,
so
it's
only
un
and
sorry
about
that.
As
you
know,
the
current
release
that
we
have
in
github
is
this
0.4
dot
3,
which
we
released
in
October
17th
and
since
then,
we've
been
working
on,
basically
a
number
of
bugs
that
have
been
fixed
and
a
little
bit
of
extra
features.
So
we're
working
now
on
our
preparing
our
next
release,
which
would
be
the
0.5
branch
and
that
branch
is
expected.
B
I
mean
that
the
first
step,
let's
say
in
our
release
process,
is
that
we
will
create
the
branch
for
that
release,
which
we
expect
to
do
tomorrow,
and
if
everything
goes
fine
and
our
testing
is
successful
and
so
on,
then
we
expect
to
have
the
0.5
release
in
github
by
the
end
of
the
week
next
week.
So
yeah
keep
stay
tuned
and
of
course
you
will
see
the
release
and
the
changed.
Look
in
github
as
usual.
C
Yes,
we
have
a
proposal
for
a
feature
introduction
that
you
can
find
the
pure
request
for
on
our
public
community
Ripple.
The
proposal
is
about
how
to
introduce
new
changes
or
a
new
feature
in
kheema,
and
it
uses
one
of
the
recent
big
sources
of
changes
in
kheema,
which
is
rebasing
quemic,
a
native
as
a
use
case.
The
proposal
basically
provides
how
we
can
use
feature
toggles
or
feature
gates
how
we
could
have
any
sort
of
profiles
and
explains
the
use
case
of
Canada
to
do
that.
C
C
The
feature
introduction
proposed
can
be
found
from
the
feature
from
the
decision
record,
and
the
idea,
basically,
is
that
we
would
use
the
installer
profile
to
provide
both
different
installation
components
and
provide
feature
gates,
and
if
you
think
about
the
use
case
for
kima
on
k
native,
there
is
a
very
small
analysis
for
any
new
component
that
will
be
provided
on
kima
with
respect
to
k
native.
So
there
is
a
legacy.
Only
component,
which
is
a
component
that
runs
in
the
old
kima
style
without
creative,
there
are
two
dual
modes
components.
C
One
of
them
is
not
affected
at
all,
so
it's
not
any
changes.
The
other
one
will
be
a
modified
that
can
work
in
both
modes
with
kenny
given
without.
However,
it
needs
to
be
aware,
when
it's
running
in
k
native
to
let's
say,
provide
a
different
functionality
or
do
provide
the
existing
functionality
in
a
different
way,
and
there
is,
of
course,
kinetic
only
components
that
should
only
be
installed
in
kima
when
it
is
running
in
kinetic
mode
and
to
provide
that
in
our
solution.
Maybe
let
me
open
this
diagram.
C
Variable
it's
up
to
you
in
that
case,
and
basically
that
means
that
for
the
Installer
we
can
have
profiles
and
the
profiles
will
be
under
installation
resources,
profiles,
profile
name
and
inside
that
profile
name.
You
can
have
minister
or
CR
and
still
go
to
config,
which
define
your
different
behaviors
there
and
I
said
previously
that
this
will
define
the
components
and
feature
toggles.
This
pull
request
is
still
under
discussion
and
there
is
no
current
strict
implementation
for
that
one.
C
D
D
Now,
from
now
on,
after
each
product
planning,
the
set
of
Zen
hub
epics
will
be
created.
It
means
that
you
can
go
at
any
point
of
time
to
design
humbert
use.
The
label
called
epic
and
see
overall,
I
would
say
status
of
my
stone
or
release
for
the
current
time,
just
small
change,
but
it
will
actually
help
to
track
the
overall
progress
right
of
the
product.
So
this
is
the
first
part
the.
D
D
So
this
is
just
the
simple
Zen
board
with,
as
you
can
see
here,
a
lab
label
called
epic.
It's
set
up,
so
there
is
a
set
of
epics
on
the
board,
which
is
stood
in
progress.
That's
at
Asura
right.
There
is
no
details.
If
you
want
to
details,
you
have
to
change
filters,
but
this
is
like
the
overall
overall
board
right
yep.
So
this
is
the
first
point.
The
second
point
is:
can
we
second
point
is
about
trash?
D
Yes,
so
from
the
community
perspective
is
also
important
because
from
now
on
at
the
issue,
trash
will
be
done
on
daily
basis
by
the
teams
what
it
means
it
means,
for
example,
if
you
can,
if
you
will
erase
an
issue
for
us,
for
example,
in
camera,
posit
or
E,
we
should
be
aware
of
that
issue
in
the
same
day
or
day
after
because
we
are
doing
this
trash
thing
on
daily
basis
right.
But
please
bear
in
mind
that
we
are
only
humans
right,
so
we
can
make
some
mistakes.