New features :
- Dial-up features now work with all installation types.
- The BOINC Manager can now be controlled using only the keyboard.
- You attach to projects using your own email address and password. Long, random 'account keys' are no longer used.
- BOINC checks for proxy configuration problems when you first attach to a project.
- The file gui_rpc_auth.cfg contains a password that protects the BOINC client from control by other users on the same host. BOINC automatically generates a password if none is found. If you use tools like BOINCView you may need to look it up or change it. If you need to revert from 5.2.x to an earlier version, you must delete gui_rpc_auth.cfg from your BOINC directory.
- Alert boxes now provide feedback when certain errors occur.
- BOINC supports 'Account Management Systems' (to be announced).
* Changes since 5.2.12

mail attention virus :/

@+ moi boinc 5.2.7 :)

---

Yes, no, security, trashing, blah blah blah.

Test the damn client before you put it to release.
Just means putting controls in place to prevent that happening.
Testing it in beta circles before hand.

Not to be argumentative, but even Microsoft hosed a hole bunch of systems when they posted the wrong build. Thousands of people that had XP that set to auto-update had to reinstall their operating systems. Errors are made.

Boinc only has 3 overworked employees and a dozen volunteer developers. Do you really believe that all the 't' are crossed and the 'i' dotted before a release is done.
Rom had to release 3 or 4 updates on Saturday to fix problems encountered when thousands of new people from Seti-Classic switched to Boinc. There was no time to do a whole lot of testing for bug that may have been introduced. We are the Beta testers. This is a fact of life with university shoe string operations.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.12.41
Win 7 i5 GPU Nvidia 470

to be honest what would be nice is an Auto-install and a check to see if update is avalible

it could check each time you recieve or send a work unit to see if there is an upgrade and mabey change the B to a B with flashing ! or such then when you click on it, it could tell you a new version is avalible would you like to download (with a check box or prefrence seting not to check for updates) alot and i do mean ALOT of programs out there do things simalary

personaly i dont spend alot of time at the computers runing boinc to download the latest version but if i could just check to make sure there are no problems (normaly daily) and click the yes upgrade button at the same time i would be happy

oh i also noted that since the 26th there have prettymuch been 1 update a day... is this normal or ???

---

Boinc only has 3 overworked employees and a dozen volunteer developers. Do you really believe that all the 't' are crossed and the 'i' dotted before a release is done.
Rom had to release 3 or 4 updates on Saturday to fix problems encountered when thousands of new people from Seti-Classic switched to Boinc. There was no time to do a whole lot of testing for bug that may have been introduced. We are the Beta testers. This is a fact of life with university shoe string operations.

We've had five or six releases in the last three to four days. Perhaps if the Boinc people got out of the mindset of "We have to fix this bug so we'll release a new version without proper testing that contains a new bug so we have to fix this bug so we'll release a new version without proper testing ...." and actually did some serious beta testing, they might be able to fix this.

The Boinc team is about three times bigger than the team that coded THINK over at FAD. However, Keith apparenly understood the basic rules of software development a lot better. We had a beta test program, and a version was not released to the masses unless it had sucessfully passed beta. We never did have a problem.

Lets face it. If a team of one programmer can pull this off, while also holding down a full time job in research, then a team of three sure as hell can do it.

They just need to rethink theier methodology.

Or what about these guys. Couple of hundred people nowadays. Founded in 1981. Fast forward from there to 1987 when I first crossed paths with them, they were just six people in a warehouse in Emeryville. Corner of 67th and Hollis IIRC. Six people do not become as successful as WRS are today doing things Boinc style. There are better ways.

---

I am also sitting at the fact that my version is working and im not haveing any problems that i know of on it 5.2.6 and 5.2.7 depending on the computer.

also its not the case for me but for some people that are on modems and get charged per the KB sent/recieved im sure they also dont want to update every day or 2.

as for a team fixing and betatesting all the bugs out it is a nice concept and worked well at FaD but this comunity is alot difrent than there and it may not work as well

Boinc also has to be able to run lots of code from lots of difrent people to run so your going to have some strange errors now and then that may not show up as well on testing with other projects

---

The shoestring budget is not the problem, it's always manpower.

I've been looking down the list of todo on boinc development phase.

NewVersion checking.
Done, just do as BoincView does and use thier own version feed
(half way measure to auto-update)

Pretty % bars
BoincView has it

Maybe they should ask the BoincView person to help in the development of the BoincManager...

As for the deamon
Ask the optimisers to help out... lol

There's more people working on the project than there are at many places.

As for rushing BOINC versions out without proper testing that's plain silly, even if it is just to get some more people onto Seti.

BOINC is not a small scale freeware app
There is over half a million hosts (or third million users) using their software.


Maybe it a problem with thier BOINC site and the fact a lot of people will ask questions (like me) in the respective project forum and not go to the boinc forum, or that is a bit scattered around when it comes to information.

---

Team mauisun.org

To all the people who are having a go about countless new versions there is no need to update if your client works properly already, the fixes are for new users who are unable to connect to the server. Stick with your current version and just await BOINC 6.x.x no doubt that is just around the corner

---

Join us in Chat (see the forum) Click the Sig


Join UBT

To all the people who are having a go about countless new versions there is no need to update if your client works properly already, the fixes are for new users who are unable to connect to the server. Stick with your current version and just await BOINC 6.x.x no doubt that is just around the corner

This is my feeling, too. With so many new versions in less than that many days, I am for most of my machines just waiting "to let the dust settle", and then will upgrade once things slow down. My current BOINC versions are working fine! :)

---

Regards,
Bob P.

In all the testing I have watched, including BOINC Beta test, there was never a build that passed internal testing that passed beta testing. And rarely a build that passed beta testing that passed release.

The simple fact of numbers is that there is no way they can test all the potential configurations.

For all of that, most versions released work well for most people.

---

sure thing beta testing and such is a nice concept (working as a software developer myself), but if you compare FaD and Boinc, please keep in mind (you still consider it wrong) that while FaD made changes for their project client, tested them and released them, boinc does features the seti folks never uses and other parties rely on, and if they run into a bug there, trying to fix them fast isn't the worst approach to keep the community happy. (e.g. trickles used in climatepredict).
so boinc would need to set up multiple betas/testprojects, which naturally would not reflect others people complex project apps. its not like they don't test the code at all, just that they miss the manpower for extensive testing.
i agree on the others that stated stay with you version as long as it works and your project does not require something newer unless you enjoy upgrading/a specific new feature (say e.g. when the statistics where introduced).

IMO there is no "right" way to software development, what works for one project can be difficult to do for another.

---

--
Florian
www.domplatz1.de