<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=NL-BE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You can have a look at coder (<a
href="http://drupal.org/project/coder">http://drupal.org/project/coder</a>) and
deadwood (<a href="http://drupal.org/project/deadwood">http://drupal.org/project/deadwood</a>
and <a href="http://boombatower.com/tools/deadwood">http://boombatower.com/tools/deadwood</a>),
the first one gives you pointers on how to convert, the second one tries to
convert it for you.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If all other modules are available for D6 100 seems reasonable<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> development-bounces@drupal.org
[mailto:development-bounces@drupal.org] <b>On Behalf Of </b>T L<br>
<b>Sent:</b> maandag 18 mei 2009 01:56<br>
<b>To:</b> development@drupal.org<br>
<b>Subject:</b> [development] 5.x to 6.x migration timeline, best practices,
tips<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hello All,<br>
<br>
I've inherited a 5.x (5.05 I think) site with about 20 contributed modules and
one monster custom module (~ 7000 lines), and I'm looking at migrating to 6.x
sometime in the next few months. I've looked over the handbook pages and
done a little bit of googling with some good success. But I haven't found
much info on planning or common pitfalls. <br>
<br>
So I was wondering if anyone had any suggestions on things to look out for or a
generalized timeline? My guess was at least 100 hours to upgrade to 5.18,
migrate to 6.12, test the system, and then adjust the theme and api
calls. Does this seem reasonable at all?<br>
<br>
Any thoughts, suggestions, or redirects to resources would be much appreciated.<br>
<br>
Thanks so much,<br>
Tim<br clear=all>
<br>
-- <br>
<br>
Tim Loudon<br>
t: 781.686.6096<br>
e: <a href="mailto:tloud365@gmail.com" target="_blank">tloud365@gmail.com</a><o:p></o:p></p>
</div>
</body>
</html>