Hello. On 04/09/2017 01:20 AM, Christophe Sadoine wrote: > Hello, > I don't mind about the time of the release but I would like to mention > something :) > About this: > >> If we can't find a core app this affects I agree we should release. > > and this: > >>> What code actually uses this in any of our core applications? will it >>> show up as a bug in e or terminology? if so we should wait if not just >>> fix it for 1.19.1 > > I think "not finding a core app" shouldn't be an argument to be able to > release. > We don't know everyone who is using efl and what api they are using. > They might not be following the list and phab issues. > Some people might try efl and on the next release see his application > broken and give up. > > Again I don't mind about releasing with this bug as a known issue. > I think e core applications shouldn't be the thing that matters when > releasing efl.
Agreed. The problem is more knowing if a non-core app is broken. Without using them or getting reports from their developers it is hard for us to know if something is broken. We got this one solved and confirmed so at least for now we are on the good side (for the problems we know about) :) regards Stefan Schmidt ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
