The way I upgrade is create a new installations of RC. I have a script that copies my skins and /config directory over to the new installation. Then I test the new installation and when all is good I copy the new installation over the current working copy of RC.

but then you have to know what rev is last. if there is also trunk.tar.gz then it's always the latest and you don't have to guess how many changes there has been after last dl and whats the number in archive name

__________________
irc://irc.freenode.net:6667/#roundcube

Ok, now we
*have one .tar.gz with the latest revision number as the name
and
*one _latest.tar.gz, which is always the latest RC revision.

Thank you, yllar!

Made a update to the opening to post to include to download source hosted by Tobix (thanks ).

//

Please pay attention that the script from Tobix downloads both branch/trunk versions,
so alway's check what version you need by looking at the trac server !!!

so for example the 460 is the current address book branch and the 459 is the current svn branch am i correct? (in tobixs download list)

at present are all svn patches applied to the addressbook branch aswell?

Youre right, 460 is the branch on the moment, and 459 is the trunk.

No, the branch and trunk are different versions !

so if the branch is a different version, all the important patches that get applied to the svn wont be applied to the branch is that not a bad thing?

Currently there is only one security fix and it is included in both....

Im not sure if you understand my question.

The SVN has continuous bugfixes applied to it all the time which are not in the latest beta or the address book trunk.

So im guessing when the SVN has all its problems sorted it will be the next release but how can the address book one every be released if it will have the bugs which have been/will be fixed in the svn.

Does that make sense?

Makes sense to me, I wondered the same thing....

__________________
Roundcube SVN 1335|PHP 5.2.4|hMailServer 5|Win 2003 SP2|IIS 6