similar to: 1.0 RC4 released

http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz.sig Does this fix the hangs people have been reporting? - SSL connections hanged sometimes, especially when saving messages. - mbox: Mail bodies were saved with CR+LF linefeeds - Mail forwarding was broken with deliver/Sieve - dbox fixes. Might actually be usable now. - Index file handling

http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz.sig Does this fix the hangs people have been reporting? - SSL connections hanged sometimes, especially when saving messages. - mbox: Mail bodies were saved with CR+LF linefeeds - Mail forwarding was broken with deliver/Sieve - dbox fixes. Might actually be usable now. - Index file handling

On 19 February 2015 at 13:57, Renato Golin <renato.golin at linaro.org> wrote: > test/CodeGen/R600/Output/infinite-loop-evergreen.ll > > Is actually in an infinite loop on AArch64... This is RC4 Phase3. I > didn't see that on RC3. Well, I spoke too early. Apparently the test finished after 8 minutes running... Is that expected? 8 minutes is longer than it takes to run the

Hello testers, RC4 has just been tagged (at r229782 on the branch). RC3 was disqualified due to an infloop that Duncan reported, and fixed in r229421. That, fixes for a few scary X86 bugs, a GCC5 bootstrap problem (PR22625), and parts of PR22589 is included in RC4. Baring any showstoppers, this release candidate will be promoted to release. Please let me know how it looks and upload binaries

Quick update before I move on to the final tag. > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > Still running due to a silly setup mistake on the first run (a broken > symlink to the test-suite source). Second attempt is a fair way through and > looks good so far though Default options were all good. Mips32 was about halfway but was good so far. >

Hi, I've encountered a severe regression in TU116 (probably also TU117) introduced in 5.3-rc4 (valid also for recent 5.4.2) [1]. The system usually hangs on the subsequent graphic mode related operation (calling xrandr after login is enough) with the following error: > kernel: nouveau 0000:01:00.0: fifo: SCHED_ERROR 08 [] ... > kernel: nouveau 0000:01:00.0: DRM: failed to idle channel

We got everything, haven't we? On 26 February 2015 at 20:44, Nikola Smiljanic <popizdeh at gmail.com> wrote: > Final has been tagged, I think we're about to release it. > > On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston <halivingston at gmail.com> > wrote: >> >> Are we waiting for an RC5? It seems like the release mirror on github has >> no

Dear testers, 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: - r245902: Revert r245355: change of clang-tools-extra symlink in the release script - r245947: Merge of r245927: Fix LLDB build on MIPS - r245948: Deprecate the DataLayout on the TargetMachine, and backport the 3.8 API - Changes to the ReleaseNotes. Those changes should all be safe, and I expect this to be an extremely

Are we waiting for an RC5? It seems like the release mirror on github has no recent activity. On Wed, Feb 25, 2015 at 3:23 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Quick update before I move on to the final tag. > > > clang+llvm-3.6.0-rc4-mipsel-linux-gnu.tar.xz > > Still running due to a silly setup mistake on the first run (a > broken >

Final has been tagged, I think we're about to release it. On Fri, Feb 27, 2015 at 7:43 AM, Hayden Livingston <halivingston at gmail.com> wrote: > Are we waiting for an RC5? It seems like the release mirror on github has > no recent activity. > > On Wed, Feb 25, 2015 at 3:23 AM, Daniel Sanders <Daniel.Sanders at imgtec.com > > wrote: > >> Quick update

On 2019-12-16 19:45, Ilia Mirkin wrote: > The obvious candidate based on a quick scan is > 0acf5676dc0ffe0683543a20d5ecbd112af5b8ee -- it merges a fix that > messes with PCI stuff, and there lie dragons. You could try building > that commit, and if things still work, then I have no idea (and you've Nice shot Ilia! I managed to build kernel from suspected bd112af5b8ee and it fails

On 2019-12-16 18:08, Ilia Mirkin wrote: > Hi Marcin, > > You should do a git bisect rather than guessing about commits. I > suspect that searching for "kernel git bisect fedora" should prove > instructive if you're not sure how to do this. Thanks for your suggestion. I realize that I can do it at the Git level and it is the ultimate way to go. However, building the

Hi, I've tagged the 8.0.1-rc4 release, please begin testing. This will (hopefully) be the last release candidate. If all goes well, I will tag the final release next Wednesday. -Tom

Hello everyone, A little less than a week after rc3, the llvmorg-11.0.0-rc4 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc4 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725

Hi, I've tagged 10.0.1-rc4, please test and report the results. -Tom

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

We found two regressions. One on Active Record and one on Action Pack. Took some time to fix those issues so the release was delayed until today. Here are the changes from 4.0.1.rc3 to 4.0.1.rc4: https://github.com/rails/rails/compare/v4.0.1.rc3...v4.0.1.rc4 And the changes from 4.0.0 to 4.0.1: https://github.com/rails/rails/compare/v4.0.0...v4.0.1.rc4 If we don''t hit any more