Two more days is OK. But please - this must be the Dead line!
Every next Error can be correct in the SVN and everybody can checkout.
The RC3 is only a name for a Snapshot more or less.

Ok - what situation should be tested with your correction ?

Greez BeNe

RC2 -> RC3:
if the update runs without problems;
if the new ./pma/config.inc.php is correct (new version)
if all variables ({VARNAME}) are parsed.

Hi RatS

I updated yesterday to 982 with the new pma-config and it looked good.

what do you mean with "if all variables ({VARNAME}) are parsed." ?

/J

have a look at the pma config and watch, if there are no more {...} entries. /J, have you tested RC2 -> RC3?

no, I did it manually...
and also took the new pma-config and transferred the values manually

So, for testing this: we don't need a real-life RC2 - a fresh install should do the job for this special test...

/J

My update proces is almost done.
like i said earlier my db was not as clean as i thought it would be.
I correct those problems en i havent got any errors on the last update proces.

only the sites are not right away reachable by the browser some how and because of the apt update i think there are some probs now on the ftp-deamon.

But my opinion is that if you have a clean vhcs2 system the update script should work fine.

lets get to the RC4 now..

greets

But the update is not for the one who do not have a vhcs (or a very new vhcs) - it's for the one who run a vhcs system since years...
and this is often not in a good state... :-)

but it's still RC, so we can improve it in the next months...

/J

It's officially now, RC3 is released!
RatS and I are busy with making the packages and updating the website.

Congratulations on my behalf, too. The time to change from vhcs 2.4.8 to omega is coming even closer. Soon I will have to start running migration tests on our test environment

Yeaah, and MS even gets paid, by their beta-tester, about $350 per licens, so who's the fool