<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 12, 2010, at 8:25 AM, David Greene wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote:<br><blockquote type="cite">Just a reminder that the 2.7 code freeze is on Feb 21st.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">All major changes should be committed approximately 1 week before the code<br></blockquote><blockquote type="cite">freeze to ensure adequate testing. Please do your part to keep the tree<br></blockquote><blockquote type="cite">stable in the days leading up to the code freeze.<br></blockquote><br>Since the metadata stuff just settled recently, I like to ask for some time to<br>get the non-temporal stuff in. This is really critical for our work here and <br>it would be nice to get this into 2.7.</div></blockquote><br></div><div>Generally, I favor timed releases over feature releases, but... the Clang team would also like a little more time to prepare for the 2.7 release. Specifically, we propose to push back by 2 weeks, with the revised schedule being:</div><div><br></div><div><div><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 12px; ">3/7 - Code Freeze (9PM PST)</span></font></div><div>3/13 - <span class="Apple-style-span" style="font-size: 12px; ">Pre-release1 released & community testing begins</span></div><div>3/20 - <span class="Apple-style-span" style="font-size: 12px; ">Pre-release1 testing ends</span></div><div>3/27 - <span class="Apple-style-span" style="font-size: 12px; ">Pre-release2 released & community testing begins </span></div><div>4/3 - <span class="Apple-style-span" style="font-size: 12px; ">Pre-release2 testing ends</span></div><div>4/5 - <span class="Apple-style-span" style="font-size: 12px; ">Release</span></div><div><br></div><div>Why now?</div><div><br></div><div>Clang's C++ support is at an important transitional point: we can self-host a Debug build, and are starting to build significant C++ open source projects such as CMake, Firefox, Qt, and even parts of Boost. LLVM 2.7 is the perfect opportunity to enable Clang C++ support by default and announce to the open-source community that we now have something worth looking at. However, we have several known semantic analysis bugs and miscompiles that prevent self-hosting with optimization enabled, cause Firefox to crash on startup, etc. To advertise Clang C++ widely as part of 2.7 while these bugs remain would be embarrassing, but we feel that we can address the major problems with only a two-week slip in the schedule. </div><div><br></div><div>Clang C++ only gets one big coming-out party (ever); a little more time will make a big difference.</div><div><br></div></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div></body></html>