I've tried 4 different Dev versions (4.35, 4.37, 4.38, 4.40) and 4.35 seemed to work perfectly fine. I'm wondering if there's a chance that the Stable version will be changed up from 4.25 anytime soon? I'm tired of extremely buggy software that makes me collect 0 credit for days at a time, but I'm also tired of the same old software with old functionality.

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

Hi

I´m sorry, but nobody forces anyone to use devlopement versions.
They have to sort things out.
Thats why use at your own risk.
Try the version that runs smoothly on your machines.

greetz and respectful
Mike

---

With each crime and every kindness we birth our future.

Here's the problem:

4.25 is old
4.35 worked perfectly fine until E@H upgraded and now only 4.25 and the very new dev versions work.
4.37 Had the infinite loop problem
4.38 didn't receive WU's from some projects
4.40 didn't work period.
4.41 I have it but am reluctant to install due to some recent reports about NO updating at all.

I'm using 4.35 (which I just re-installed) and we'll see where it goes from there...

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

<blockquote>Here's the problem:

4.25 is old
4.35 worked perfectly fine until E@H upgraded and now only 4.25 and the very new dev versions work.
4.37 Had the infinite loop problem
4.38 didn't receive WU's from some projects
4.40 didn't work period.
4.41 I have it but am reluctant to install due to some recent reports about NO updating at all.

I'm using 4.35 (which I just re-installed) and we'll see where it goes from there...</blockquote>
The development versions are by definition buggy. If they weren't, they would be released as stable.

If you are adverse to bugs, you should not run buggy software.

If you want to help with the next bug-free stable release, then you run the buggy software and report the bugs. That's why "development" software is made available.

---

<blockquote><blockquote>Here's the problem:

4.25 is old
4.35 worked perfectly fine until E@H upgraded and now only 4.25 and the very new dev versions work.
4.37 Had the infinite loop problem
4.38 didn't receive WU's from some projects
4.40 didn't work period.
4.41 I have it but am reluctant to install due to some recent reports about NO updating at all.

I'm using 4.35 (which I just re-installed) and we'll see where it goes from there...</blockquote>
The development versions are by definition buggy. If they weren't, they would be released as stable.

If you are adverse to bugs, you should not run buggy software.

If you want to help with the next bug-free stable release, then you run the buggy software and report the bugs. That's why "development" software is made available.</blockquote>

Hence my question, when will the next stable version come out? I'd like to help with bugs on dev software too, but these bugs are too big for me so I'm sticking w/ 4.35

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

<blockquote><blockquote><blockquote>Here's the problem:

4.25 is old
4.35 worked perfectly fine until E@H upgraded and now only 4.25 and the very new dev versions work.
4.37 Had the infinite loop problem
4.38 didn't receive WU's from some projects
4.40 didn't work period.
4.41 I have it but am reluctant to install due to some recent reports about NO updating at all.

I'm using 4.35 (which I just re-installed) and we'll see where it goes from there...</blockquote>
The development versions are by definition buggy. If they weren't, they would be released as stable.

If you are adverse to bugs, you should not run buggy software.

If you want to help with the next bug-free stable release, then you run the buggy software and report the bugs. That's why "development" software is made available.</blockquote>

Hence my question, when will the next stable version come out? I'd like to help with bugs on dev software too, but these bugs are too big for me so I'm sticking w/ 4.35</blockquote>
Running anything earlier than 4.41 does not help find bugs. There is no active development on 4.35.

So, by running 4.35, you are not contributing to the debugging process at all.

It has been stated that the next stable version will be out when it is ready, among other things, "ready" means "when those running the latest development version stop reporting problems."

I know that's not what you want to hear, but it is the nature of software development.

I'm currently running a development project and test program now. Our test versions all expire on a certain date so that the testers stay on the latest version and the old versions go away forever.

---

<blockquote><blockquote><blockquote><blockquote>Here's the problem:

4.25 is old
4.35 worked perfectly fine until E@H upgraded and now only 4.25 and the very new dev versions work.
4.37 Had the infinite loop problem
4.38 didn't receive WU's from some projects
4.40 didn't work period.
4.41 I have it but am reluctant to install due to some recent reports about NO updating at all.

I'm using 4.35 (which I just re-installed) and we'll see where it goes from there...</blockquote>
The development versions are by definition buggy. If they weren't, they would be released as stable.

If you are adverse to bugs, you should not run buggy software.

If you want to help with the next bug-free stable release, then you run the buggy software and report the bugs. That's why "development" software is made available.</blockquote>

Hence my question, when will the next stable version come out? I'd like to help with bugs on dev software too, but these bugs are too big for me so I'm sticking w/ 4.35</blockquote>
Running anything earlier than 4.41 does not help find bugs. There is no active development on 4.35.

So, by running 4.35, you are not contributing to the debugging process at all.

It has been stated that the next stable version will be out when it is ready, among other things, "ready" means "when those running the latest development version stop reporting problems."

I know that's not what you want to hear, but it is the nature of software development.

I'm currently running a development project and test program now. Our test versions all expire on a certain date so that the testers stay on the latest version and the old versions go away forever.</blockquote>

There may have been a misunderstanding. I wanted to contribute to helping find bugs, but the bugs I found on say, 4.40 (where it didn't work at all) are too much for me. I'd like to stay on the bleeding edge, but in the words of someone else, that's just too bleeding for me. So 4.35 is my fallback version at the moment. Sorry if I was unclear as to my intentions.

---

<a href="http://tinyurl.com/9hemz"><img src="http://www.boincsynergy.com/images/stats/comb-1441.jpg"></img></a>

<blockquote>There may have been a misunderstanding. I wanted to contribute to helping find bugs, but the bugs I found on say, 4.40 (where it didn't work at all) are too much for me. I'd like to stay on the bleeding edge, but in the words of someone else, that's just too bleeding for me. So 4.35 is my fallback version at the moment. Sorry if I was unclear as to my intentions.</blockquote>
That is what I understood.

Let me give you a real world example:

I'm running 4.40, and from what I can see, it works well. You say it is so bad that you had to roll back to an earlier version -- and you won't even try 4.41.

I didn't like 4.39, but the fixes came out in a few days, and it did work well enough that I could put up with it.

If your goal is to help find bugs you need to load 4.41, and try to stay on 4.41 -- and report.

If not, then that's okay, but rolling back to 4.35 doesn't help produce the next stable version.

---