similar to: 4.0.1 Release Schedule + Need feedback for improving stable releases

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

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

I've uploaded clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz and clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz started testing them. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Daniel Sanders > Sent: 16 March 2015 15:36 > To: Tom Stellard; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Reminder 3.5.2

Hi, Just a reminder that testing for 3.5.2 will begin on Monday, Mar 16. If you have any patches you want merged please send an email to the relevant commits list and cc me and the code owner. If you have already done this and are waiting for a response, please ping the thread. As always we need testers, so let me know if you want to help with testing. Thanks, Tom

With today''s build, my domain 0 crashes during boot when it tries to bring eth0 up (it''s an E100). cb->prev (eax) is NULL in e100_exec_cb() (e100.c:827). Just from code inspection, I don''t see how this can be. e100_alloc_cbs() was just called, which looks like it should have correctly linked up all the cb->prev/cb->next pointers. It happens regardless of

Hi Hans, 2016-07-30 0:57 GMT+02:00 Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org>: > There are still open merge requests and bugs, but I'd like to get the > real testing started to see where we're at. Just to double-check, is this bug also on people's radar? It causes Clang to crash when trying to build a fair number of Open Source packages/libraries. In my

Some users are hitting this panic in network_alloc_rx_buffers() when running a big network intensive app: /* Check return status of HYPERVISOR_dom_mem_op(). */ if ( rx_mcl[nr_pfns].args[5] != nr_pfns ) panic("Unable to reduce memory reservation\n"); I''m not clear on what is happening here. Are the domains changing size? Which memory reservation is being

Hi, I've just tagged the 4.0.1 -rc1 release. Testers can start testing and uploading the binaries. If you still have bug fixes you want to get into the 4.0.1 release, you have until May 22 to submit merge requests. -Tom

While trying to compile xen-bk.2.0 unstable,at my debian 3.1 machine everthing went fine until make docs here`s the error message ------------------------------------------------------------------------------------------------------- make -C docs all || true make[2]: Entering directory `/root/xen-2.0.bk/docs'' latex interface >/dev/null if [ -e interface.toc ] ; then latex interface

Hi. First of all, thanks for Xen. It''s terrific! I''m interested in doing memory oversubscription and am wondering if Xen can do this (now or in the future). For example, on a machine with 100MB available physical memory, can I: 1. Create a domain with a 90MB allocation 2. Inflate a balloon in that domain and return say 40MB back to Xen I know there are mechanisms for doing

Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small

Hi Tom, On 9 Jun 2014, at 15:36, Tom Stellard <tom at stellard.net> wrote: > Unfortunately, it is too late to get this into 3.4.2. With the 3.5 > release coming soon, I wasn't planning on doing another 3.4 point > release. We are likely to keep the llvm 3.4 port in FreeBSD for a while after 3.5 is released. We've only removed the llvm 3.1 port a couple of months ago. A

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

Good news, everybody! It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly. This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive

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 >

Hi, We're less than 2 weeks away from the developer meeting, so I wanted to give an update on the GitHub migration and what's (hopefully) going to happen during the developer meeting. Everyone who has added their information to the github-usernames.txt file in SVN before today should have received an invite to become a collaborator on the llvm-project repository. If you did not receive

Dear All, I've just heard that there's been a recent discussion on the IRC channel about moving the LLVM source repository from CVS to Subversion (SVN) and that this migration may happen "soon." Is such a migration being planned, and if so, what is the timeframe? How will the migration be performed? I and other LLVM users have deadlines in the near future, so we would like to

Hi, I just tagged LLVM 4.0.1-rc3, and it's ready for testing. If all goes well, we will do the final release on Monday. -Tom