<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Sure that sounds fine.<div><br></div><div>-bw</div><div><br><div style=""><div>On Jul 14, 2014, at 1:46 PM, Tom Stellard <<a href="mailto:tom@stellard.net">tom@stellard.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On Mon, Jul 14, 2014 at 10:59:03AM -0700, Bill Wendling wrote:<br><blockquote type="cite">Hi all,<br><br>I’m sorry for the late announcement. Here’s a tentative schedule for the 3.5 release.<br><br></blockquote><br>Hi Bill,<br><br>I would like to propose a slight change to the release process. Instead<br>of naming the release tag directory RELEASE_XY, it would be better to<br>use RELEASE_XYZ to make it easier to support dot releases in the various<br>release scripts. Here is a documentation patch for the proposed change:<br><a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140616/221946.html">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140616/221946.html</a><br><br>If there are no objections to this, then I will create aliases for the<br>3.4.2 tags using this new naming convention and then update the release<br>scripts. I think we will want to use 3.4.2 as the baseline when we check<br>3.5 for regressions, since in theory it has less bugs than 3.4.0<br><br>-Tom<br><br><br><blockquote type="cite">July 21: Branch for 3.5 release.<br><br>- All features should be near completion. Changes to complete existing features will be accepted until the end of testing phase I. But they should *not* be major (i.e., large) changes. If they are, they may be rejected.<br><br>July 21-27: Testing Phase I.<br><br>- Binaries will be available for general testing.<br><br>July 28-Aug 3: Fix bugs from Testing Phase I.<br><br>- At this point, all features should be complete. Any features which aren’t need to be turned off by default.<br><br>Aug 4-10: Testing Phase II.<br><br>- Only critical bug fixes accepted. Binaries will be available for general testing.<br><br>Aug 11-17: Fix bugs from Testing Phase II.<br><br>- The bugs fixed here are release blockers. Ideally, we won’t need a Testing Phase III.<br><br>Aug 25: 3.5 RELEASE! :-)<br><br>Share and enjoy!<br>-bw<br><br><br>_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a><span class="Apple-converted-space"> </span> <a href="http://llvm.cs.uiuc.edu/">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a></blockquote></div></blockquote></div><br></div></body></html>