<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IVF Release Strategy in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839600#M57569</link>
    <description>Steve,&lt;BR /&gt;&lt;BR /&gt;Thanks.  I appreciate your openness about the release strategy.  I was expecting some fixes, predicted to be in this release by staff on Premier Support, but I guess their projections were overtaken by unforseen events.  It happens.  (And it happens to me and my team on a semi-regular basis.)  So I understand and accept your answer.  I just wanted to confirm that the list of fixes in the release notes was actually intended to be complete.  &lt;BR /&gt;&lt;BR /&gt;Cheers!</description>
    <pubDate>Fri, 05 Aug 2005 08:03:49 GMT</pubDate>
    <dc:creator>ivfuser</dc:creator>
    <dc:date>2005-08-05T08:03:49Z</dc:date>
    <item>
      <title>IVF Release Strategy</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839598#M57567</link>
      <description>Could one of the Intel folk help me out here?  I probably missed this the firts time around.&lt;BR /&gt;&lt;BR /&gt;I've just installed IVF 9.0.020 and am looking forward to running some regressions on which 9.0.019 came up short.  I figured I'd check the release notes first to see what changed between releases.  Is the list of five resolved Q-labeled issues exhuastive for this release?  I could understand if those were the only items released to manufacturing before a rigid monthly ship date.  Is that the case here?&lt;BR /&gt;&lt;BR /&gt;I'm not doubting the importance of these fixes, but it has been my impression that Intel sometimes fixes a lot more in a point-release than is reflected in the release notes.  Is that the case this time?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 04 Aug 2005 13:08:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839598#M57567</guid>
      <dc:creator>ivfuser</dc:creator>
      <dc:date>2005-08-04T13:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: IVF Release Strategy</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839599#M57568</link>
      <description>Normally, there would be many more issues fixed in the monthly update.  Our development process is that each subcomponent team collects and tests their fixes, and then "promotes" them to the global build.  With the number of teams we have working on different parts of the compiler, this has proven to be much more productive than everyone checking changes in to the shared codebase all the time.&lt;BR /&gt;&lt;BR /&gt;Due to non-technical circumstances, the compiler "front end" team was not able to do their promotion in time for the schedule for this update (and the updates are very tightly scheduled with the packaging and validation teams.)  This means that a large group of fixes that normally would have made this update didn't.  The update at the end of August will have a lot more fixes.&lt;BR /&gt;&lt;BR /&gt;If you reported a problem to Intel Premier Support, you should have been told when to expect to see an update with the fix.</description>
      <pubDate>Thu, 04 Aug 2005 21:27:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839599#M57568</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2005-08-04T21:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: IVF Release Strategy</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839600#M57569</link>
      <description>Steve,&lt;BR /&gt;&lt;BR /&gt;Thanks.  I appreciate your openness about the release strategy.  I was expecting some fixes, predicted to be in this release by staff on Premier Support, but I guess their projections were overtaken by unforseen events.  It happens.  (And it happens to me and my team on a semi-regular basis.)  So I understand and accept your answer.  I just wanted to confirm that the list of fixes in the release notes was actually intended to be complete.  &lt;BR /&gt;&lt;BR /&gt;Cheers!</description>
      <pubDate>Fri, 05 Aug 2005 08:03:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839600#M57569</guid>
      <dc:creator>ivfuser</dc:creator>
      <dc:date>2005-08-05T08:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: IVF Release Strategy</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839601#M57570</link>
      <description>I can't promise that the list is complete, but it's likely to be close to complete, at least as far as the compiler itself is concerned.</description>
      <pubDate>Fri, 05 Aug 2005 20:18:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/IVF-Release-Strategy/m-p/839601#M57570</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2005-08-05T20:18:22Z</dc:date>
    </item>
  </channel>
</rss>

