<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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:0in;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Courier New";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Courier New";
color:windowtext;}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jason,<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Let me introduce Dave. Dave Wilbur is working with a
customer support group within Autodesk and he and his team are looking into making
hotfixes available to our customers the most efficient way. We are also
concerned that we want these modifications to benefit the entire community and,
as you clearly pointed out, show open-ness. <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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The intent was not to impose Autodesk schedule on the community
and maybe the way it was presented lead you to think that it was the case.
But instead, it was trying to communicate our intent with regards to our current
and upcoming releases. Dave also suggesting interesting changes that will
help better track the version and build of FDO. We actually suggested
that this be communicated to the community exactly to show open-ness.<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As a matter of fact, FDO version 3.3.1 has been released to the
community but no branch created for it. Further work was done in the
interest of MG OS and it is done with the intent that this would become 3.3.2. The
intent of publishing this version under 3.3.2 is what is proposed by Dave in
order to have a recognizable point release for MG OS community. <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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As for the hotfix strategy, it is not different than what FDO
has been following so far. Creating 3.X.X branch to hold hotfixes have
been done in the past. It just has the chance of happening more often
going forward. All Dave is proposing is to have new branches that will
allow the community (and of course Autodesk! :^) ) to make small modification
over a specific release. That’s good news!<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think the community and the FDO PSC is solely responsible for
deciding when to create a point release. As always, Autodesk will suggest
when this should happen and the PSC will decide. <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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The proposal at this point is to publish the build of branches/3.3
(rev 4505) as release 3.3.2 and create branches for 3.3.1 and 3.3.2 (which
doesn’t exist at the moment). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Does the PSC and the FDO communicaty have any objection against
it?<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 style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Robert Fortin<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>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Jason Birch<br>
<b>Sent:</b> Thursday, September 25, 2008 5:29 PM<br>
<b>To:</b> FDO Internals Mail List; fdo-internals@lists.osgeo.org<br>
<b>Subject:</b> RE: [fdo-internals] Creation of FDO 3.3 revision branches to
supportAutodesk hotfixes<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=idOWAReplyText97846>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>David, I have no problem with the technical suggestion of branches
to support hotfixes on point releases, and agree that physical file versions
should match the release number. However, I think that there is a
disconnect here in the amount of communication between Autodesk and the
community on releases. Is there no opportunity to change procedures so
that rather than Autodesk product-specific releases and community
releases, there are just releases?</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>In general I think there needs to be a bit more open-ness, at
least as much as is permitted from a publicly traded company. I
understand that it is hard to live within two communities--one completely
closed and the other entirely public--but there is certainly some room for
improvement. It would be helpful if more of the people who are involved
with FDO within Autodesk took a more active role in the community, or at least
stopped by and introduced themselves :)</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Jason</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> fdo-internals-bounces@lists.osgeo.org on
behalf of David Wilbur<br>
<b>Sent:</b> Thu 2008-09-25 1:25 PM<br>
<b>To:</b> fdo-internals@lists.osgeo.org<br>
<b>Subject:</b> [fdo-internals] Creation of FDO 3.3 revision branches to
supportAutodesk hotfixes</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'>Hello FDO community,</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>In an effort to support hotfix
revisions for versions of FDO released by Autodesk, we will need to create
point revision branches in the SVN vault to match any Autodesk releases. Any
hotfix updates for a release will then be submitted to these new branches.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Here is a list of proposed new
branches and the corresponding Autodesk releases:</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>fdo/branches/3.3.1 AutoCAD Map 3D,
MapGuide, and Topobase 2009 (from SVN revision 3791/3802)<o:p></o:p></p>
<p class=MsoNormal>fdo/branches/3.3.2 Update 1 for AutoCAD
Map 3D, MapGuide, Topobase 2009 and SQL Server Spatial (from SVN revision 4045)<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>By creating SVN branches for
every Autodesk release we can ensure that hotfixes can always be created for
each release.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Note that this strategy does not
preclude the creation and release of any interim build revisions that do not
correspond to Autodesk releases. If a release is created without a
corresponding Autodesk release, we will just increment to the next revision for
the next Autodesk release.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>On a related topic, we are
planning to implement a file versioning scheme to follow this release format.
Currently, all Autodesk releases have been distributed with file versions of
3.0.0.x, when they really should have been numbered according to the
corresponding revision.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Once we adopt this strategy, the
next Autodesk release can start using the proper file numbering. Eg. For Map 3D
2009 Update 2 the files will potentially be versioned 3.3.3.x.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>To simplify the migration of the
FDO build to new version numbers, I would also like to propose that the FDO
vcproj files be changed to use a parameterized input for the version number.
The first 3 digits are currently hard coded in the FDO vcproj file post build
steps. A simplified version configuration could be accomplished by either using
a new build environment variable, changing the post build steps to read the
version number from a vault file, or by using a 'resource file include' scheme
where the version rc resource information is stored in a common shared header
file.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Please respond soon with your
thoughts on these topics, as we need to move forward quickly with a solution
for the building of hotfixes for FDO.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Thank you,</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Dave</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#FF6600'><img width=85 height=20 id="Picture_x0020_1"
src="https://webmail.nanaimo.ca/exchange/jason/Drafts/RE:%20%5bfdo-internals%5d%20Creation%20of%20FDO%203.3%20revision%20branches%20to%20supportAutodesk%20hotfixes.EML/1_multipart/image001.gif"
alt="cid:image001.gif@01C63097.C5E10050"></span><span style='font-size:8.0pt;
font-family:"Arial","sans-serif"'><br>
<b><span style='color:black'>David Wilbur</span></b></span><span
style='font-size:11.0pt;font-family:"Arial","sans-serif"'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:black'>Software Developer</span><span style='font-size:11.0pt;font-family:
"Arial","sans-serif"'><br>
</span><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:black'>Geospatial Business Unit - Customer Response Team</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:black'>Direct 618 </span><span
lang=IT style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>345-0989</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</body>
</html>