New revision documentation

%3CLINGO-SUB%20id%3D%22lingo-sub-67160%22%20slang%3D%22en-US%22%3ENew%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67160%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20releasing%20a%20new%20version%20of%20Windows%2010%20can%20it%20be%20accompanied%20with%20detailed%20documentation%20about%20new%2Fchanged%2Fdeprecated%20features%2C%20especailly%20those%20that%20could%20impact%20applications%20e.g.%20API%2C%20security%20models%2C%20features%3F%20Reason%20being%20that%20with%20160k%2B%20machines%2C%203000%2B%20applications%20and%203000%2B%20internal%2Fexternal%20websites%20used%20daily%2C%20we%20need%20to%20provide%20our%20developer%2Fapplication%20owner%20community%20with%20as%20much%20information%20as%20possible.%26nbsp%3B%20This%20is%20going%20to%20be%20key%20to%20maintaining%20the%20cadence%20of%20the%20CBB%20releases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357589%22%20slang%3D%22en-US%22%3ERe%3A%20New%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357589%22%20slang%3D%22en-US%22%3E%3CP%3EI%20second%20this%20-%20it%20would%20really%20be%20helpful%20to%20have%20all%20this%20information%20bundled%20together%20on%20a%20single%20site%20instead%20of%20having%20to%20piece%20it%20together%20component%20by%20component%E2%80%A6%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67239%22%20slang%3D%22en-US%22%3ERe%3A%20New%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67239%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20great%20news%20and%20looks%20like%20the%20information%20we%20need.%20(Edge%20also%20has%20a%20great%20site%20on%20what's%20changed%20-%20%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fmicrosoft-edge%2Fplatform%2Fchangelog%2Finsider%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fmicrosoft-edge%2Fplatform%2Fchangelog%2Finsider%3C%2FA%3E).%3C%2FP%3E%3CP%3EHowever%2C%20I%20have%20asked%20by%20my%20TAM%20and%20DSE%20for%20this%20numerous%20times%20and%20I've%20had%20nothing%20from%20them.%20How%20about%20putting%20all%20the%20links%20on%20one%20site%20for%20each%20release%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67233%22%20slang%3D%22en-US%22%3ERe%3A%20New%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67233%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20continually%20working%20to%20improve%20our%20documentation.%20Today%2C%20we%20publish%20information%20about%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4014193%2Ffeatures-that-are-removed-or-deprecated-in-windows-10-creators-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eremoved%2Fdeprecated%20features%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwhats-new%2Fwhats-new-windows-10-version-1703%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Enew%2Fupdated%20documentation%20for%20IT%20pros%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fwhats-new%2Fwindows-10-version-1703%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ewhat's%20new%20for%20developers%3C%2FA%3E%2C%20a%20list%20of%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fwhats-new%2Fwindows-10-version-1703-api-diff%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Enew%20APIs%3C%2FA%3E%2C%20and%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fwindowsitpro%2F2017%2F04%2F05%2Fwhats-new-for-it-pros-in-the-windows-10-creators-update%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ewhat's%20new%20for%20IT%20pros%3C%2FA%3E.%20You%20can%20also%20find%20a%20list%20of%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fwhats-new%2Fwindows-10-build-15021-api-diff%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Enew%20APIs%20in%20Preview%20builds%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67225%22%20slang%3D%22en-US%22%3ERe%3A%20New%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67225%22%20slang%3D%22en-US%22%3EWe%20release%20deprecation%20information%20here%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4014193%2Ffeatures-that-are-removed-or-deprecated-in-windows-10-creators-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4014193%2Ffeatures-that-are-removed-or-deprecated-in-windows-10-creators-update%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20general%20we%20strive%20to%20keep%20Windows%20compatible%20and%20not%20break%20apps%20or%20change%20things.%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe'd%20recommend%20looking%20into%20Windows%20Analytics%3A%20Upgrade%20Readiness%20which%20uses%20telemetry%20data%20to%20provide%20rich%2C%20actionable%20information%20to%20help%20you%20gain%20deep%20insights%20into%20operational%20efficiency%20and%20the%20health%20of%20Windows%26nbsp%3B10%20devices%20in%20your%20environment.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2FWindowsForBusiness%2Fwindows-analytics%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2FWindowsForBusiness%2Fwindows-analytics%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67215%22%20slang%3D%22en-US%22%3ERe%3A%20New%20revision%20documentation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67215%22%20slang%3D%22en-US%22%3E%3CP%3EAbsolutely%20necessary%20because%20with%20fixed%20delivery%20dates%20and%20quality%2C%20features%20will%20slip%20or%20move%20between%20releases.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

When releasing a new version of Windows 10 can it be accompanied with detailed documentation about new/changed/deprecated features, especailly those that could impact applications e.g. API, security models, features? Reason being that with 160k+ machines, 3000+ applications and 3000+ internal/external websites used daily, we need to provide our developer/application owner community with as much information as possible.  This is going to be key to maintaining the cadence of the CBB releases.

5 Replies
Highlighted

Absolutely necessary because with fixed delivery dates and quality, features will slip or move between releases.

Highlighted
We release deprecation information here https://support.microsoft.com/en-us/help/4014193/features-that-are-removed-or-deprecated-in-windows-...

In general we strive to keep Windows compatible and not break apps or change things.

We'd recommend looking into Windows Analytics: Upgrade Readiness which uses telemetry data to provide rich, actionable information to help you gain deep insights into operational efficiency and the health of Windows 10 devices in your environment.

https://www.microsoft.com/en-us/WindowsForBusiness/windows-analytics
Highlighted

We are continually working to improve our documentation. Today, we publish information about removed/deprecated features, new/updated documentation for IT pros, what's new for developers, a list of new APIs, and what's new for IT pros. You can also find a list of new APIs in Preview builds.

Highlighted

This is great news and looks like the information we need. (Edge also has a great site on what's changed - https://developer.microsoft.com/en-us/microsoft-edge/platform/changelog/insider).

However, I have asked by my TAM and DSE for this numerous times and I've had nothing from them. How about putting all the links on one site for each release? 

Highlighted

I second this - it would really be helpful to have all this information bundled together on a single site instead of having to piece it together component by component…