similar to: [6.0.0 Release] Scheduling the release

FWIW, I don't have really strong objections, but I'm honestly not a fan. The reason is mostly that I think it is very late to make the change and likely to mean most people are on holiday when the branch occurs. I somewhat anticipate significantly more cherrypicks as a consequence. I'd love for Apple's releases to by sync'd with the open source ones, but I don't understand

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

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

Hi Hans, Looks ok here. I've uploaded the binaries. SHA256(clang+llvm-6.0.0-mipsel-linux-gnu.tar.xz)= 5ff062f4838ac51a3500383faeb0731440f1c4473bf892258314a49cbaa66e61 SHA256(clang+llvm-6.0.0-mips-linux-gnu.tar.xz)= 39820007ef6b2e3a4d05ec15feb477ce6e4e6e90180d00326e6ab9982ed8fe82 SHA256(clang+llvm-6.0.0-x86_64-linux-gnu-debian8.tar.xz)=

Dear testers, Start your engines; 6.0.0-rc1 was just tagged. I know there are still open blockers and it's early in the process in a way, but I'd like to find out where we are. Please run the test script, let me know the results, and upload binaries. Thanks, Hans

According to the schedule (e.g. on the right on llvm.org), we should have tagged the release by now, but we haven't, so we're officially behind schedule. I'm still optimistic that we can wrap this up pretty soon, though. This is what's blocking us: - PR26509: Crash in InnerLoopVectorizer::vectorizeLoop() I'm waiting to hear what Cong comes up with, otherwise we can revert

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'

Hi, No major issues seen so far for mips. Binaries uploaded. SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)= 54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d61 SHA256(clang+llvm-6.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)=

Dear testers, Release Candidate 2 has just been tagged [1]. Please build, test, and upload to the sftp. I know there are still outstanding issues from RC1, but there have been a lot of merges going into the branch and I think it's time for another round of RC testing. This RC comes a little behind schedule, sorry about that, but I'm still optimistic about hitting the target of releasing

Hello everyone, The release branch for LLVM 9 and its sub-projects was just created from trunk at r366426, and the trunk version was subsequently bumped to 10.0.0. Release blockers are tracked by https://llvm.org/PR42474 Please mark any bugs, old or new, that need to be fixed before the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and

On Mon, Dec 5, 2016 at 12:02 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 5 December 2016 at 19:56, Hans Wennborg <hans at chromium.org> wrote: >> I'd like to avoid 4.1 because of the potential for confusion about >> whether it's a major release (as it would have been under the old >> scheme) or a patch release. > > But if the versioning

Breaking this out into a separate thread since it's kind of a separate issue, and to make sure people see it. If you have opinions on this, please chime in. I'd like to collect as many arguments here as possible to make a good decision. The main contestants are 4.0 and 3.10, and I've seen folks being equally surprised by both. Brain-dump so far: - After LLVM 1.9 came 2.0, and after

Dear everyone, The release branch was recently created from trunk at r308441 and the trunk version was subsequently incremented to 6.0.0. Release blockers are tracked by https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help out with the release by notifying me of any bugs, commits, or other

Hello testers, 4.0.0-rc2 was just tagged from the branch at r294535. There are still open relase blocking bugs and merge requests, so this will not be the last release candidate, but we've had a lot of merges since the last one, and I'd like to see what the testing looks like. The test-release.sh script was updated to also include lld. Make sure you're using the latest version of

On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start

On Fri, Aug 3, 2018 at 3:38 PM, <paul.robinson at sony.com> wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit <update to llvm/docs/ReleaseNotes.rst> > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git

On Mon, Jun 13, 2016 at 5:03 PM Hal Finkel via lldb-dev < lldb-dev at lists.llvm.org> wrote: > ----- Original Message ----- > > From: "Hans Wennborg via cfe-dev" <cfe-dev at lists.llvm.org> > > To: "llvm-dev" <llvm-dev at lists.llvm.org>, "cfe-dev" < > cfe-dev at lists.llvm.org>, "LLDB Dev" <lldb-dev at

On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg