similar to: 5.0.1 Release Schedule

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

Hi, It's about time to start thinking about the 3.8.1 release. Here is a proposed release schedule: May 25 - Deadline to request a change be merged to the 3.8 branch. June 1 - Deadline to merge changes to the 3.8 branch. June 1 - 3.8.1-rc1 June 8 - 3.8.1-rc2 (if necessary) June 15 - 3.8.1 Release If you want a patch included in the 3.8.1 release, send an email to llvm-commits with the

Tom - In terms of release testing - What about using OpenSUSE build service? It could be possible to setup a toolchain and try to build a ton of packages. Most of this could be easily automated and you may significantly extend the amount of code coverage you get. I don't think build service is able to run make test, but you'd possibly flush out build and link issues. (As well as seeing how

Hi, I would like to start a discussion about improvements to the stable release process, but first, here is a proposed schedule for the 4.0.1 release. May 1, 2017 -rc1 May 22, 2017 Deadline for submitting merge request May 29, 2017 Deadline for merging changes. June 3, 2017 -rc2 June 10, 2017 Final Release This is slightly different from previous stable releases in that we are doing an early

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch.

Hi, Here is a proposed release schedule for 3.9.1: Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch Nov 29, 2016: -rc1 Dec 5, 2015: 3.9.1 Release As a reminder, if you would like to request a patch be merged to the 3.9 branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx into the 3.9 branch." and add

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.

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

Hi, Here is the schedule for the 3.6.2 release: June 15: Deadline to propose patches for the 3.6 branch June 15 - June 21: Grace period for reviewing proposed patches and resolving other issues. June 22: 3.6.2 -rc1 June 29: 3.6.2 release Also, I would like to try to try to experiment with using phabricator for proposing patches to the stable branch. This is not a

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

Will the PR's marked as blockers of PR36649 be merged in or do we need to do something specific? On Thu, Apr 26, 2018 at 12:28 AM, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I've just tagged the 6.0.1-rc1 release. Testers may begin testing and > uploading > binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to >

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

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

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 a 'real' Release Candidate. The purpose of rc1 will be to update and test the release scripts

On Wed, Nov 29, 2017 at 6:19 PM, Tom Stellard via Release-testers < release-testers at lists.llvm.org> wrote: > Hi, > > I've tagged the 5.0.1-rc2 release, go ahead and start testing and report > your results. > > > SLES11 uploaded. 1312db7bdfd05c82dd52983f8c5df1a6819df79f clang+llvm-5.0.1-rc2-linux-x86_64-sles11.3.tar.xz -------------- next part -------------- An

Hi, The merge request deadline for 6.0.1 is scheduled for Friday, May 18, with the -rc2 release schedule for May 25. If you have patches you want merged please submit your requests by Friday, this will make it easier for us to get code owner approval and merge the patches. As always, I will continue to accept new merge requests right up until -rc2, but I may have to say no to last minute

Hello everyone, There's plenty of time before the release process starts, but I'd like to begin the schedule discussion. For the September release we usually branch mid-July. However, this year my vacation runs a little later, so a good branch date for me would be the 1st of August. Proposal: - 1 August 2018: Branch; RC1 soon after - 22 August 2018: RC2; all lose ends should be tied up

I request this to be included in the 6.0.1 release: https://reviews.llvm.org/rLLD330788 On Wed, May 16, 2018 at 5:12 PM, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > The merge request deadline for 6.0.1 is scheduled for Friday, May > 18, with the -rc2 release schedule for May 25. If you have patches you > want merged please submit your requests

Hello everyone, I know 7.0.1 isn't out the door yet, and 8.0.0 isn't due for a while, so relax :-) But I would like to get the schedule decided before folks disappear over the holidays. According to the usual schedule, the branch would be created two weeks into January, with the goal of shipping early March, so this is my proposal: - 16 January 2019: Create the 8.0.0 branch, RC1 tagged

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original