A “hot fix” would be safer and faster wouldn’t it?

I tried an app level fix and am just starting to test it on Ralph@home which 
basically skips anything dependent on shared memory if it can’t be 
made/initialized. But I’m not hopeful that it will help as other issues may 
arise from running in dirty slots.

David K



> On Sep 29, 2017, at 4:48 PM, Charlie Fenton <[email protected]> wrote:
> 
> On Sep 29, 2017, at 3:10 PM, David Anderson <[email protected] 
> <mailto:[email protected]>> wrote:
>> At this point master has lots of fixes and nothing obviously destabilizing.
>> Should we go for a 7.10 release rather than 7.8.3?
> 
> Unfortunately, our recent experience has demonstrated that serous bugs are 
> often not obvious. Because of the large number of changes between 7.8.2 and 
> master, I would prefer to see a 7.8.3 with a shorter alpha testing period so 
> we can get these critical bug fixes out, followed by the 7.9 built with all 
> the changes in master for more extensive testing.
> 
> I think there are enough serious bug fixes needed that a 7..8.3 "bug fix" / 
> "hot fix" version is warranted.
> 
> But that is just my opinion.
> 
> Cheers,
> --Charlie
> 
>> On 9/29/2017 7:44 AM, Juha Sointusalo wrote:
>>> Please include also the fix to the non stop account manager contacts. There 
>>> has been a few questions about it as well.
>>> 
>>> -Juha
>>> 
>>> On 29 September 2017 at 10:08, Richard Haselgrove 
>>> <[email protected] <mailto:[email protected]> 
>>> <mailto:[email protected] 
>>> <mailto:[email protected]>>> wrote:
>>> 
>>>   Could you please include your
>>> 
>>>   client: eliminate possible buffer overflow in reporting result errors
>>> 
>>> 
>>>   at the same time? We ran into a big problem with CPDN about 10 days after
>>>   v7.8.2 was released, which demonstrated exactly that problem.
>>> 
>>>       On Friday, 29 September 2017, 3:15, David Anderson 
>>> <[email protected] <mailto:[email protected]>
>>>   <mailto:[email protected] <mailto:[email protected]>>> wrote:
>>> 
>>> 
>>>    I plan to do a 7.8.3 test release when Charlie finishes;
>>>   this will have the slot directory cleanup fix as well.
>>> 
>>>   After that I'll do a 7.9 release based on the current code,
>>>   which has lots of changes and fixes.
>>> 
>>>   -- David
>>> 
>>>   On 9/28/2017 5:50 PM, Charlie Fenton wrote:
>>>> Project graphics apps do not appear in the BOINC screensaver on OS 10.13.
>>>   I'm working on a fix.
>>>> 
>>>> Cheers,
>>>> --Charlie
>>>> 
>>>> On Sep 28, 2017, at 12:36 PM, Georges Vinotte <[email protected] 
>>>> <mailto:[email protected]>
>>>   <mailto:[email protected] <mailto:[email protected]>>> wrote:
>>>>>    Hi Guys,
>>>>> 
>>>>> I tested BM 7.8.2 and 7.6.34 on Mac OS High Sierra (10.13)
>>>>> 
>>>>> No specifics bugs, both are running as well as under Mac OS Sierra 
>>>>> (10.12.6)
>>>>> 
>>>>> Cheers,
>>>>> Georges
>>>>> 
>>>>> 
>>>>>> Le 29 août 2017 à 21:45, David Anderson <[email protected] 
>>>>>> <mailto:[email protected]>
>>>   <mailto:[email protected] <mailto:[email protected]>>> a écrit :
>>>>>> 
>>>>>> A new client is available for testing on Win and Mac.
>>>>>> The changes relative to 7.8.1 are:
>>>>>> - fix slow startup problem on Win
>>>>>> - update translation files.
>>>>>> 
>>>>>> This is a release candidate.
>>>>>> Please report test results soon:
>>>>>> https://boinc.berkeley.edu/alpha/test_form.php 
>>>>>> <https://boinc.berkeley.edu/alpha/test_form.php>
>>>   <https://boinc.berkeley.edu/alpha/test_form.php 
>>> <https://boinc.berkeley.edu/alpha/test_form.php>>
>>>>>> 
>>>>>> Thanks --
>>>>>> 
>>>>>> David
>>>>>> _______________________________________________
>>>>>> boinc_alpha mailing list
>>>>>> [email protected] <mailto:[email protected]> 
>>>>>> <mailto:[email protected] 
>>>>>> <mailto:[email protected]>>
>>>>>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha 
>>>>>> <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
>>>   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha 
>>> <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>>
>>>>>> To unsubscribe, visit the above URL and
>>>>>> (near bottom of page) enter your email address.
>>>>> _______________________________________________
>>>>> boinc_alpha mailing list
>>>>> [email protected] <mailto:[email protected]>
>>>>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>>>   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
>>>>> To unsubscribe, visit the above URL and
>>>>> (near bottom of page) enter your email address.
>>>>> 
>>> 
>>>   _______________________________________________
>>>   boinc_alpha mailing list
>>>   [email protected] <mailto:[email protected]>
>>>   https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>>>   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
>>>   To unsubscribe, visit the above URL and
>>>   (near bottom of page) enter your email address.
>>> 
>>> 
>>>   _______________________________________________
>>>   boinc_alpha mailing list
>>>   [email protected] <mailto:[email protected]>
>>>   https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
>>>   <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha>
>>>   To unsubscribe, visit the above URL and
>>>   (near bottom of page) enter your email address.
>>> 
>>> 
>> 
>> _______________________________________________
>> boinc_dev mailing list
>> [email protected]
>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>> 
> 
> _______________________________________________
> boinc_dev mailing list
> [email protected] <mailto:[email protected]>
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev 
> <https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to