Suggestion: Share Available Features in Each Build

%3CLINGO-SUB%20id%3D%22lingo-sub-1921691%22%20slang%3D%22en-US%22%3ESuggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921691%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20top%20feedback%20posts%20in%20this%20forum%20where%20inform%20us%20on%20upcoming%20features%20in%20Microsoft%20Edge.%20I%20though%2C%20it%20would%20be%20interesting%20if%20there%20was%20something%20like%20master%20list%20of%20features%20and%20availability%20in%20each%20channel.%20Take%20a%20look%20at%20following%20example%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20border%3D%221%22%20width%3D%2297.74977229245157%25%22%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3E%26nbsp%3B%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EOfficial%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EBeta%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EDev%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3ECan%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EFeature%201%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EFeature%202%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3EFeature%203%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%26nbsp%3B%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%26nbsp%3B%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3CTD%20width%3D%2220%25%22%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20height%3D%2229px%22%3EFeature%204%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Eavailable%26nbsp%3B%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Eavailable%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20height%3D%2229px%22%3EFeature%205%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Ecoming%20soon%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Eavailable%26nbsp%3B%3C%2FTD%3E%3CTD%20height%3D%2229px%22%3Eavailable%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20for%20features%20which%20have%20been%20confirmed%20to%20be%20available%20and%20user%20want%20to%20know%20which%20feature%20is%20available%20in%20each%20build.%20We%20could%20find%20details%20from%20posts%20%2C%20but%20representing%20in%20above%20format%20would%20be%20more%20valuable%20for%20many%20users.%20This%20is%20just%20an%20idea%20and%20we%20could%20discuss%20on%20improving%20it.%20Available%20could%20show%20the%20build%20number%20and%2For%20available%20date%20and%20coming%20soon%20also%20show%20estimated%20date%20where%20feature%20will%20be%20available%20or%20in%20case%20it%20is%20unknown%20just%20shows%20coming%20soon%20and%20this%20list%20could%20be%20updated%20regularly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921810%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921810%22%20slang%3D%22en-US%22%3E%3CP%3Eit%20already%20exist%20%3A%3CBR%20%2F%3E%3CBR%20%2F%3EStable%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-relnote-stable-channel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EStable%20Channel%3C%2FA%3E%3CBR%20%2F%3EBeta%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-relnote-beta-channel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EBeta%20Channel%3C%2FA%3E%3CBR%20%2F%3EDEV%20%26amp%3B%20CAN%20in%20this%20forum%20%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fbd-p%2FEdgeInsiderDiscussions%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EEdge%20Insider%20Discussions%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921821%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921821%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390049%22%20target%3D%22_blank%22%3E%40Aelisya%3C%2FA%3E%26nbsp%3B%3CSTRONG%3EAvailable%26nbsp%3B%3C%2FSTRONG%3Efeatures...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921848%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921848%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F565232%22%20target%3D%22_blank%22%3E%40Kam%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F565232%22%20target%3D%22_blank%22%3E%40Kam%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390049%22%20target%3D%22_blank%22%3E%40Aelisya%3C%2FA%3E%26nbsp%3B%3CSTRONG%3EAvailable%26nbsp%3B%3C%2FSTRONG%3Efeatures...%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThose%20websites%20he%20mentioned%20are%20for%20available%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921851%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921851%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13441%22%20target%3D%22_blank%22%3E%40Reza%20Ameri%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390049%22%20target%3D%22_blank%22%3E%40Aelisya%3C%2FA%3E%26nbsp%3Bsaid%20above%20is%20correct%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fsuggestion-share-available-features-in-each-build%2Fm-p%2F1921810%2Fhighlight%2Ftrue%23M39262%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fsuggestion-share-available-features-in-each-build%2Fm-p%2F1921810%2Fhighlight%2Ftrue%23M39262%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeta%20and%20Stable%20channels%20have%20their%20change%20logs%20with%20specific%20available%20features%20in%20Microsoft%20Docs.%3C%2FP%3E%3CP%3EAny%20new%20feature%20that%20gets%20crossed%20out%20on%20the%20Top%20Feedback%20list%20means%20that%20it%20is%20available%20on%20Edge%20canary%2C%20that's%20the%20starting%20point.%20Edge%20community%20moderators%20said%20that%20themselves.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eafter%20that%2C%20the%20weekly%20Edge%20dev%20update%20posts%20that%20contain%20change%20logs%2C%20precisely%20specify%20which%20features%20are%20available%20in%20each%20build.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921899%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921899%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BNo%2C%20I%20thought%20they're%20for%20new%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1922048%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1922048%22%20slang%3D%22en-US%22%3EThey%20are%20relatively%20new%2C%20to%20each%20version.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1924406%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1924406%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F390049%22%20target%3D%22_blank%22%3E%40Aelisya%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20fully%20aware%20of%20such%20available%20resources%20and%20I%20am%20checking%20them%20regularly.%20However%20%2C%20my%20point%20is%20having%20all%20details%20in%20one%20view%20like%20the%20table%20I%20just%20mentioned.%20From%20those%20resources%2C%20let%20say%20you%20want%20to%20see%20which%20feature%20is%20available%20in%20each%20build%2C%20you%20will%20need%20to%20check%20them%20one%20by%20one.%20But%20from%20the%20example%20I%20just%20shared%2C%20you%20could%20see%20availability%20of%20each%20feature%20in%20one%20view%20rather%20than%20having%20to%20check%20separate%20resources.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1924411%22%20slang%3D%22en-US%22%3ERe%3A%20Suggestion%3A%20Share%20Available%20Features%20in%20Each%20Build%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1924411%22%20slang%3D%22en-US%22%3EI%20don't%20see%20any%20reason%20to%20know%20when%20version%20of%20Edge%20had%20which%20feature%20in%20a%20table.%3CBR%20%2F%3Efeatures%20added%20to%20Stable%20are%20part%20of%20the%20browser%20now%2C%20they%20are%20usually%20showcased%20in%20What's%20New%20page%20and%20other%20Microsoft%20websites.%20lots%20of%20features%20are%20going%20to%20be%20added%20to%20stable.%3CBR%20%2F%3Ethey%20are%20well%20documented%20in%20Microsoft%20Docs%20(for%20stable%2Fbeta)%3CBR%20%2F%3Ethings%20we%20see%20for%20insider%20are%20also%20well%20documented%20in%20a%20table%20for%20Edge%20canary%2Fdev%2C%20even%20though%20they%20are%20temporary.%3CBR%20%2F%3E%3CBR%20%2F%3Ethere%20is%20no%20point%20in%20coming%20back%20and%20viewing%20a%20table%20that%20tells%20me%20web%20capture%20was%20added%201%20year%20ago%20or%20sidebar%20was%20added%209%20months%20ago.%20just%20useless%20info.%20they%20are%20all%20part%20of%20the%20Edge%20stable%20and%20one%20package.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
Valued Contributor

