Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] LLVM 3.3.1 Release Plans"
2013 Sep 11
0
[LLVMdev] LLVM 3.3.1 Release Plans
On Fri, Aug 23, 2013 at 04:17:02PM -0700, Tom Stellard wrote:
> Hi,
>
> The number of stable patches has slowed down in the last few weeks, and
> we are approaching the halfway point between 3.3 and 3.4, so I think now
> is a good time to start planning for the 3.3.1 release. Here is the
> tentative schedule:
>
> September 3: 3.3.1-rc1
> - This won't actually be
2013 Sep 12
1
[LLVMdev] LLVM 3.3.1 Release Plans
On Tue, Sep 10, 2013 at 09:02:58PM -0700, Tom Stellard wrote:
> On Fri, Aug 23, 2013 at 04:17:02PM -0700, Tom Stellard wrote:
> > Hi,
> >
> > The number of stable patches has slowed down in the last few weeks, and
> > we are approaching the halfway point between 3.3 and 3.4, so I think now
> > is a good time to start planning for the 3.3.1 release. Here is the
2018 Jun 15
7
6.0.1-rc3 has been tagged
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
2018 Dec 08
5
LLVM 7.0.1-rc3 has been tagged.
Hi,
I've just tagged 7.0.1-rc3. This will hopefully be the last release candidate.
Please test and report results.
Thanks,
Tom
2019 Jun 27
4
LLVM 8.0.1-rc3
Hi,
I've just tagged LLVM 8.0.1-rc3. Testers, please begin testing and report
results.
-Tom
2016 Dec 10
5
3.9.1-rc3 has been tagged
Hi,
I have tagged 3.9.1-rc3. The only differences from -rc2 were a few
bug fixes for ARM/AARCH64, so if you aren't testing either of these
I think it's safe to take this -rc off and what for -final.
I'm hoping to do -final next week after I get the ARM test results.
Thanks,
Tom
2017 Dec 07
7
5.0.1-rc3 has been tagged
Hi,
I've just tagged 5.0.1-rc3, please test and report the results.
Hopefully, this will be the last RC and the final release will
be next week.
-Tom
2014 May 12
12
[LLVMdev] LLVM 3.4.2 Release Plan - Testers Needed
Hi,
I would like to begin the 3.4.2 release process for LLVM. There have
been two issues identified in 3.4.1, which there is interest in having
fixed in a 3.4.x release:
1. Build failure with gcc 4.9 (This is not a regression, 3.4 also fails
to build with gcc 4.9).
2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4
libLLVM-3.4.1.so
I will also accept any other bug-fixes that
2016 Dec 13
7
3.9.1 -final has been tagged
Hi,
I've created the 3.9.1-final tag no changes from -rc3. Testers can
begin uploading binaries now.
-Tom
2018 Mar 30
4
LLVM 5.0.2-rc2 has been tagged
Hi,
I've fixed the version numbering and tagged 5.0.2-rc2. Testers can
begin testing.
-Tom
2020 Jul 08
8
10.0.1-rc4 tagged
Hi,
I've tagged 10.0.1-rc4, please test and report the results.
-Tom
2014 Dec 19
9
[LLVMdev] 3.5.1 Testing Phase II Begins
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
2019 Jun 11
3
LLVM 8.0.1-rc2 has been tagged
Hi,
I've tagged the 8.0.1-rc2 release, testers please begin testing and upload your
binaries.
There are still a few more bug fixes that I need to merge, so
I'm planning to do one more release candidate before 8.0.1-final.
-Tom
2020 May 21
10
RFC: Release process changes
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.
2013 Jun 24
10
[LLVMdev] LLVM 3.3 dot releases
Hi,
A few months ago, I mentioned I was interested in helping to make dot
releases for LLVM 3.3. Now that 3.3 has been released, I would like
to kick off the process of collecting bug fixes and merging them into the
3.3 branch.
I reviewed the previous discussion about dot releases:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/060821.html
and I've come up with the following dot
2018 Jun 07
2
[Release-testers] 6.0.1-rc2 has been tagged
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)
2018 Apr 20
0
[Release-testers] LLVM 5.0.2-rc2 has been tagged
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
2016 Dec 02
9
3.9.1-rc2 is ready for testing
Hi,
I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in
-rc1 before I could send out a release announcement, so I decided to merge
the fix and tag -rc2 to save some testing cycles.
We can always use more testers, so if you are interested in helping, let
me know.
Thanks,
Tom
2018 Mar 13
4
LLVM Release Schedules: 5.0.2, 6.0.1
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
2015 Feb 13
10
[LLVMdev] [3.6 Release] RC3 has been tagged
Hello testers,
Start your engines, RC3 has just been tagged (at r229050 on the
branch). If this one looks good, it will become the release.
There has been quite a bit of activity on the branch since RC2; let's
hope it's all goodness :-)
Please let me know how it looks, and upload binaries to the sftp as usual.
Thanks for all your efforts so far!
- Hans