<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 3/21/11 11:28 AM, Camille Bissuel wrote:
<blockquote cite="mid:4D872849.5030302@yagraph.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi all,<br>
<br>
I'm certainly not an authority in this field, but willing to
change our tools (SVN, mercurial, Drupal or whatever), a few weeks
before the event is not really a bright idea in my point of view.<br>
<br>
We already spent weeks doing the actual LGM2011 website, and even
if it's not prefect, it do the job. In the best scenario , trying
to restart everything again now will only conduct to a beta
quality website two weeks before the event.<br>
<br>
Furthermore, using a revision control system is not ideal because
it increase complexity, and forbid quick testing in the production
environment (it's easy to make a typo mistake in a javascript file
for example). Drupal is a good CMS, but we will need time to set
it up fully, so it will be wiser to use it for next year.<br>
<br>
Said simply, as already said by a number fo people here, let's
focus on next tasks instead of re-doing the same ones again and
again.<br>
<br>
Cheers,<br>
Camille<br>
<br>
</blockquote>
<br>
Well said.. don't change now.. develop what is there and make it
right for 2011. You all liked it for 2010, 9 weeks is no time at
all.<br>
<br>
Having said that though, you should not be doing testing in
production, you should have a test environment for that! Using any
revision control system could simply allow a checkout of a release
version into prod. Adding a CMS on top complicates that, although a
database dump from test to prod and a checkout should generally
cover it.<br>
<br>
Craig<br>
</body>
</html>