similar to: [6.0.0 Release] The release branch is here; trunk is now 7.0.0

Hi Dan, You can commit it to ReleaseNotes.rst on the branch directly, or send me a patch or just some text and I'll do it for you. Thanks, Hans On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote: > Hi Hans, > >> To get a change committed to the branch, first commit it to trunk as >> usual, and then request it to be merged --- ideally by filing a

Hi Hans, > To get a change committed to the branch, first commit it to trunk as > usual, and then request it to be merged --- ideally by filing a > blocker bug on PR35804, or by cc'ing me on the commit email. > What about adding a project to the list of projects ported to LLVM 6.0 in `docs/ReleaseNotes.rst`? I have a project that I've just ported to LLVM 6.0 that I'd like

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

Hi everyone, The release branch for 7.0.0 was created off trunk at r338536 earlier today, and the trunk version was subsequently bumped to 8.0.0. Release blockers are tracked by https://llvm.org/PR38406 Please mark any bugs, old or new, that need to be fixed for the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be

Hello everyone, The release branch for LLVM 11 was created from the trunk at 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was bumped to 12.0.0. Release blockers are tracked by https://llvm.org/PR46725 Please mark any bugs, old or new, that need to be fixed before the release as blocking that bug. Please keep me in the loop via email on any bugs, commits, or other issues that

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

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev: > 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. Hi Hans, I can't build the documentation:

Dear everyone, It has begun: the release branch was recently created from trunk at r291814 and the trunk version was subsequently incremented to 5.0.0 (as per the new versioning scheme [1]). Release blockers are tracked by http://llvm.org/PR31622 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help me out in staying on top of the

Alex, I have built ubuntu binaries for the last couple of releases. I apologize -- I haven't built those new binaries yet, I only have uploaded the SLES ones. I have an ubuntu 14 tarball that I'll upload today. I will work on getting ubuntu 16 or 17 next. The dpkg/APT repos might be a good substitute, though. Hans, apologies -- I should've asked to hold the 7.0.0 release for

Hello everyone, Source, docs and binaries for LLVM-6.0.0-rc2 are now available at http://prereleases.llvm.org/6.0.0/#rc2 I'll add more binaries as they become available. Please report any problems you find, ideally as bugs marked as blockers of http://llvm.org/PR35804 Thanks, Hans

Dear everyone, The release schedule has snuck up on me again, and it's time to wrap up the release. We won't make it to the final tag on the 21st as per the schedule, but I would like to get all outstanding blockers fixed and rc3 tagged by Friday. Hopefully this would be the last rc and we could go to final soon after. If you're involved in a release-blocking bug (see

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

Ubuntu 16: a2a2768b04e1d561e6f9a1a2d525eda7aae18624 clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz On Thu, Sep 20, 2018 at 7:12 PM Brian Cain <brian.cain at gmail.com> wrote: > Uploaded ubuntu 14: > > dec5ca53043c80c1c6e90c0473df84f0182d80af > clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > > On Wed, Sep 19, 2018 at 12:58 PM Brian Cain <brian.cain

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

Hi all, It is my understanding that now WebKit depends on the stack map functionality in production. Also, on the mailing lists we've seen lots of users using in this feature. Can we eliminate the experimental status for 3.5? Off the top of my head, the changes needed are: - A read-through of StackMaps.rst to remove any mention of it being experimental. - Removing mention of it being

Hi Hans, we have uploaded tarballs for ARM and AArch64 targets: a20ea3fe482e754a61ccb37c67456ad1 clang+llvm-6.0.1-aarch64-linux-gnu.tar.xz f37b132c3dfb3b776524980be5af3a76 clang+llvm-6.0.1-armv7a-linux-gnueabihf.tar.xz and 47a9a9bb02d41581e6804b98918188f6 clang+llvm-7.0.0-aarch64-linux-gnu.tar.xz e639d8f5dc58be5cf44d017fd5eefd6c clang+llvm-7.0.0-armv7a-linux-gnueabihf.tar.xz Yvan On Mon,

It's there for me now: $ git fetch origin remote: Counting objects: 811, done. remote: Compressing objects: 100% (561/561), done. remote: Total 562 (delta 462), reused 2 (delta 0) Receiving objects: 100% (562/562), 927.00 KiB | 1.29 MiB/s, done. Resolving deltas: 100% (462/462), completed with 240 local objects. >From http://llvm.org/git/llvm 233ecbde652..16c5e12d3a5 master ->

Hi Developers, This is to clarify which patches may be merged into the 3.5 branch. * All doc changes may go in. In fact, you’re encouraged to update the branch's ReleaseNotes.rst file! :-) * All non-documentation patches should first receive approval from the appropriate code maintainer. (A blanket approval is acceptable for the first phase of testing.) * If your patch fixes a major bug,