Let's see, till v4 is released, connecting with v4 will leave to deferral for 24 hours... So actually not making v4 available for download before v4 is usable doesn't seems so bad for me.
Also, since "everyone" needs to download v4 afterwards, it's probably leave to a little breathing-space for the scheduling-server, so not all connects immediately.

> Let's see, till v4 is released, connecting with v4 will leave to deferral for
> 24 hours... So actually not making v4 available for download before v4 is
> usable doesn't seems so bad for me.
> Also, since "everyone" needs to download v4 afterwards, it's probably leave to
> a little breathing-space for the scheduling-server, so not all connects
> immediately.

Again, not everybody participates in other projects. Some might been participating
in SETI since day one and don't even know CPDN exist.
If it's for a breathing space that the version 4 is not on their web
site, WHY NOT SAY IT ? and tell us where we should go to download it ?

Note that in your message you PROBABLY. Sounds like GUESS to me and there
is just too much of this in this project.



-.-. --.- -.. -..- . - .-.-. -.- --... ...--

>
> Again, not everybody participates in other projects. Some might been
> participating
> in SETI since day one and don't even know CPDN exist.
> If it's for a breathing space that the version 4 is not on their web
> site, WHY NOT SAY IT ? and tell us where we should go to download it ?
>
>

Uhm, if it's not available due to giving the scheduler breathing-space then up again, I can't see any intelligent reason to tell of another place to download it from... Seeing all the messages of people constantly clicking "retry" and effectually making the exponential backoff of little help, do you really think many wouldn't try this if the client was released beforehand.

Another reason can be that they'll planning to release a newer version than available in CPDN, and was fixing a bug last day but let the client run overnight to see if the bug is really fixed...

Oh, a little re-wording in my last message to remove the "guessing"...
Since "all" must download the client after release, this will give the scheduling-server some breathing-space since downloading & installing the client will take many hours... better now?

> > You can get 4.05 from here
> >
> > http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download.php
>
> Thanks. I know I could get it from there. I just wanted to pointed
> out how rediculous it is. Is it normal that we have to go on another
> project web site to get the SETI updates ? Surely not !
> Why is it that they do everything wrong ? I don't know who is the
> big boss behind all this but he want CPDN to take over SETI and
> that's clear as water.

Actually I see it as a boinc upgrade ;-)

Anyway, the boinc web-site seems like a more logical place to download the client than the projects web-sites...


S@h Berkeley's Staff Friends Club © member

> > > You can get 4.05 from here
> > >
> > > http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download.php
> >
> > Thanks. I know I could get it from there. I just wanted to pointed
> > out how rediculous it is. Is it normal that we have to go on another
> > project web site to get the SETI updates ? Surely not !
> > Why is it that they do everything wrong ? I don't know who is the
> > big boss behind all this but he want CPDN to take over SETI and
> > that's clear as water.
>
> Actually I see it as a boinc upgrade ;-)
>
> Anyway, the boinc web-site seems like a more logical place to download the
> client than the projects web-sites...
>

Yes but there's nothing there either.

-.-. --.- -.. -..- . - .-.-. -.- --... ...--

> Oh, a little re-wording in my last message to remove the "guessing"...
> Since "all" must download the client after release, this will give the
> scheduling-server some breathing-space since downloading & installing the
> client will take many hours... better now?

OK so you think it will be better when 60000 thousands computer try to download
the new boinc at the same time. OK I see. Well I would came up with something
better. Something with a MINIMUM of preparations.

A message on the board one week before the update with CLEAR informations

-When it will happen (day and time)
-how to proceed
-compatibility issue (ver3-ver4)
-the reasons for this upgrade
-what is new in this version
-where to download it
-When to install it
-etc...

This is called professional management of a project. Period.
Look at the mess we're in now. Read the posts. This has not
been properly managed and some still have units to reports
but the scheduler is off. If you were chief of a technical
department would you make crucials update on a Friday ?
I can't wait to see if SETI will work this weekend. But it's
OK CPDN WILL...............................................

I am sorry but is it that hard to understand ?

-.-. --.- -.. -..- . - .-.-. -.- --... ...--

