It would have to be after he 22nd as I am currently on honeymoon is that ok for you
Sent from my iPhone > On 14 Jul 2018, at 19:20, Mike Blumenkrantz <[email protected]> > wrote: > > If you have interest in writing tests it's actually very simple, and I > would not expect a new unit test to take more than 1-2 minutes to write and > run. The biggest issue with it at present is that there are no docs for it. > I can try to work with you a bit on this (mentoring test writing and adding > some docs for it) next week if you can be around on IRC, just let me know. > > On Sat, Jul 14, 2018 at 5:02 AM Jonathan Aquilina <[email protected]> > wrote: > >> Where can I begin? >> >> Sent from my iPhone >> >>> On 14 Jul 2018, at 10:25, Carsten Haitzler <[email protected]> wrote: >>> >>> On Sat, 14 Jul 2018 10:00:41 +0300 Jonathan Aquilina < >> [email protected]> >>> said: >>> >>>> Hi Raster with what you said below and other threads I’ve seen with >> people >>>> complaining about lack of unit tests etc wouldn’t it be better to get >> nightly >>>> builds to those that like to be on bleeding edge and help us test and >> report >>>> bugs. Not to mention I think nightly builds are possible as I see a lot >> of >>>> things that get committed to the repos on a daily basis at times. >>> >>> we already have that - jenkins and now travis builds every commit. there >> is no >>> point building daily if you are building every commit already. >>> >>> the issue isn't the builds, it's the tests themselves. having them cover >>> everything in an efficient and sensible way. in fact lowering the >> barrier of >>> entry to making a test... that's the work needed. :) >>> >>>> My take like this is engaging the community and user base more. >>>> >>>> Let me ask you this and it’s more to ponder on. How much of the current >> user >>>> base is on the latest and greatest? >>>> >>>> Sent from my iPhone >>>> >>>>> On 14 Jul 2018, at 08:57, Carsten Haitzler (The Rasterman) >>>>> <[email protected]> wrote: >>>>> >>>>> On Fri, 13 Jul 2018 18:51:30 +0300 Jonathan Aquilina >>>>> <[email protected]> said: >>>>> >>>>>> I think it was me not being clear I think what I’m thinking is >> nightly tar >>>>>> balls and if need be I’m willing to work on pre packaged binaries for >>>>>> nightly builds >>>>> >>>>> TBH fixes don't move into a stable branch fast enough to justify >> nightlies. >>>>> they go in over time maybe every few days or weeks then every now and >> again >>>>> a point release goes out with them after a "does it compile and pass >> tests" >>>>> check. these releases are incredibly easy and simple and can be >> automated, >>>>> but no point having them nightly - just a "we have enough fixes now - >> push >>>>> one out" time point. >>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 13 Jul 2018, at 18:46, Stefan Schmidt <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Hello. >>>>>>> >>>>>>>> On 13.07.2018 11:27, Jonathan Aquilina wrote: >>>>>>>> I was even thinking weekly point releases to get any new code or bug >>>>>>>> fixes out for early testing. >>>>>>> >>>>>>> Hmm, not sure I get you here. What I talk about are stable updates >> which >>>>>>> would only contain fixes. No new code and definitely not used for >>>>>>> testing at the users systems. These should only ship with verified >> fixes. >>>>>>> >>>>>>> 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 >>>>> >>>>> >>>>> -- >>>>> ------------- Codito, ergo sum - "I code, therefore I am" >> -------------- >>>>> Carsten Haitzler - [email protected] >>>>> >>>> >>> >>> >>> -- >>> ------------- Codito, ergo sum - "I code, therefore I am" -------------- >>> Carsten Haitzler - [email protected] >>> >> >> >> >> ------------------------------------------------------------------------------ >> 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 ------------------------------------------------------------------------------ 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
