similar to: 3.8.1 Release Schedule

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

> Test suite is green but I'm seeing two libc++ test failures when running check-all. What tests are failing? On Fri, Jun 10, 2016 at 5:13 PM, Nikola Smiljanic via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Uploaded Fedora and openSUSE binaries. Test suite is green but I'm seeing > two libc++ test failures when running check-all. I'm pretty sure these were >

Hi, I've tagged 3.8.1-rc1, testers can begin testing. -Tom

Hi, I would like to start a discussion about improvements to the stable release process, but first, here is a proposed schedule for the 4.0.1 release. May 1, 2017 -rc1 May 22, 2017 Deadline for submitting merge request May 29, 2017 Deadline for merging changes. June 3, 2017 -rc2 June 10, 2017 Final Release This is slightly different from previous stable releases in that we are doing an early

Hi, I know a lot of people were busy with the dev-meeting last week, so I've decided to continue to accept stable patches until November 9. I would still like to keep the original schedule of an -rc1 release on November 10, so if there are any newly submitted patches that take more than a few days to get approved, they will probably end up going into llvm 3.7.2. I am currently working

Hi, Here is a proposed release schedule for 3.9.1: Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch Nov 29, 2016: -rc1 Dec 5, 2015: 3.9.1 Release As a reminder, if you would like to request a patch be merged to the 3.9 branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx into the 3.9 branch." and add

Hi, We don't normally do X.Y.2 releases, but there has been some interest in getting a 5.0.2 release out with the Spectre mitigations included, so I am proposing the following schedule for a 5.0.2 release: LLVM 5.0.2 -rc1 Mon Mar 19 -final Mon Mar 26 To keep things easy for testers, 5.0.2 will be for Spectre related fixes only and won't be opened up for general bugs. And here is

Hi, I've tagged 3.8.1-final, so testers can start building the final binaries. -Tom

Hi, Here is the schedule for the 3.6.2 release: June 15: Deadline to propose patches for the 3.6 branch June 15 - June 21: Grace period for reviewing proposed patches and resolving other issues. June 22: 3.6.2 -rc1 June 29: 3.6.2 release Also, I would like to try to try to experiment with using phabricator for proposing patches to the stable branch. This is not a

Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom

Hello Tom, Tom Stellard via llvm-dev <llvm-dev <at> lists.llvm.org> writes: > > Hi, > > I'm working on uploading all the packages now. I've downloaded them files several times from different locations (suspected my webgw might muck with the content) using different clients and the result is the same: $ gpg --verify ~/Downloads/cfe-3.8.1.src.tar.xz.sig

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch.

We just wanted to check to see if they are real bugs first. We will report them if they are not already fixed. Thanks. Del From: Renato Golin [mailto:renato.golin at linaro.org] Sent: Wednesday, July 6, 2016 12:07 AM To: Del Myers <delmyers at microsoft.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] llvm 3.8.1 Release Did you report the bugs? It would be a

I've uploaded clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz and clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz started testing them. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Daniel Sanders > Sent: 16 March 2015 15:36 > To: Tom Stellard; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Reminder 3.5.2

Hi, I tagged 5.0.1-final on Friday. Testers can begin uploading binaries. -Tom

Hi, Just a reminder that testing for 3.5.2 will begin on Monday, Mar 16. If you have any patches you want merged please send an email to the relevant commits list and cc me and the code owner. If you have already done this and are waiting for a response, please ping the thread. As always we need testers, so let me know if you want to help with testing. Thanks, Tom

Hi, I've tagged 6.0.1-rc3, which should be the last rc release. If every thing goes well, 6.0.1-final will be next Thursday. Testers please test 6.0.1-rc3 and upload the results. -Tom

On 01/14/2020 08:59 AM, Russell Gallop wrote: > Hi Tom, Hans, > > I can't see LLVM-9.0.1-win*.exe from Hans on the GitHub release page (https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1). Is this still in progress? > Hans did you upload these? I don't see them on the server. -Tom > Thanks > Russ > > On Thu, 9 Jan 2020 at 20:05, Tom Stellard via

On 01/08/2020 09:24 AM, Brian Cain wrote: > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1 > The binaries have been posted now. > I also checked https://releases.llvm.org/ because I recall some debate or back-and-forth about where the releases should go and/or redirects or links from

Hi, I've created the 3.9.1-final tag no changes from -rc3. Testers can begin uploading binaries now. -Tom