On Thu, 9 Aug 2018 11:08:53 +0200 Xavi Artigas said:
> Hi,
>
> The API docs require both language polishing and a technical review for
> missing or unclear info. I generally think it is more efficient to do both
> in one go, so I'd rather do these once you know some C at least.
>
> Putting your
There is still some confusion related to the feature proposal query on
phabricator: in order to appear in the query, the ticket must have the
'efl-1.22' tag as well as EITHER 'major_change' OR 'refactoring'. If it
does not meet both of these requirements (i.e., if (A && (B || C))) then it
will not
Hello,
It seems we are closing in on the final release for 1.21. If we do not
encounter any major issues, then it's probable we will see the release
happen next week.
Given the proximity of the release, and the lack of any alternate proposals
or negative feedback related to the (only) existing pr
This second, and hopefully last, beta release for 1.21 brings a number
of fixes over the first beta release.
The number of known issues shrunk to just a few left overs we are
working on right now. We appreciate any tester of this to let us know
about problems. This goes for packaging, testing with
Hi,
The API docs require both language polishing and a technical review for
missing or unclear info. I generally think it is more efficient to do both
in one go, so I'd rather do these once you know some C at least.
Putting yourself in the place of a user, installing Enlightenment and some
EFL ap
