Hi, In general principle I would agree with you - everything we release should be of the top quality and there should never be a known regression.
But then there is the context: we are now 4 months behind the original release date for 1.19. Anyone relying on our new apis or enhancements cannot release until we do and so I think that puts pressure up over time to release. Additionally we are able to get people to focus on bug fixing and testing for a couple of weeks to a month but at this point (according to my observations) most people are fed up of that and drifting off. Not only does that mean that the release slips further but, as we are in feature freeze, it means that valuable contributions are also falling behind and potentially being missed. In my understanding what is being added to efl now is making it far easier to start using as a developer and so the argument of core apps (as showcases) has some merit? Thanks for your thoughts, Andy On Sun, 9 Apr 2017 at 00:20, Christophe Sadoine <ch...@indefini.org> 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. > > > ------------------------------------------------------------------------------ > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- http://andywilliams.me http://ajwillia.ms ------------------------------------------------------------------------------ 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
