Slashdot Mirror
Microsoft To Release Two Major Windows 10 Updates Next Year (arstechnica.com)
An anonymous reader quotes a report from Ars Technica: With the Windows 10 Anniversary Update, aka Windows 10 version 1607, released earlier this week, it's time to look forward to what's next. Windows 10 has multiple release tracks to address the needs of its various customer types. The mainstream consumer release, the one that received the Anniversary Update on Tuesday, is dubbed the Current Branch (CB). The Current Branch for Business (CBB) trails the CB by several months, giving it greater time to bed in and receive another few rounds of bug fixing. Currently the CBB is using last year's November Update, version 1511. In about four months, Microsoft plans to bump CBB up to version 1607, putting both CB and CBB on the same major version. [The Long Term Servicing Branch, an Enterprise-only version that will receive security and critical issue support for 10 years, will also be updated.] Going forward, however, the differences between both current branch variants (CB and CBB) and LTSB will become more marked. Microsoft is not planning another major update this year. There will be no equivalent to last year's 1511 release, but Microsoft will have two next year. These are believed to be codenamed Redstone 2 (rs2) and Redstone 3 (rs3), with this week's 1607 release being Redstone 1 (rs1). Current expectation is that rs2 will have a heavy mobile focus and be shipped simultaneously with new Surface branded hardware.
I've been through two major OS upgrades and even more minor ones since purchasing my Mac mini, none of which I paid for. Either you're misinformed or Apple just really likes me for some reason.
Irony: Agile development has too much intertia to be abandoned now.
Besides, this is how most OSS projects work.
Except that with Linux distributions, e.g., you choose the patches you want by choosing the distribution that does the patches you want. You can pick a more conservative or more trigger-happy team of people. With Windows 10? Apparently, you can buy your new car as long you want it black.
Ezekiel 23:20
TFA mentions Current Branch and Current Branch for Business, without explaining them too much. I doubt that many folks here are aware of them and the differences, so...
If you're on CB, you get major feature updates (e.g. the Anniversary Edition) pushed to you as soon as it's made generally available. Folks on CBB will still get those updates pushed to them, but a while later (MS says around four months delay), and with all the fixes made in that time.
Now, if you have the Pro or Enterprise editions (sorry Home users, you guys are stuck on CB only), you can quite easily switch between the two by means of checking (or unchecking) the "Defer upgrades" option that's somewhere in the Windows Update options. Want to live on MS's cutting edge? Leave it off. Want to use those Home peasants as your beta testers? Switch it on.
Then, there's the LTSB edition of Enterprise, which is basically RTM that just receives security patches and the like (MS will make newer versions available -- I believe there's a 2016 update to LTSB coming later this year -- but, as far as I'm aware, there's no obligation to upgrade to a newer LTSB version, and MS claims that they'll support each version for ~10 years anyway). Because MS doesn't want too many things in this edition to change, things like Edge, Cortana and the Windows Store are stripped out of it. MS's intended usage scenarios for this edition are things like POS machines and the like.
You can actually compare this to Ubuntu upgrades. If you're on CB, you're like the Ubuntu user who upgrades between point releases as soon as the new one becomes available. If you're on CBB, you're like the Ubuntu user who upgrades between point releases as soon as the old one is about to become unsupported. If you're on LTSB, then you're the Ubuntu user who only ever uses the LTS releases.
Cygwin and the Linux Subsystem are completely different entities. Cygwin is an attempt to implement the POSIX API on the Win32 API set. Most applications will compile just fine under this emulated environment, and the applications are regular Win32 applications as far as Windows is concerned. The shell has been modified so it will append ".exe" when launching an image if it wasn't specified (because you can't do "ls" as it will fail (file not found), but "ls.exe" will succeed) These binaries are stnadard WinPE style binaries.
The Linux Subsystem is more akin to the FreeBSD Linux API layer - it runs Linux binaries unmodified, so the NTOSKRNL will natively load an ELF image, emulates the LInux syscall interface and provides all the necessary calls to make it appear you're running on Linux.
It's why Windows 10 can load Ubuntu 14.04 userspace - it's not a recompiled for Windows set of binaries, but everything that ships in Ubuntu 14.04 minus the Linux kernel.
No, they explicity stated that registry settings won't work either. You have absolutely no control over the disabled settings.