I can confirm that the specific case cited in that ticket is now fixed, but I ran some other tests from azy and they are now failing when they did not used to fail. I've requested some regression testing from another azy user, and I hope to have these results within a day or so.
On a side note, I don't think it's reasonable to say that the behavioral discrepancies here are "legacy" and thus imply that it's a corner case. This is, afaik, the most widely deployed means of using ecore-con, and it is currently used/shipped on thousands of devices. On Sun, Apr 9, 2017 at 7:11 PM Stefan Schmidt <[email protected]> wrote: > Hello. > > On 04/09/2017 10:08 AM, Gustavo Sverzut Barbieri wrote: > > On Fri, Apr 7, 2017 at 9:25 PM, Stefan Schmidt <[email protected]> > wrote: > >> Hello. > >> > >> On 04/07/2017 08:04 PM, Simon Lees wrote: > >>> > >>> > >>> On 04/08/2017 08:23 AM, Andrew Williams wrote: > >>>> Hi, > >>>> > >>>> So it's a month after the revised release date and we've been in beta > for 2 > >>>> months with a freeze on anything but bug fixes. Can we just call it > at this > >>>> stage? There will be a 1.19.1 - what is still blocking us from > release? > >> > >> What is blocking us all the time is that once one blocker is fixed > >> another one springs up. :) > >> > >>>> It's unclear if the recent blockers have been new since 1.18 or if we > just > >>>> want to be better across the board but at this stage I feel like we're > >>>> holding up feature work. > >>>> > >>>> Any other thoughts? I know folk are working hard on stuff but I'd > like to > >>>> get this line drawn as soon as possible. > >>>> > >>>> Cheers, > >>>> Andy > >>>> > >>> > >>> We did get a beta4 Stefan hasn't been on IRC the last couple of days so > >>> maybe he's away atm, that would hold up a release. > >> > >> Traveling but still looking after things, Just not on IRC. > >> > >> What holds up the release from my side right now is: > >> https://phab.enlightenment.org/T5339 > >> > >> I wanted to hear from Gustavo if he can reproduce this. > > > > finally had time to fix it, fortunately wasn't a bug with the new code > > (which I was worried about), rather a bug in the compatibility layer > > (ecore_con_legacy.c) which a particular case azy used but none of our > > examples or tests does, which is to "connect -> send" right away, > > usually we wait on "server,add" event prior to sending data. However, > > if that was allowed before, it must be allowed now as we're not > > supposed to break compatibility! > > Might be worth adding a test case for it to avoid future problems with > it. But nothing to stress you with. Enjoy the time with your new family > member and thanks for finding the time fixing this! > > > it's in GIT, let's hear from discomfitor if it fixed his problem (from > > my testing, yes)... in that case we can release! > > Perfect. I wait for zmike to confirm this and do the release afterwards. > > 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 > ------------------------------------------------------------------------------ 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
