> As far as tweaking in production goes, its usually better to launch and iterate, than to sit and try to make it perfect before launch.
So tweak on a staging site is my point (and has been all along). If I refresh the page and suddenly the bottom footer is no longer in the center but flush left (with dead white filling the right), that looks sloppy. I'm not saying hold up the launch, I'm saying try your changes on a non-visible site.
To reiterate what I mean here: you should not be running vim on the box hosting www.videolan.org. I watched you do it earlier today.
Commit those changes as a unit, then pull them over to production. Half-baked edits to production should never happen on a public-facing site, especially with $20/mo VPS providers that can spin you up a server in minutes.
> To reiterate what I mean here: you should not be running vim on the box hosting www.videolan.org. I watched you do it earlier today.
Very unlikely. The Website is open source, and the www.v.o pulls the svn every few minutes and recompiles it.
You'll see the website change quite a lot in the next days, because of that...
But the main thing is that you don't like the way we see the website, ever-evolving and not 100%-tested before. I agree, but we don't have the teams to do that.
So tweak on a staging site is my point (and has been all along). If I refresh the page and suddenly the bottom footer is no longer in the center but flush left (with dead white filling the right), that looks sloppy. I'm not saying hold up the launch, I'm saying try your changes on a non-visible site.
To reiterate what I mean here: you should not be running vim on the box hosting www.videolan.org. I watched you do it earlier today.
Commit those changes as a unit, then pull them over to production. Half-baked edits to production should never happen on a public-facing site, especially with $20/mo VPS providers that can spin you up a server in minutes.