similar to: [8.0.0 Release] Release schedule

Displaying 20 results from an estimated 20000 matches similar to: "[8.0.0 Release] Release schedule"

2019 Mar 18
4
[8.0.0 Release] The final tag is in
Dear testers, The final version of 8.0.0 was just tagged from the release_80 branch at r356364. It's identical to rc5 except for a few documentation changes. Apologies for being behind schedule. It took longer than planned this time. Please build the final binaries and upload to the sftp. For those following along: this means 8.0.0 is done, but it will take a few days to get all the
2019 Feb 27
5
[8.0.0 Release] rc3 has been tagged
Dear testers, 8.0.0-rc3 was just tagged from the release_80 branch at r355015. We're running a little behind schedule now, but I think we're also close to be able to call this done. Please take a close look at this release candidate. Unless anything bad comes up, this is probably very similar to what the final release will look like. Testers, please run the test script, share your
2019 Mar 12
6
[8.0.0 Release] rc5 has been tagged
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.
2016 Dec 05
10
[4.0 Release] Schedule and call for testers
Dear everyone, There's still plenty of time left, but I'd like to get the schedule set before folks start disappearing for the holidays. Note that this release will also switch us to the new versioning scheme where the major version is incremented for each major release (i.e., when the 4.0 branch is created, trunk will become 5.0). If you'd like to help providing binaries and
2019 Feb 11
2
[Release-testers] [8.0.0 Release] rc2 has been tagged
rc1 did not exhibit this mismatch. A repeat of the rc2 build repeated the mismatch. I diff'd the disassembly between phase 2 and phase 3 and the difference is the same on both builds. The difference follows: # diff x86isel_p{2,3}.s 2c2 < Phase2/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o: file format elf64-x86-64 --- >
2019 Jan 24
14
[8.0.0 Release] rc1 has been tagged
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
2019 Mar 21
4
LLVM 8.0.0 Release
cmake ../llvm/ -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_INSTALL_PREFIX=../install -DLLVM_TARGETS_TO_BUILD="XXX" -DLLVM_ENABLE_PROJECTS='lld;clang;' ________________________________ From: Hans Wennborg <hans at chromium.org> Sent: Thursday, March 21, 2019 2:21 AM To: Josh Sharp Cc: Brian Cain; via llvm-dev Subject: Re: [llvm-dev] LLVM 8.0.0
2017 Dec 06
8
[6.0.0 Release] Scheduling the release
Hello everyone, It's time to start making plans for the 6.0.0 release. Following our regular schedule, the branch would occur about two weeks into January, on Wednesday 17 January 2018, with the goal of shipping early March. This is the schedule I would propose. However, one large consumer of the branch has asked if we could start earlier this time, branching on 3 January instead (not
2019 Feb 07
9
[8.0.0 Release] rc2 has been tagged
Dear testers, 8.0.0-rc2 has been tagged from the release_80 branch at r353413. 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
2019 Mar 12
2
[8.0.0 Release] rc4 has been tagged
Hans Wennborg wrote: >Dear testers, > >8.0.0-rc4 was just tagged from the release_80 branch at r355690. I've tested the current branch on SystemZ without problems. I noticed I forgot to send a ReleaseNotes updates, sorry. If there's still time, here's a list of the major user-visible changes: (See attached file: systemz-releasenotes.diff) Mit freundlichen Gruessen / Best
2019 Mar 21
2
LLVM 8.0.0 Release
Thanks, Brian I tried enabling both the lld and the clang projects by adding -DLLVM_ENABLE_PROJECTS='lld;clang' into the cmake command. After the build completed successfully, I can see ld.lld in my bin folder but not clang. Is it supposed to be in another folder? Thanks. ________________________________ From: Brian Cain <brian.cain at gmail.com> Sent: Wednesday, March 20, 2019
2019 Mar 21
2
LLVM 8.0.0 Release
Hans, I'd like to make sure that I'm using the right LLVM version. I tried to download LLVM 8 from the link in your email by cloning this repository: git clone https://github.com/llvm/llvm-project.git When I do llc --version, it says LLVM 9.0.0 instead of 8.0.0 LLVM (http://llvm.org/): LLVM version 9.0.0svn DEBUG build with assertions. Default target: x86_64-unknown-linux-gnu
2016 Dec 05
2
[Openmp-dev] [4.0 Release] Schedule and call for testers
On Mon, Dec 5, 2016 at 10:42 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 05 Dec 2016, at 19:26, Hans Wennborg via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >> >> There's still plenty of time left, but I'd like to get the schedule >> set before folks start disappearing for the holidays. >> >> Note that this release will also
2017 Dec 15
2
[Openmp-dev] [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
2019 Aug 02
3
LLVM 8.0.1 Release
LLVM 8.0.1 is now available! Download it now, or read the release notes. This release contains bug-fixes for the LLVM 8.0.0 release. This release is API and ABI compatible with 8.0.0. LLVM 8.0.1 would not be possible without the help of our volunteer release team! Thanks to all the release testers: Dimitry Andric, Hans Wennborg, Yvan Roux, Sylvestre Ledru, Michał Górny, Bernhard Rosenkraenzer,
2019 Aug 02
3
LLVM 8.0.1 Release
LLVM 8.0.1 is now available! Download it now, or read the release notes. This release contains bug-fixes for the LLVM 8.0.0 release. This release is API and ABI compatible with 8.0.0. LLVM 8.0.1 would not be possible without the help of our volunteer release team! Thanks to all the release testers: Dimitry Andric, Hans Wennborg, Yvan Roux, Sylvestre Ledru, Michał Górny, Bernhard Rosenkraenzer,
2018 Feb 07
12
[6.0.0 Release] Release Candidate 2 tagged
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
2019 Apr 04
2
Unable to verify of llvm sources with the .sig files
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
2019 Jan 30
2
[8.0.0 Release] rc1 has been tagged
Alex, ping? There was a thread about moving Risc-V out of experimental but I think it didn't go anywhere? Separately, do the listed patches sound okay for merging? Thanks, Hans On Fri, Jan 25, 2019 at 4:40 PM Bruce Hoult <brucehoult at sifive.com> wrote: > > In https://llvm.org/svn/llvm-project/llvm/branches/release_80 I find > that RISCV is still in
2019 Jan 24
2
[Release-testers] [8.0.0 Release] rc1 has been tagged
On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers wrote: > On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > > > 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