Hi all, The following article from Windows Central confirms rumors about why November 2019 Update isn’t a full Windows 10 build but rather a service pack. As you can see, Version 20H1 is about to RTM (release to manufacturing), sooner than Windows Insiders predicted: https://www.windowscentral.com/windows-10-os-development-schedule-changes To expand what the article says (and based on other sources I can gather): A few years ago Windows development was put under Azure development. Because Microsoft Azure uses an outdated version of Windows Server platform, it needed to catch up with technologies introduced in newer Windows Server releases such as 2016 and 2019, which are both cloud optimized. In order to do that, Azure and Windows developers had to be on the same development schedule, and given the fact that Azure releases were done in June and December and Windows targeted March and September, something had to be sacrificed; and that sacrifice is Windows 10 November 2019 Update: rather than a full Windows 10 release, it is a service pack on top of May 2019 Update. Based on the article linked, Windows 10 Version 20H1 is done – it is going through bug fix phase, typically done for several months prior to RTM and general availability a few weeks later. Although it is scheduled for December, it will still carry 20H1 codename because public release will be done in 2020. This means some of us (Windows Insiders) will be moved to 20H2 (codenamed “Manganese”, targeting June 2020) in a few weeks, which also explains why slow ring Insiders will be moving to 20H1 builds soon. The things I noted above will have huge implications for this forum cluster, which I’ll outline in an upcoming “state of the list” post. Cheers, Joseph
|
|
Hello Joseph! I am an insider on the slow ring. Right now, I have 1903 still
With build number 18362.10024. I am wondering if I will even get the 1909 build, because I have not received it yet, and it sounds like 20h1 is being wrapped up already. well I start getting builds for 20h1 being a slow ring insider, or will I still receive 1909? I was just wondering about this. Take care Joseph, and thanks for keeping us enlightened! David Moore
sent from Android toy!
toggle quoted messageShow quoted text
Hi all, The following article from Windows Central confirms rumors about why November 2019 Update isn’t a full Windows 10 build but rather a service pack. As you can see, Version 20H1 is about to RTM (release to manufacturing), sooner than Windows Insiders predicted: https://www.windowscentral.com/windows-10-os-development-schedule-changes To expand what the article says (and based on other sources I can gather): A few years ago Windows development was put under Azure development. Because Microsoft Azure uses an outdated version of Windows Server platform, it needed to catch up with technologies introduced in newer Windows Server releases such as 2016 and 2019, which are both cloud optimized. In order to do that, Azure and Windows developers had to be on the same development schedule, and given the fact that Azure releases were done in June and December and Windows targeted March and September, something had to be sacrificed; and that sacrifice is Windows 10 November 2019 Update: rather than a full Windows 10 release, it is a service pack on top of May 2019 Update. Based on the article linked, Windows 10 Version 20H1 is done – it is going through bug fix phase, typically done for several months prior to RTM and general availability a few weeks later. Although it is scheduled for December, it will still carry 20H1 codename because public release will be done in 2020. This means some of us (Windows Insiders) will be moved to 20H2 (codenamed “Manganese”, targeting June 2020) in a few weeks, which also explains why slow ring Insiders will be moving to 20H1 builds soon. The things I noted above will have huge implications for this forum cluster, which I’ll outline in an upcoming “state of the list” post. Cheers, Joseph
|
|
Hi, If you are on slow ring, you’ll eventually get 20H1. Cheers, Joseph
toggle quoted messageShow quoted text
From: win10@win10.groups.io <win10@win10.groups.io> On Behalf Of David Moore Sent: Monday, October 28, 2019 2:21 PM To: win10@win10.groups.io Subject: Re: [win10] Windows Central: Windows 10 Version 20H1 is about to RTM #WinTenDev Hello Joseph! I am an insider on the slow ring. Right now, I have 1903 still With build number 18362.10024. I am wondering if I will even get the 1909 build, because I have not received it yet, and it sounds like 20h1 is being wrapped up already. well I start getting builds for 20h1 being a slow ring insider, or will I still receive 1909? I was just wondering about this. Take care Joseph, and thanks for keeping us enlightened! David Moore sent from Android toy! Hi all, The following article from Windows Central confirms rumors about why November 2019 Update isn’t a full Windows 10 build but rather a service pack. As you can see, Version 20H1 is about to RTM (release to manufacturing), sooner than Windows Insiders predicted: https://www.windowscentral.com/windows-10-os-development-schedule-changes To expand what the article says (and based on other sources I can gather): A few years ago Windows development was put under Azure development. Because Microsoft Azure uses an outdated version of Windows Server platform, it needed to catch up with technologies introduced in newer Windows Server releases such as 2016 and 2019, which are both cloud optimized. In order to do that, Azure and Windows developers had to be on the same development schedule, and given the fact that Azure releases were done in June and December and Windows targeted March and September, something had to be sacrificed; and that sacrifice is Windows 10 November 2019 Update: rather than a full Windows 10 release, it is a service pack on top of May 2019 Update. Based on the article linked, Windows 10 Version 20H1 is done – it is going through bug fix phase, typically done for several months prior to RTM and general availability a few weeks later. Although it is scheduled for December, it will still carry 20H1 codename because public release will be done in 2020. This means some of us (Windows Insiders) will be moved to 20H2 (codenamed “Manganese”, targeting June 2020) in a few weeks, which also explains why slow ring Insiders will be moving to 20H1 builds soon. The things I noted above will have huge implications for this forum cluster, which I’ll outline in an upcoming “state of the list” post. Cheers, Joseph
|
|
When will the stable build of 19h2 be rolling out I don’t want to force it just wondering when it will come ddown on Windows update .
toggle quoted messageShow quoted text
From: win10@win10.groups.io <win10@win10.groups.io> On Behalf Of Joseph Lee Sent: Monday, October 28, 2019 2:53 PM To: win10@win10.groups.io Subject: Re: [win10] Windows Central: Windows 10 Version 20H1 is about to RTM #WinTenDev Hi, If you are on slow ring, you’ll eventually get 20H1. Cheers, Joseph From: win10@win10.groups.io <win10@win10.groups.io> On Behalf Of David Moore Sent: Monday, October 28, 2019 2:21 PM To: win10@win10.groups.io Subject: Re: [win10] Windows Central: Windows 10 Version 20H1 is about to RTM #WinTenDev Hello Joseph! I am an insider on the slow ring. Right now, I have 1903 still With build number 18362.10024. I am wondering if I will even get the 1909 build, because I have not received it yet, and it sounds like 20h1 is being wrapped up already. well I start getting builds for 20h1 being a slow ring insider, or will I still receive 1909? I was just wondering about this. Take care Joseph, and thanks for keeping us enlightened! David Moore sent from Android toy! Hi all, The following article from Windows Central confirms rumors about why November 2019 Update isn’t a full Windows 10 build but rather a service pack. As you can see, Version 20H1 is about to RTM (release to manufacturing), sooner than Windows Insiders predicted: https://www.windowscentral.com/windows-10-os-development-schedule-changes To expand what the article says (and based on other sources I can gather): A few years ago Windows development was put under Azure development. Because Microsoft Azure uses an outdated version of Windows Server platform, it needed to catch up with technologies introduced in newer Windows Server releases such as 2016 and 2019, which are both cloud optimized. In order to do that, Azure and Windows developers had to be on the same development schedule, and given the fact that Azure releases were done in June and December and Windows targeted March and September, something had to be sacrificed; and that sacrifice is Windows 10 November 2019 Update: rather than a full Windows 10 release, it is a service pack on top of May 2019 Update. Based on the article linked, Windows 10 Version 20H1 is done – it is going through bug fix phase, typically done for several months prior to RTM and general availability a few weeks later. Although it is scheduled for December, it will still carry 20H1 codename because public release will be done in 2020. This means some of us (Windows Insiders) will be moved to 20H2 (codenamed “Manganese”, targeting June 2020) in a few weeks, which also explains why slow ring Insiders will be moving to 20H1 builds soon. The things I noted above will have huge implications for this forum cluster, which I’ll outline in an upcoming “state of the list” post. Cheers, Joseph
|
|
Some reports say on the next patch day, either the 12th of
november or the 10th or before that.
toggle quoted messageShow quoted text
On 29/10/2019 11:05 am, g melconian
wrote:
When will the stable build of 19h2 be
rolling out I don’t want to force it just wondering when it
will come ddown on Windows update .
Hi,
If you are on slow ring, you’ll eventually
get 20H1.
Cheers,
Joseph
From: win10@win10.groups.io
<win10@win10.groups.io> On
Behalf Of David Moore
Sent: Monday, October 28, 2019 2:21 PM
To: win10@win10.groups.io
Subject: Re: [win10] Windows Central: Windows 10
Version 20H1 is about to RTM #WinTenDev
Hello Joseph! I am an insider on the slow ring. Right now, I
have 1903 still
With build number 18362.10024. I am wondering if I will even
get the 1909 build, because I have not received it yet, and it
sounds like 20h1 is being wrapped up already. well I start
getting builds for 20h1 being a slow ring insider, or will I
still receive 1909? I was just wondering about this. Take care
Joseph, and thanks for keeping us enlightened! David Moore
sent from Android toy!
Hi
all,
The
following article from Windows Central confirms rumors
about why November 2019 Update isn’t a full Windows 10
build but rather a service pack. As you can see,
Version 20H1 is about to RTM (release to
manufacturing), sooner than Windows Insiders
predicted:
https://www.windowscentral.com/windows-10-os-development-schedule-changes
To
expand what the article says (and based on other
sources I can gather):
A
few years ago Windows development was put under Azure
development. Because Microsoft Azure uses an outdated
version of Windows Server platform, it needed to catch
up with technologies introduced in newer Windows
Server releases such as 2016 and 2019, which are both
cloud optimized. In order to do that, Azure and
Windows developers had to be on the same development
schedule, and given the fact that Azure releases were
done in June and December and Windows targeted March
and September, something had to be sacrificed; and
that sacrifice is Windows 10 November 2019 Update:
rather than a full Windows 10 release, it is a service
pack on top of May 2019 Update.
Based
on the article linked, Windows 10 Version 20H1 is done
– it is going through bug fix phase, typically done
for several months prior to RTM and general
availability a few weeks later. Although it is
scheduled for December, it will still carry 20H1
codename because public release will be done in 2020.
This means some of us (Windows Insiders) will be moved
to 20H2 (codenamed “Manganese”, targeting June 2020)
in a few weeks, which also explains why slow ring
Insiders will be moving to 20H1 builds soon.
The
things I noted above will have huge implications for
this forum cluster, which I’ll outline in an upcoming
“state of the list” post.
Cheers,
Joseph
|
|