Since there is nowhere feedback to be found for this build, I give some here.

BOINC 7.0.26 works all fine for me; well, with its small and useful changes (from 7.0.25) it should do so ;)

IMHO you should set this build as the "Recommended version". Even more, since it does solve some problems as can be seen here.


Greetings
:)

Since there is nowhere feedback to be found for this build, I give some here.

BOINC 7.0.26 works all fine for me; well, with its small and useful changes (from 7.0.25) it should do so ;)

IMHO you should set this build as the "Recommended version". Even more, since it does solve some problems as can be seen here.


Greetings
:)

There are other bugs that have surfaced and the devs are working on a 7.0.27

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Since there is nowhere feedback to be found for this build, I give some here.

BOINC 7.0.26 works all fine for me; well, with its small and useful changes (from 7.0.25) it should do so ;)

IMHO you should set this build as the "Recommended version". Even more, since it does solve some problems as can be seen here.

Greetings
:)

There are other bugs that have surfaced and the devs are working on a 7.0.27

Interesting philosophical debate. In a situation where the "receommended" version has bugs which are complete show-stoppers for some projects, is it better to wait and promote the bug-free version, or to promote an interim "not quite so bad" version.

Hint: if we waited for bugs like [trac]#336[/trac] - described as 'critical' by the lead developer, when he reported it five years ago - to be fixed, we would still be in a pre-beta testing phase.

So why wait now?

So why wait now?

I asked for 7.0.26 to be promoted several days ago, but will probably not get an answer on that until after the weekend. It seems the developers are taking their weekends off this year. ;-)

---

So why wait now?

I asked for 7.0.26 to be promoted several days ago, but will probably not get an answer on that until after the weekend. It seems the developers are taking their weekends off this year. ;-)

Thanks Ageless
:)

There are other bugs that have surfaced and the devs are working on a 7.0.27

Interesting philosophical debate. In a situation where the "receommended" version has bugs which are complete show-stoppers for some projects, is it better to wait and promote the bug-free version, or to promote an interim "not quite so bad" version.

Hint: if we waited for bugs like [trac]#336[/trac] - described as 'critical' by the lead developer, when he reported it five years ago - to be fixed, we would still be in a pre-beta testing phase.

So why wait now?

I'm not speaking on behalf of the devs but if we were able to recruit a greater number of alpha testers then we could probably have recommended releases that were "stable" and relatively bug free avoiding this situation - and this is only meant as a comment, not an answer or counter-point to your question :)

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

A 7.0.27 tag has been created in the tree so an official release is getting nearer ;)

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

A 7.0.27 tag has been created in the tree so an official release is getting nearer ;)

The Windows downloads are already accessible, but not yet Linux or macOSX.

A 7.0.27 tag has been created in the tree so an official release is getting nearer ;)

The Windows downloads are already accessible, but not yet Linux or macOSX.

Mac OSX is also up we are still waiting on Linux. (I will be doing the OSX version on Sunday or Monday due to other delays in my life.)

7.0.27 compiles fine on gentoo (stable 64bit) and no noticable hiccups running it so far.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

7.0.27 compiles fine on gentoo (stable 64bit) and no noticable hiccups running it so far.

Same here with 7.0.27 on WinXP SP4 (32 bit). Looks really good :)

7.0.28 is out. I'm waiting @ 7.0.27 until I see some posts on if it is better. I will probably wait until the first week of June as I will be out of town later in the week. I'm also going to cutting back to summertime crunching levels; one half of my CPU cores and only at night.

7.0.28 is out. I'm waiting @ 7.0.27 until I see some posts on if it is better. I will probably wait until the first week of June as I will be out of town later in the week. I'm also going to cutting back to summertime crunching levels; one half of my CPU cores and only at night.

I am crunching on 7.0.28 for weeks now, everything is OK. No problems at all.

@ BOINC Team: How about making 7.0.28 the new default version?