Forum Discussion
Suggestion: Share Available Features in Each Build
if user doesn't want to wait 6 weeks, then they can use Beta, change log again in Microsoft docs.
nothing can be so critical to force someone use unstable builds from Dev or Canary for their "critical" job. even if that was the case, Dev weekly change log posts and there to help.
top feedback list also has a history list.
there are a lot of important things to work on.
Let me tell you one example, in production environment we always deploy stable build but users working a lot with stable build but they want PDF feature to add note. In this case, either we have to deploy third-party program like Adobe Reader or deploy the build of Microsoft Edge where support this feature or in case we know it will be available soon, wait for availability.
Once this feature becomes available in stable release we shall remove insider version. Having such feature is not consuming a lot of time but it is very valuable for users.
- in that example there is no need for this. just install insider builds and you will find out which one has it, And also read the change logs.
before deploying anything, you have to test it so you will know.Yes, this is exactly what we are doing, we trying all builds and check release notes and they make decisions but having such a table would make our jobs a lot easier and I believe it is the same for other users.
In addition, this could be data retrieval and could be done automatically.
- That's not how it works.
in business environments, people don't make decisions based on things that exist in Dev and Canary channels. even Edge developers don't know which features are going to be added to which Stable channel exactly, until they experiment with them a lot and receive data from users.
things that are in Dev and Canary can be removed at any time or something else replace them, or get delayed by a couple of months.
this is why this chart or whatever is useless, Specially for businesses.
the only concrete information businesses need, and I'm talking from experience, is the change log that is official and exists in Microsoft Docs.
the same thing applies to Windows channels (Dev/Beta/Release Preview).
anything in the Dev channel is subject to change/removal at any time.