Language Selection

English French German Italian Portuguese Spanish

Linux 4.20 RC1

Filed under
  • Linux 4.20-rc1

    So I did debate calling it 5.0, but if we all help each other, I'm
    sure we can count to 20. It's a nice round number, and I didn't want
    to make a pattern of it. I think 5.0 happens next year, because then I
    *really* run out of fingers and toes.

    Anyway, 4.20-rc1 is tagged and pushed out, and the merge window is
    over. This was a fairly big merge window, but it didn't break any
    records, just solid. And things look pretty regular, with about 70% of
    the patch is driver updates (gpu drivers are looming large as usual,
    but there's changes all over). The rest is arch updates (x86, arm64,
    arm, powerpc and the new C-SKY architecture), header files,
    networking, core mm and kernel, and tooling.

    In fact, tooling is quite noticeable. A fair amount of selftest
    changes, but also various perf tooling updates.

    There's a vfs pull request I declined and it might still go in later
    in a slightly reduced form, but apart from that I think everything got
    merged. We had one pull request that almost missed the merge windows
    due to a silly change in my email setup, but I verified that nothing
    else had happened to hit that special case.

    One thing I _would_ like to point out as the merge window closes: I
    tend to delay some pull requests that I want to take a closer look at
    until the second week of the merge window when things are calming
    down, and that _really_ means that I'd like to get all the normal pull
    requests in the first week of the two-week merge window. And most
    people really followed that, but by Wednesday this week I had gotten a
    big frustrated that I kept getting new pull requests when I wanted to
    really just spend most of the day looking through the ones that
    deserved a bit of extra attention.

    And yes, people generally kind of know about this and I really do get
    *most* pull requests early. But I'm considering trying to make that a
    more explicit rule that I will literally stop taking new pull requests
    some time during the second week unless you have a good reason for why
    it was delayed.

    Because yes, the merge window is two weeks, but it's two weeks partly
    exactly _because_ people (not just me) sometimes need extra time to
    resolve any possible issues, not because regular everyday pull
    requests should spread out over the whole two weeks. The development
    for things meant for the next release should have been done by the
    time the merge window opens.

    Anyway, let's see. Maybe it won't be needed. It hasn't become a
    problem, it just was starting to feel a bit tight there.

    Oh, and I did try to do the reply emails. And I'm _entirely_ sure that
    I must have missed acknowledging emails for a few pull requests. I'm
    hoping that by the time the next merge window rolls around, we'll just
    have new automation for it, so that everybody just automatically gets
    notified when their pull request hit mainline. In the meantime, you
    have a good chance - but not a guarantee - that I'll send a "Pulled"
    ack email when I start processing a pull request.

    And as usual for rc1, the log below is just the list of people I
    pulled from with a one-liner "mergelog". Very much a high-level
    summary of merges, for details you need to look into the git tree..


  • Linux 4.20-rc1 Kernel Released As The Kernel Hits Its Highest Point For 2018

    The next kernel release was either going to be Linux 4.20 or Linux 5.0 and today Linus Torvalds decided it would be the "4.20" kernel version.

    Linux 4.20-rc1 was just tagged in Git while keeping to the "People's Front" codename that was introduced with Linux 4.19 final. Sorry, no "420" jokes for the codename at this stage and the kernel changes this merge window are in fact far from being blunt.

The Many New Features of The Linux 4.20 Kernel

  • The Many New Features of The Linux 4.20 Kernel

    With Linus Torvalds having just released Linux 4.20-rc1, here is our original feature overview looking at the major changes merged over the past two weeks for this new kernel. The Linux kernel will be ending 2018 on a high note with this kernel bringing more than 350 thousand lines of new code!
    This kernel began its life two weeks ago not knowing whether it would be called Linux 4.20 or Linux 5.0. As with the transition from Linux 3.20 being renamed to Linux 4.0, Linus Torvalds previously disclosed his preference after his fingers and toes are counted, to move onto the next big version bump. In today's announcement, Linus Torvalds decided to stick to 4.20.

