similar to: 5.0.1-rc3 has been tagged

Hi, I've tagged the 5.0.1-rc2 release, go ahead and start testing and report your results. -Tom

Hi, I just tagged LLVM 4.0.1-rc3, and it's ready for testing. If all goes well, we will do the final release on Monday. -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

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

On Sat, Dec 9, 2017 at 6:51 AM, Dimitry Andric via Release-testers < release-testers at lists.llvm.org> wrote: > On 8 Dec 2017, at 00:47, Tom Stellard via Release-testers < > release-testers at lists.llvm.org> wrote: > > I've just tagged 5.0.1-rc3, please test and report the results. > > Hopefully, this will be the last RC and the final release will > > be

Dear testers, 5.0.0-rc2 was just tagged. I know we still have a bunch of open release blockers, but there has been a lot of merged patches and I'd like to find out what the status is. Please build, test and upload binaries to the sftp. When uploading, make sure to use the /data/testers-uploads/ directory on the server. Let me know if there are any issues. I'll upload sources, docs and

Hi, Tom, Considering the severity of this bug, I would like to go ahead to push the fix into release_50 branch. The fix has been tested in the trunk and by various people as well and I will also make sure all BPF tests passed before the push. Thanks! Yonghong On Fri, Dec 1, 2017 at 10:18 AM, Y Song <ys114321 at gmail.com> wrote: > Hi, Tom, > > I have a BPF backend bug which is

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

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

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Dear testers, The final version of 3.9.0 was just tagged (from the 3.9 branch at r280312). There were no changes after rc3. This took a little longer than expected, but on the up side that means it's had more time to be tested. Please build the final binaries and upload to the sftp. For others following along: this means 3.9.0 is complete, but it will take a few days to get the tarballs

Dear testers, My list of blockers is empty, and there were no new problems discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. Please build the final binaries and upload to the sftp. For others following along: yes, this means 3.8.0 is complete, but it takes a couple of days to get the source and binary tarballs built. I will send the release announcement when everything's

On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. Built, tested and uploaded: SHA256

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final'

Dear testers, The final version of 6.0.0 has just been tagged from the branch after r326550. It has the same contents as -rc3 modulo release notes and one small x86 fix (r326393). Please build the final binaries and upload to the sftp. For those following along: this means llvm-6.0.0 is complete, but it will take a few days to get all the tarballs ready and published on the web page. I will

On 06/05/2018 10:47 AM, Dimitry Andric wrote: > On 4 Jun 2018, at 18:01, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote: >> >> The 6.0.1-rc2 release has been tagged. Testers may begin testing and >> reporting results. > > Built for FreeBSD 10, tested and uploaded: > > SHA256 (clang+llvm-6.0.1-rc2-amd64-unknown-freebsd10.tar.xz)

Hello testers, RC4 has just been tagged (at r229782 on the branch). RC3 was disqualified due to an infloop that Duncan reported, and fixed in r229421. That, fixes for a few scary X86 bugs, a GCC5 bootstrap problem (PR22625), and parts of PR22589 is included in RC4. Baring any showstoppers, this release candidate will be promoted to release. Please let me know how it looks and upload binaries