Hi all,
I think writing unit tests would be good for someone like me whose new
to the code base if it helps to catch issues. My question though is do
we have a tags on phab where senior devs post tickets for tests that
someone like me can grab and start working on?
On 2018-06-28 04:36,
On Wed, 27 Jun 2018 13:14:39 -0400 Mike Blumenkrantz
said:
> I don't think we need to do testing in EFL, we do have unit test coverage
> for these functions and they pass. Given that this has never occurred in
> any other circumstance (and we have testing), this should be considered an
>
On Thu, 28 Jun 2018 11:07:36 +0900 Hermet Park said:
> Additional explanation for the second,
>
> Unit test, TC, and automation tool is good but not enough.
> We need human testers absolutely. They could test apps, detect errors and
> then report it.
> For the progressive sw, this must be a
Additional explanation for the second,
Unit test, TC, and automation tool is good but not enough.
We need human testers absolutely. They could test apps, detect errors and
then report it.
For the progressive sw, this must be a mandatory, not an optional process.
For version release(maybe in the
See the weekly phab report mails which lists ticket/patch counts for high
priority items.
A number of the highest priority tickets will be resolved over the next 24h
as patches continue to land from the review queue. If people continue to
work on the high priority tickets which are tagged with
I don't think we need to do testing in EFL, we do have unit test coverage
for these functions and they pass. Given that this has never occurred in
any other circumstance (and we have testing), this should be considered an
application bug only; I've already filed a ticket for it.
On Wed, Jun 27,
Okay we need to do some testing and make sure changes to eina/ecore/eio
file ops are not the culprit, because if they are... Ephoto, Rage,
Terminology, EFM, many gadgets, etc... are all possible to do the same.
On Wed, Jun 27, 2018, 9:56 AM Xavi Artigas wrote:
> What? I have been working with
What? I have been working with it on my dev machine!
I hope my recent changes to bring it back to life didn't cause this...
Xavi
El lun., 25 jun. 2018 9:06 p. m., Mike Blumenkrantz <
michael.blumenkra...@gmail.com> escribió:
> Hi,
>
> Do not attempt to use Eflete.
>
> I was attempting to
EFLETE JUST REMOVED MY HOME FOLDER.
You can say "Told you so" now.
I was importing an edj file into a project in a folder off my home, it took
a while, then it kicked me to the login screen and after logging back in...
nada.
Xavi
On Tue, 26 Jun 2018 at 05:54, Hermet Park wrote:
> Thankfully,
On Tue, 26 Jun 2018 11:41:29 +0930
Simon Lees wrote:
>
> Last time I tried to use it, it wouldn't build against the current
> stable efl release so I gave up, which is a shame because when it was
> working well it was a really useful tool.
It did not build when I first packaged it, but did in
Good Morning --
I just wanted to get an update on where we are with this and what is still
prioritized to get an alpha out?
Stephen
On Thu, Jun 14, 2018 at 8:19 AM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> Update: this is the query which should now be used for finding high
>
It seems like you have two main points here:
1) The review process for components should require the approval of
"maintainers", or people who are experts in a given area, and not just
anyone with commit access.
I agree with this idea. While it would certainly be nice if everyone could
review
12 matches
Mail list logo