>
> OK so you think it will be better when 60000 thousands computer try to
> download
> the new boinc at the same time. OK I see. Well I would came up with something
> better. Something with a MINIMUM of preparations.

The BOINC core client must manually be downloaded and installed.

>
> A message on the board one week before the update with CLEAR informations
>

V4.05 wasn't built before 25. August, earlier versions too buggy...

> -When it will happen (day and time)

The current client is BETA, M1, v3.20... It's not unexpected beta-releases doesn't follow the rules. BTW, I didn't see any exact date then beta2 of XP-64 was to be released either. ;)

> -how to proceed

See link on download-page on how to install BOINC...

> -compatibility issue (ver3-ver4)

Read the update on the home-page before the upgrade was released...

> -the reasons for this upgrade

To upgrade the current beta-version to a later version...
Also to make it compatible with CPDN.

> -what is new in this version

Look at the main BOINC-pages, CVS.

> -where to download it

From the download-page, then the system is ready for v4.

> -When to install it

After the servers is upgraded to v4.
Oh, installing earlier isn't a problem, but you'll only successfully connect once a day till the servers are upgraded, remember the backoffs is there for a reason.
But seeing all the posts about users constantly hitting "retry", maybe it isn't so bad an idea to remove this option by not making the file available for download before the servers are upgraded...



If any problems, read the transition-page, especially the lines "If you have problems with the new version, you can uninstall it and reinstall the old 'Classic' version of SETI@home."
And "Once SETI@home/BOINC is running smoothly"... atleast my interpretation of this line is that some problems is expected... but it wouldn't be the 1st time, and not the last, is mis-interpreting something. :)

> > -where to download it
>
> Maybe, just maybe, from "Participate in SETI@home"...
>

Your snide remarks are not very helpful. Click on the "Participate in SETI@home" link and follow the download link . . . surprise, it says that is for version 3.20. Then, when you try to go to that link, it won't even load the page. The rest of your response is, at best, your opinion.

Petit Soleil is interested (as am I) in information from some official source, not unofficial and offen incorrect guesswork.

> After the servers is upgraded to v4.
> Oh, installing earlier isn't a problem, but you'll only successfully connect
> once a day till the servers are upgraded, remember the backoffs is there for a
> reason.
> But seeing all the posts about users constantly hitting "retry", maybe it
> isn't so bad an idea to remove this option by not making the file available
> for download before the servers are upgraded...
>
>
> If any problems, read the transition-page, especially the lines "If you have
> problems with the new version, you can uninstall it and reinstall the old
> 'Classic' version of SETI@home."
> And "Once SETI@home/BOINC is running smoothly"... atleast my interpretation of
> this line is that some problems is expected... but it wouldn't be the 1st
> time, and not the last, is mis-interpreting something. :)


OK I give up. You seem to know everything about this project.
I am happy for you. If all this is known by you it must be known
by the dev team. If you can post all the details why they can't ?

Does it mean that because you know the answers one should not be informed.
Not everyones has the chances to be so well informed as you are.
You probably reads all the threads at CPDN, PREDICTOR, BOINC what ever,
but I don't. My grand mother doesn't either. She would like to participate
in the project but it's too complicated for her.....

The BOINC core client must manually be downloaded and installed.
V4.05 wasn't built before 25. August, earlier versions too buggy.
The current client is BETA, M1, v3.20... It's not unexpected beta-releases.
and there is just too many places to go to get the informations.

I still stick with my idea that it would have been better for
EVERYONE if they had prepared this transition in a professional
way. You know what I am trying to say but you're acting like if
you don't. That's it for me now. I don't intend to continue posting
on this thread.

Regards
Marc


-.-. --.- -.. -..- . - .-.-. -.- --... ...--

Hi everybody!

After reading all your posts and the messages at the front page of the project I can´t understand why the 3 projects that today are using BOINC client to run, need different (and incompatible the one with each other) versions of that client. I mean: is it too difficult to co-ordinate the developing of each project to avoid this incompatibility problems? It's so disgusting attaching to a new project and stop collaborating with other projects due to incompatibility between different versions!

See ya!