Talk:Windows Insider

If someone will ever Create a Windows 10 version history page, please merge this page with that one, thank you. --Namlong618 (talk) 10:07, 22 February 2015 (UTC)

: What's your rationale behind this proposal? We've already voted to keep this page, remember that? <<< SOME GADGET GEEK >>> (talk) 18:28, 29 March 2015 (UTC)

How to make the telephone list collapse and expandable? --Lumia930uploader (talk) 08:16, 28 March 2015 (UTC)

When I navigated to [http://windows.microsoft.com/en-us/windows/preview-supported-phones Microsoft's supported phone listings] today I have noticed that the Lumia 540 is now on the list. Using the [http://web.archive.org/web/20150630220717/http://windows.microsoft.com/en-us/windows/preview-supported-phones Internet Archive database cache from June 30], I didn't see the 540 there, but [http://webcache.googleusercontent.com/search?q=cache:sc4olZahPEUJ:windows.microsoft.com/en-us/windows/preview-supported-phones+&cd=1&hl=en&ct=clnk&gl=us Google's cache of the page on July 10] includes the 540. I've taken this as an advance note of an official preview build to be released for the device soon and have updated the table accordingly. <<< SOME GADGET GEEK >>> (talk) 03:26, 12 July 2015 (UTC)

:That's an understandable edit, personally I would add every Windows Phone device to the table, but for older models I'd say that there is a certain level of uncertainty, but for newer models Microsoft has largely confirmed that they will receive the Windows 10 update in the future. --42.113.73.178 (talk) 02:09, 13 July 2015 (UTC)

::Build 10166 has been released and although [http://blogs.windows.com/bloggingwindows/2015/07/10/announcing-windows-10-mobile-insider-preview-build-10166/ Gabe Aul's post] never mentioned it, users of Lumia 540s are [http://www.nokiapoweruser.com/windows-10-mobile-build-10166-installation-experience-screenshots-gallery/ reporting] that they have received this build... which means, de facto official support? <<< SOME GADGET GEEK >>> (talk) 17:59, 16 July 2015 (UTC)

I check pages listed in :Category:Pages with incorrect ref formatting to try to fix reference errors. One of the things I do is look for content for orphaned references in wikilinked articles. I have found content for some of :Windows Insider's orphans, the problem is that I found more than one version. I can't determine which (if any) is correct for this article, so I am asking for a sentient editor to look it over and copy the correct ref content into this article.

Reference named "ieblog-spartan":

• From Windows 10: {{cite web |title=Project Spartan and the Windows 10 January Preview Build |url=http://blogs.msdn.com/b/ie/archive/2015/01/22/project-spartan-and-the-windows-10-january-preview-build.aspx |website=IEBlog |publisher=Microsoft |accessdate=January 23, 2015}}
• From Microsoft Edge: {{cite web | url=http://blogs.msdn.com/b/ie/archive/2015/01/22/project-spartan-and-the-windows-10-january-preview-build.aspx | title=Spartan and the Windows 10 January Preview Build | publisher=Microsoft | website=IEBlog | date=January 21, 2015 | first1=Jason | last1=Weber}}

Reference named "ieblog-edge":

• From Windows 10: {{cite web |title=Living on the Edge – our next step in helping the web just work |url=http://blogs.msdn.com/b/ie/archive/2014/11/11/living-on-the-edge-our-next-step-in-interoperability.aspx |website=IEBlog |publisher=Microsoft |accessdate=January 23, 2015}}
• From Microsoft Edge: {{cite web | url=http://blogs.msdn.com/b/ie/archive/2014/11/11/living-on-the-edge-our-next-step-in-interoperability.aspx | title=Living on the Edge – our next step in helping the web just work | publisher=Microsoft | website=IEBlog | date=November 11, 2014 | first1=Jacob | last1=Rossi}}

I apologize if any of the above are effectively identical; I am just a simple computer program, so I can't determine whether minor differences are significant or not. AnomieBOT⚡ 22:35, 15 November 2015 (UTC)

:I fixed the cite errors. Thank you. Qpalzmmzlapq (talk) 02:14, 16 November 2015 (UTC)

OOPS! I meant to put "Removed version history section: Windows 10's was placed in Windows 10 version history and Windows 10 Mobile's is in the Windows 10 Mobile page" but I accidentally pressed Enter and the edit was saved. The bold text is what I accidentally left out and meant to put in the edit summary. Sorry about that. Qpalzmmzlapq (talk) 00:55, 17 November 2015 (UTC)

:That's ok, we can accept that. Next time, how about trying the dummy edit procedure? <<< SOME GADGET GEEK >>> (talk) 02:32, 17 November 2015 (UTC)

http://mspoweruser.com/microsoft-launches-bing-insider-program-to-get-suggestions-and-feedback-from-bing-users/

There is a related Bing Insider service, someone please incorporate this into the history or introductory section as a related but separate service. --14.162.227.163 (talk) 11:05, 4 May 2016 (UTC)

:Why not just make a separate article called Bing Insider? <<< SOME GADGET GEEK >>> (talk) 01:06, 5 May 2016 (UTC)

Should we divide the list of Windows Phone devices further into those that originally came with Windows Phone 8.1 and those that came with Windows 10 Mobile? It'd make it much easier on the eyes when we can see right away, for example, that the only WP8.1 devices the Creator's Update is coming to is the L640/XL. ««« SOME GADGET GEEK »»» (talk) 18:32, 21 April 2017 (UTC) ««« SOME GADGET GEEK »»» (talk) 18:32, 21 April 2017 (UTC)

Hello

Today I noticed a longstanding gaffe in the article: An {{tl|Infobox software}} was placed on it giving the impression that there is such a thing as a "Windows Insider" app. The information in the infobox were unreferenced, and as far as I am concerned, wrong and contradictory. I'll start from the top:

• The logo: It is the logo of Windows 10 but the article already says the program was available for Windows Phone 8.1 and Windows Server 2016.
• The screenshot: It is not a screenshot of an app called Windows Insider. The subject of this article is an organized effort anyway. Per our WP:NFCC policy (our most strict policy, AFAIK) this spurious image must not be.
• Original author: An organized effort has no "author". It has a leader or organizer.
• Initial release: An organized effort has no initial release. It has a launch date. Also, this date contradicts the date in the lead, which is 30 September 2017.
• Development status: Again, no' an app...
• Operating system: The most glarring error. I am aware that there are people who go to articles about Windows components and arbitarily add "Xbox One" or "Xbox System Software" to whichever that already has "Windows 10" on it. But lead text contradicts this: "Microsoft Office, Bing, Xbox and Visual Studio Code teams have set up their own Insider programs". In other words, Windows Insider does not cover Xbox which is already covered by Xbox Insider.
• License: Again, no' an app...
• Website: Oh, well. This one is correct, but again, I think no one is going to miss it, seeing how it is already at the bottom of the article.

Best regards,
Codename Lisa (talk) 12:56, 26 November 2017 (UTC)

Okay, this has been bugging me for a while. The Wikipedia article states that the Microsoft ring is the last internal ring that a Windows build goes through before going to the, public, Insider Fast ring. I know this fact to incorrect. This USED to be the case back in 2015. Now it's 2018, and the Fast ring receives builds BEFORE the Microsoft ring does.

So this is how it currently stands:

Canary ring (daily builds) > WDG Selfhost ring (3 builds/week) > WIP Fast ring (~weekly builds plus or minus) > Microsoft ring (once validated by WIP Fast) > WIP Slow ring (once validated by WIP Fast > WIP Release Preview (once build hits RTM)

The announcement was posted on the Windows Insider hub, and also noted in a couple of third party sources in the web.

I'm updating the article to reflect this change, with citations of course, Insh'Allah. For more information, please see the citations included with the update.

Best,

NazmusLabs (A small part of a bigger movement to better the world!) (talk) 23:50, 20 March 2018 (UTC)

There was a major issue on how the Skip Ahead ring was described in the article. It was described as a "faster" version of the fast ring, meaning that builds get validated by Skip Ahead and moves on to the slow ring, essentially, making the Skip Ahead "fast", Fast ring "Medium", and Slow ring "Slow".

That's not how it works.

The skip ahead ring is essentially the Fast ring except that it always stays on the prerelease development branch. The Fast ring, on the other hand, stays locked to a particular release until it reaches RTM, and can be on either the prerelease or the release development branch, depending on the phase of development. As a release nears completion, Microsoft changes its branch from rs_prerelease to rs_release. The release is now on a stabilization phase where it continues to receive new builds containing bug fixes and performance optimization until a build is declared as RTM. The RTM build then heads off to the Slow ring and the Release Preview ring and the Fast ring is switched back to the rs_prerelease branch where it now locks on to the next release of Windows 10, which the Skip Ahead ring was already on.

In summery, the Skip Ahead ring is a mode of the Fast ring that will stay locked to and only receive builds from the prerelease branch, even if it means its receiving builds that are two versions away, whereas the regular Fast ring will stay locked on to the next release and get builds from it until it reaches RTM and then lock on to the next release.

Best,

NazmusLabs (A small part of a bigger movement to better the world!) (talk) 00:59, 21 March 2018 (UTC)

As the content this page deals with is also related to WDG i am wondering if it would be good to either integrate WDG here or to create a separate page for WDG.

This [https://gist.github.com/riverar/697fb0b21a0d83278ea2 page] provides additional material on WDG currently not contained in the article or elsewhere (as far as i know).

--Alexander.stohr (talk) 12:42, 24 January 2019 (UTC)