similar to: 6.0.1 Release: Try to get your merge requests in by Friday

I request this to be included in the 6.0.1 release: https://reviews.llvm.org/rLLD330788 On Wed, May 16, 2018 at 5:12 PM, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > The merge request deadline for 6.0.1 is scheduled for Friday, May > 18, with the -rc2 release schedule for May 25. If you have patches you > want merged please submit your requests

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)

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, 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

Will the PR's marked as blockers of PR36649 be merged in or do we need to do something specific? On Thu, Apr 26, 2018 at 12:28 AM, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I've just tagged the 6.0.1-rc1 release. Testers may begin testing and > uploading > binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to >

Hi, It's about time to start thinking about the 3.8.1 release. Here is a proposed release schedule: May 25 - Deadline to request a change be merged to the 3.8 branch. June 1 - Deadline to merge changes to the 3.8 branch. June 1 - 3.8.1-rc1 June 8 - 3.8.1-rc2 (if necessary) June 15 - 3.8.1 Release If you want a patch included in the 3.8.1 release, send an email to llvm-commits with the

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I would like to propose a few changes to the LLVM release process. The current process is documented here: https://llvm.org/docs/HowToReleaseLLVM.html There are two parts to this proposal. The first is a list of clarifications, which are things we are currently doing that aren't documented. The second is a list of changes which would actually modify how releases are currently managed.

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom

Hi, I've just tagged 3.5.1-rc2, so testing can begin. Remember to use the 3.5 branch of the test-suite. If you have any questions, let me know. -Tom

Hi, I've fixed the version numbering and tagged 5.0.2-rc2. Testers can begin testing. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

I've uploaded clang+llvm-3.5.1-rc2-mips-linux-gnu.tar.xz and clang+llvm-3.5.1-rc2-mipsel-linux-gnu.tar.xz. The latter fails prune.m in 'make check-all' as it did last time but this is because the 'touch -a' command isn't actually changing the access timestamp. I've started the test-suite for both of them. ________________________________________ From: llvmdev-bounces

Hi, I've just tagged 7.0.1-rc3. This will hopefully be the last release candidate. Please test and report results. Thanks, Tom

Hi, I've tagged the 10.0.1-rc2 release, please test the release and report any issues. Thanks, Tom

Hi, The 7.0.1-rc2 release has been tagged and is ready for testing. I forgot to bump the version number to 7.0.1 before I tagged -rc1, which is why we are now on -rc2. Remember, you can continue to submit merge requests up until Nov, 21, so keep testing and submitting fixes. Thanks, Tom

Hi, I've just tagged LLVM 8.0.1-rc3. Testers, please begin testing and report results. -Tom

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

On 03/29/2018 08:09 PM, Tom Stellard via Release-testers wrote: > Hi, > > I've fixed the version numbering and tagged 5.0.2-rc2. Testers can > begin testing. > So far, I've only received 5.0.2-rc2 binaries from 2 testers. I am guessing this is due to the mix up with -rc1 and the fact that we don't normally do X.Y.2 releases. If you would like to test this release

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