<div dir="ltr">i Don't know if others have raised this issue, but I'm seeing *a lot* of llvm-dev emails and cfe emails landing in my spam folder in gmail. Are other people having this problem?<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, May 12, 2014 at 11:57 AM, Tom Stellard <span dir="ltr"><<a href="mailto:tom@stellard.net" target="_blank">tom@stellard.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I would like to begin the 3.4.2 release process for LLVM. There have<br>
been two issues identified in 3.4.1, which there is interest in having<br>
fixed in a 3.4.x release:<br>
<br>
1. Build failure with gcc 4.9 (This is not a regression, 3.4 also fails<br>
to build with gcc 4.9).<br>
<br>
2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4<br>
<a href="http://libLLVM-3.4.1.so" target="_blank">libLLVM-3.4.1.so</a><br>
<br>
I will also accept any other bug-fixes that people want to submit as<br>
long as they conform to the rules of stable releases:<br>
<a href="http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules" target="_blank">http://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules</a><br>
<br>
In order to get these fixes out quickly, we will have a very short period<br>
for nominating bug-fixes, followed by our usually stable release testing phase.<br>
<br>
Here is an approximate schedule:<br>
<br>
Monday, May 12 to Thursday, May 15: Nominate bug-fixes for the 3.4 branch.<br>
Friday, May 16 to Friday, May 23: Testing Phase I<br>
Monday, May 25: Release or Phase II of testing if necessary.<br>
<br>
If you are interested in helping with release qualification testing<br>
of 3.4.2, send me an email with the target, operating system and host<br>
compiler you can test with. Since we have fixes specifically for gcc<br>
4.9 in this release we need some testers who can test with gcc 4.9.<br>
<br>
Besides release qualification, it will be helpful to have people building<br>
the 3.4 branch with gcc 4.9 and looking for potential issues. This can be<br>
done before the testing phase once the gcc 4.9 fixes have landed.<br>
<br>
I have a busy schedule in the next month, so I would like to have one or more<br>
backup up release managers, in case I am unable to make this release in a timely<br>
manner. If you are interested in this, let me know.<br>
<br>
Thanks,<br>
Tom<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote></div><br></div></div>