Linus Torvalds Says Linux 5.0 Comes in 2019

  • Linus Torvalds Says Linux 5.0 Comes in 2019, Kicks Off Development of Linux 4.20

    Linus Torvalds is back from a short vacation to rethink his strategy as the leader of the development of the Linux kernel, and kicked off a new development cycle for the next 6 weeks, this time for Linux kernel 4.20.

    That’s right, Linux 4.20 is the next kernel coming after Linux 4.19, which was released by Greg Kroah-Hartman on October 22,2018, not Linux 5.0 like many of you out there where hoping to see this year. Linus Torvalds decided it’s best to end 2018 with Linux 4.20 and release Linux 5.0 in 2019.

Woke Linus Torvalds rolls his first 4.20, mulls Linux 5.0 effort

  • Woke Linus Torvalds rolls his first 4.20, mulls Linux 5.0 effort for 2019

    The new, improved, and chilled-out Linus Torvalds emitted the first release candidate for Linux kernel 4.20 over the weekend.

    He decided not to repeat the jump from 3.19 to 4.0 that happened last year, thus avoiding leaping from 4.19 to 5.0, because “I didn't want to make a pattern of it,” he told the kernel's official development mailing list.

    “At this point," the kernel project chieftain added, “I think 5.0 happens next year,” and if all goes well, the Linux 4.20 kernel will be done by December.

    His Sunday evening code drop was “70 per cent” driver updates, Torvalds typed, with GPU drivers “looming large as usual” in the “fairly big merge window.”

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

WordPress 5.3 “Kirk”

5.3 expands and refines the block editor with more intuitive interactions and improved accessibility. New features in the editor increase design freedoms, provide additional layout options and style variations to allow designers more control over the look of a site. This release also introduces the Twenty Twenty theme giving the user more design flexibility and integration with the block editor. Creating beautiful web pages and advanced layouts has never been easier. Read more

Proprietary Software From OnlyOffice and Microsoft

  • OnlyOffice, the Open Source Office Suite Apis Now Available on Flathub

    Big fan of productivity software? If so, you may be interested to know that the OnlyOffice Desktop Editors are now available on Flathub. Yes, Flathub, aka the de facto app store for Flatpak, the cross-distro containerised app distribution method.

  • ONLYOFFICE Desktop Editors Now Available To Install On Linux From Flathub

    ONLYOFFICE Desktop Editors, a free and open source office suite that offers text, spreadsheet and presentation editors for the Linux, Windows and macOS desktops, is now available on Flathub for easy installation (and update) on Linux distributions that support Flatpak. Flathub is an app store and build service for Linux that distributes applications as Flatpak packages, which allows them to run on almost any Linux distribution. ONLYOFFICE Desktop Editors allows creating, viewing and editing text documents, spreadsheets and presentations with support for most popular formats like .docx, .odt, .xlsx., .ods, .pptx, .csv and .odp. Its website claims it has the "highest compatibility with Microsoft Office formats".

  • How to get Microsoft core fonts on Linux

    Linux is an open-source operating system. As a result, it is missing some critical components that users of proprietary operating systems enjoy. One big thing that all Linux operating systems miss out on is proprietary fonts. The most used proprietary fonts out there today are the Microsoft Core Fonts. They’re used in many apps, development, and even graphics design projects. In this guide, we’ll go over how to set them up on Linux. Note: not using Ubuntu, Debian, Arch Linux, Fedora, or OpenSUSE? Download the generic font package here and install the fonts by hand.

IEI's and Arbor Technology's Linux-Ready Devices

  • IEI ITG-100AI DIN-Rail Rugged mini PC Comes with a Myriad X AI Accelerator Module
  • Compact Kaby Lake signage player has dual 4K HDMI ports

    Arbor’s rugged, Linux-friendly “IEC-3900” signage player has a 7th Gen U-Series Core CPU, dual independent 4K HDMI ports, 4x USB 3.0 ports, M.2 SATA storage, and a 130 x 124 x 35mm footprint. Arbor Technology, which recently introduced a rugged ELIT-1930 signage player based on Intel’s 8th Gen Coffee Lake, has now launched an even more rugged signage system with a much more compact form factor that runs on a 7th Gen Kaby Lake processor. The 130 x 124 x 35mm, 0.73 kg IEC-3900 runs Linux or Win 10 on a dual-core, 2.8GHz/3.9GHz Core i7-7600U or 2.6GHz/3.5GHz Core i5-7300U.

today's howtos