Forum Discussion
Suggestion: Share Available Features in Each Build
It won't cost much, there could be a platform to automatically mine data from sources and show them in table and it won't take too much time and man power to do that, but it is valuable.
Let me share you some use cases, normally we ask users to use stable and final build. But let say user is looking for features which are not available in stable build yet and are critical for users, in this case we might need to invest on deploying next most stable build. For example, in case we have deployment plan for next month and we will see specific feature is available in Dev and next month will be available in Beta and it might take six month to come to stable release, then we deploy Beta instead of Dev. Normally, we come across these decisions after reviewing set of features in each build release note manually and then decide. It is not only about single user with one PC, but it is about entire organization. Knowing features and supported build in one view is very helpful to make decision especially when we are planning to do massive deployment. We could do this manually by looking into such information and bring them into table and then decide, but having such information save us time.
- HotCakeXNov 24, 2020MVPThere is top feedback list for insiders, and Microsoft docs for stable and beta.
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.- Reza_Ameri-ArchivedNov 25, 2020Bronze Contributor
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.
- HotCakeXNov 25, 2020MVPin 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.
- dragonwolf83Nov 25, 2020Brass Contributor
The problem is that the official https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel for Stable and Beta releases is not the complete list. It is geared more towards Enterprise feature/changes. I noticed this on the first release that it doesn't show all the bug fixes and was missing features that was clearly rolled out. For example, the Favorites menu is fully rolled out but not documented as such.
The Dev Change list and Feedback list is the most clear picture of tracking changes. My suggestion is that the Feedback List gain a column that indicates Can/Dev/Beta/Stable and then that can be used to help update the Release Notes documentation for Beta and Stable.
- HotCakeXNov 25, 2020MVPSpoiler
dragonwolf83 wrote:The problem is that the official Release Notes for Stable and Beta releases is not the complete list. It is geared more towards Enterprise feature/changes. I noticed this on the first release that it doesn't show all the bug fixes and was missing features that was clearly rolled out. For example, the Favorites menu is fully rolled out but not documented as such.
The Dev Change list and Feedback list is the most clear picture of tracking changes. My suggestion is that the Feedback List gain a column that indicates Can/Dev/Beta/Stable and then that can be used to help update the Release Notes documentation for Beta and Stable.
Yeah they can add an extra column to the top feedback list, but the favorites menu is a different matter.
they are knowingly/unknowingly running controlled feature rollout experiments in the stable channel.
I asked developers in the forum many times but none of them are responding, they all ignore that specific question, which is kind of suspicious, no one is denying nor confirming it, they all ignore.
this has never happened before:
Deleted johnjansen