After you upload your files to the server, login as site admin into the backend of the primary mu blog. If any database changes need to be made they will occur then automatically.
The beta gets updated when they bump the beta version and release it. The svn version will be the freshest version you can get.
Thank you for your fast reply. 
So with SVN is it just a simple case of dropping the desired component or files into mu-plugins folder. Can you just add the individual files or do you have to have the whole component?
Do we need to deactivate the current components first.
What about css and the like. Will we will still need to fiddle with them??
@socialbandit SVN or beta zip is the same procedure. With incremental updates from SVN I know what files were modified. I can’t keep track of them individually. That’d be a nightmare. SVN updates come through files from here, files from there. All over the place. When I’m ready to update I do the whole shebang.
I don’t know how others do it.
No deactivation is needed. I’m usually up at 3am so I do it then. That probably doesn’t make a diff though. It’s not 3am in Moscow.
css changes on updates? I’m not sure what you mean by that.
@burtadsit Thanks for that
Hi all,
Are these instructions still applicable to the latest SVN version of BP.
I downloaded the latest trunk last night and replaced the mu-plugins with the SVN one. I left the themes as they were as the theme works with RC1 components.
However, after replacing all the components with the latest SVN copies i got a blank screen.
A PHP error probably, i shall turn on logging when i get back and have another look.
Just wondered if there was a new way to upgrade now?
Not yet. The reason 1.0 is slightly delayed is so that WPMU can be installed to allow for always-on plugins like BuddyPress to be part of the automatic updater going forward.
For now it’s a manual process, but it won’t always be that way.
ooops
False alarm on my blank page sarga.
It was NOT connected to the bp-components; it was the super cache plugin since i moved directories.
The plugin uses a fixed path!
I only found that out by going through the code echoing a timestamp and exiting code block by block. Finally followed the culprit code to an advanced-cache include in wp-settings.
Oh well!
Looking forward to bp v1 with its auto upgrade.
