similar to: [7.0.0 Release] One week to the branch

Hello everyone, This is just a quick reminder that the upcoming release branch is scheduled for creation one week from today, on Wednesday 16 January 2019. The full schedule is available under "Upcoming Releases" in the right column at https://llvm.org. Please try to avoid committing disruptive changes just before or after the branch. As the branch is created, the trunk version will

On Fri, Jan 11, 2019 at 6:26 AM Martin Storsjö <martin at martin.st> wrote: > Hi, > > The COFF support in llvm-objcopy is in a pretty half-finished state at the > moment. I had hoped to have it mostly usable for the common scenarios by > the time of the branch (the initial patch was sent at the end of > November), but it's still lacking stripping of sections (while

Hi Martin, On Fri, 3 Aug 2018 at 14:10, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > $ git branch --list > * master > martino By default "git branch" only lists local branches. "git branch -a" will list all of them, including (for me) "remotes/origin/release_70". If you just type "git checkout release_70" git will

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

On Thu, 24 Jan 2019, Hans Wennborg wrote: > On Thu, Jan 24, 2019 at 3:51 AM Martin Storsjö <martin at martin.st> wrote: >> >> FWIW, I've got the main COFF functionality that I had planned on doing >> committed in trunk by now. So at least for my own usecases, it's fully >> functional by now. (And for unsupported options, it clearly errors out.) >>

That's odd... Have the branch created as usual? On Fri, Jan 13, 2017 at 9:28 AM, Hans Wennborg <hans at chromium.org> wrote: > Oh wait, the branch on the git mirror doesn't look right! > > Anton, can you take a look? The first commit on the branch for llvm is: > > ------------------------------------------------------------------------ > r291843 | hans | 2017-01-12

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

On Fri, 3 Aug 2018 at 11:42, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > A few months ago I switched from using SVN for the LLVM project to using the GIT mono-repo, but I am still not particularly good at using GIT. How can I use the GIT command-line interface to select to the exact same set of sources used for the v7.0.0 branch, Do you mean the commit

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

On Tue, 15 Jan 2019, Hans Wennborg wrote: > On Sat, Jan 12, 2019 at 12:49 AM Jordan Rupprecht <rupprecht at google.com> wrote: >> >> >> >> On Fri, Jan 11, 2019 at 6:26 AM Martin Storsjö <martin at martin.st> wrote: >>> >>> Hi, >>> >>> The COFF support in llvm-objcopy is in a pretty half-finished state at the >>>

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

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

Hi all, I would really like to get a patch into 3.6 for libc++. The patch renames template parameters with the names '_A' and '_V' to longer names. '_A' is frequently defined in ctypes.h and that could cause libc++ to not compile. I'm fairly sure the code was added between 3.5 and 3.6 so that would make this a regression. The patch can be found here:

With the new signature file I was able to verify, but there was still a bad signature: "gpg: key 0x0FC3042E345AD05D: 1 bad signature" which I highlighted below. Didn't seem to be a problem, but thought I'd point it out. I'd be glad to do additional tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub

Dear testers, The final version of 7.0.0 has been tagged from the branch at r342370. It is identical to rc3 modulo release notes and docs changes. Please build the final binaries and upload to the sftp. For those following along: this means 7.0.0 is done, but it will take a few days to get all the tarballs ready and published on the web page. I will send the announcement once everything is

Dear testers, 8.0.0-rc1 was just tagged (from the branch at r351980). It took a little longer than planned, but it's looking good. Please run the test script, share your results, and upload binaries. I'll get the source tarballs and docs published as soon as possible, and binaries as they become available. Thanks, Hans

Dear testers, 8.0.0-rc5 was just tagged from the release_80 branch at r355909. This is identical to rc4 with the addition of r355743. Hopefully it is the final release candidate, so please give it a good testing. As usual, please run the test script, share your results, and upload binaries. I'll publish source tarballs and docs as soon as possible, and binaries as they become available.

On 05/02/2015 18:34, Hans Wennborg wrote: > On Tue, Feb 3, 2015 at 11:47 AM, Hans Wennborg <hans at chromium.org> wrote: >> Hello all, >> >> Source and binaries for LLVM 3.6.0-rc2 are now available at >> http://llvm.org/pre-releases/3.6.0/ >> >> Please try them out, run tests, build your favourite projects, and >> *file bugs* about anything that