There is top feedback posts in this forum where inform us on upcoming features in Microsoft Edge. I though, it would be interesting if there was something like master list of features and availability in each channel. Take a look at following example:

 

 OfficialBetaDevCan
Feature 1coming sooncoming soonavailableavailable
Feature 2coming sooncoming sooncoming sooncoming soon
Feature 3available available availableavailable
Feature 4coming soonavailable availableavailable
Feature 5coming sooncoming soonavailable available 

 

This is for features which have been confirmed to be available and user want to know which feature is available in each build. We could find details from posts , but representing in above format would be more valuable for many users. This is just an idea and we could discuss on improving it. Available could show the build number and/or available date and coming soon also show estimated date where feature will be available or in case it is unknown just shows coming soon and this list could be updated regularly. 

31 Replies
Highlighted

it already exist :

Stable : Stable Channel
Beta : Beta Channel
DEV & CAN in this forum : Edge Insider Discussions.

Highlighted

@Aelisya Available features...

Highlighted

@Kam 


@Kam wrote:

@Aelisya Available features...


Those websites he mentioned are for available features.

Highlighted

@Reza Ameri 

What @Aelisya said above is correct

https://techcommunity.microsoft.com/t5/discussions/suggestion-share-available-features-in-each-build...

 

Beta and Stable channels have their change logs with specific available features in Microsoft Docs.

Any new feature that gets crossed out on the Top Feedback list means that it is available on Edge canary, that's the starting point. Edge community moderators said that themselves.

 

after that, the weekly Edge dev update posts that contain change logs, precisely specify which features are available in each build.

Highlighted

@HotCakeX No, I thought they're for new features.

Highlighted
They are relatively new, to each version.
Highlighted

@Aelisya @HotCakeX 

I am fully aware of such available resources and I am checking them regularly. However , my point is having all details in one view like the table I just mentioned. From those resources, let say you want to see which feature is available in each build, you will need to check them one by one. But from the example I just shared, you could see availability of each feature in one view rather than having to check separate resources.

Highlighted
I don't see any reason to know when version of Edge had which feature in a table.
features added to Stable are part of the browser now, they are usually showcased in What's New page and other Microsoft websites. lots of features are going to be added to stable.
they are well documented in Microsoft Docs (for stable/beta)
things we see for insider are also well documented in a table for Edge canary/dev, even though they are temporary.

there is no point in coming back and viewing a table that tells me web capture was added 1 year ago or sidebar was added 9 months ago. just useless info. they are all part of the Edge stable and one package.
Highlighted

@Reza Ameri 

And maintain useless information cost manpower, i prefer to see peoples integrate news functions than maintain an information totally useless since enterprise will only check the release note of the stable/beta version a roll it out manually.

And for technical user they will follow what information there is here or like @HotCakeX as said they will see on update page.

And for normal user they don't care and many of them will not even see the browser is updated.

Highlighted

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.

Highlighted
There 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.
Highlighted

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.

Highlighted

@dragonwolf83 

Spoiler

@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:

https://techcommunity.microsoft.com/t5/discussions/why-is-edge-87-stable-channel-running-experiments...

 

@fawkes @johnjansen 

 

Highlighted

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.

Highlighted
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.
Highlighted

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.

Highlighted
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.
Highlighted

It is not the way you said.

There are features we are sure will be available in stable release but might subject to change like add note to PDF or table of content.

It is also important to have such table to be able to provide valuable feedbacks. So let say we know this feature is available in which channel and we know exactly what channel we have to test and in large scale such data are very valuable.

Highlighted
It is exactly like what I described, because that's how it is in reality. it has nothing to do with feedbacks.
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.