Nightly Build or CVS?

What I do:
Backup my database.
Download all the files to an archive folder on my PC.
Upload all the new files, saying yes to ‘Overwrite existing’.
Run the upgrade.php.
Then get the index.php back to how I like it.
Done it several times now without a hitch. I’m using the 1/3/04 nightly.
Have fun!

why download teh files everytime u upload a new version!
just rename the old folder and upload the new files. add the old config file and u are good to go!
and if anything mess up, u have ur old installation already in place! rename the old folder back ??

Doh!!
Why did I not think of that ………?
Ta!

ask the guy who is always short on bandwidth on his package ??

Sushubh, are you saying that if I keep the existing wp-config.php it’s not necessary to run upgrade.php?
Podz, I see three new nightlies since March 1, is there a reason you’ve chosen to not use any of them?

No, you’ll still have to run upgrade.php since you’re making a jump from 1.0.1 to 1.1/1.2.
The CVS has always worked great for me…I’ve used it consistently since I figured out how to get it. The issue I’m having with the latest CVS (030904) is with permalinks; mod_rewrite doesn’t like the rules being generated. Otherwise, 1.2-alpha’s been doing great.

my experience is that its better to always run the upgrade file!
it never harms in anyways…

@harpshot … no reason whatsoever ??
To be honest, I’d done a run of upgrades and just stopped there. I have no doubt whatsoever I’ll keep upgrading.
I’d also got plans to really make my blog look good before upgrading again, and while the HTML and CSS hold no fear for me, I’ve the creative abilities of a grated carrot. So it’ll always look crap anyway !

The variety of approaches that arrive at the same end is both interesting and reassuring. I downloaded the March 8 nightly and unzipped into a directory. I backed up my blog directory. Then I used a sync program to copy all “newer” files from the March 8 directory to the blog directory. This left the “customized” files like css, index.php, config and some others intact. I did *not* run install.php or upgrade.php. The blog works fine. In fact, I can’t tell any difference, which seems ideal. Of course, this was on my PC localhost, as I didn’t want to risk the real site without a rehearsal. So I reckon I’ll double-check the files that *weren’t* updated, to be safe, and upload to web server. Unless anybody can say whether running upgrade.php does something else that’s important. ???

Running upgrade creates at least one new database table, for starters.

Um, yes. Disregard my previous post. There was an excellent reason I couldn’t tell the difference. Ah, er, please don’t ask. Is there a smiley with dunce cap?

OK, better now. In case it hasn’t been mentioned before, turn off firewall to run upgrade.php on localhost PC. Also, anybody run into this: Missing argument 2 for zeroise() in /wp-includes/functions-formatting.php on line 241? It echos on page loaded from archive link (i.e. index.php?m=200402), instead of the name of month (or else it’s covering it up but I don’t think so). I’ve looked at the function but as mentioned before I don’t know enough PHP to debug it. It wasn’t there before upgrade. Is now. I haven’t searched forum yet but thought I’d mention it while here ’cause you three seem pretty clued in.
Thanks for earlier guidance. It helped. Sleep now. Search tomorrow…
HarpShot

what does CVS mean?
bgr

“Concurrent Versions System”. It’s an app that allows developers to keep track of changes/modifications/additions/etc to a given software project.
‘Using the CVS version’ refers to the practice of downloading the latest files in a project. Translation: You have the latest stuff, but sometimes also the latest bugs. ?? Not recommended for production sites.

dafynition of Upgrade: Take old bugs out, put new ones in.
TG