Still miss a bug tracker and detailed changelogs for both Dev and Canary

%3CLINGO-SUB%20id%3D%22lingo-sub-1272056%22%20slang%3D%22en-US%22%3EStill%20miss%20a%20bug%20tracker%20and%20detailed%20changelogs%20for%20both%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272056%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20this%20was%20mentioned%20many%20times%20here%20in%20the%20discussions%20before%2C%20but%20I%20want%20to%20bring%20this%20up%20again%20because%20I%20think%20it's%20pretty%20important%20for%20the%20further%20development%20of%20edge.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20We%20need%20a%20bug%20tracker%20like%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2F%3C%2FA%3E%26nbsp%3Bto%20report%20issues%20and%20follow%20the%20progress%20of%20fixing.%20The%20feedback%20button%20is%20a%20nice%20feature%2C%20but%20you%20can't%20track%20the%20bug%20and%20don't%20know%20if%20it's%20recognized%2C%20worked%20on%20or%20maybe%20even%20fixed.%20And%20the%20dev%20team%20gets%20multiple%20feedbacks%20on%20the%20exact%20same%20issue%2C%20that's%20not%20very%20productive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20I%20think%20it%20would%20be%20very%20important%20to%20have%20a%20detailed%20changelog%20for%20both%20channels%2C%20Dev%20and%20Canary.%20It's%20extremely%20difficult%20for%20us%20insiders%20to%20test%20new%20features%20or%20bug-fixes%20without%20knowing%20what%20changes%20have%20been%20made%2C%20especially%20in%20the%20Canary%20branch.%20It's%20a%20daily%20game%20of%20trial%20and%20error%20for%20most%20of%20us%2C%20so%20a%20changelog%20would%20be%20very%20helpfull.%3C%2FP%3E%3CP%3EI%20know%20this%20produces%20extra%20workload%2C%20but%20on%20the%20other%20hand%20a%20better%20and%20faster%20feedback%20from%20us%20testers%20may%20reduce%20some%20coding%26nbsp%3Bexpenditure%20in%20return%20and%20speed%20up%20the%20development.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20dear%20Developer%20Team%2C%20please%20think%20this%20over%2C%20you'd%20do%20us%20insiders%20a%20big%20favour%20with%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1280053%22%20slang%3D%22en-US%22%3ERe%3A%20Still%20miss%20a%20bug%20tracker%20and%20detailed%20changelogs%20for%20both%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1280053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F382315%22%20target%3D%22_blank%22%3E%40Neon01%3C%2FA%3E%26nbsp%3BWe%20appreciate%20you%20reaching%20out%20and%20bringing%20this%20back%20to%20our%20attention.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20provide%20some%20insight%3A%20we%20definitely%20see%20that%20these%20are%20important%20to%20our%20Insiders%2C%20but%20there%20are%20some%20confounding%20factors.%20However%2C%26nbsp%3Bthe%20good%20news%20is%20that%20we've%20heard%20your%20feedback%2C%20and%20our%20team%20is%20actively%20reviewing%20both%20requests!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)Project%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I know this was mentioned many times here in the discussions before, but I want to bring this up again because I think it's pretty important for the further development of edge. 

 

1. We need a bug tracker like https://bugs.chromium.org/ to report issues and follow the progress of fixing. The feedback button is a nice feature, but you can't track the bug and don't know if it's recognized, worked on or maybe even fixed. And the dev team gets multiple feedbacks on the exact same issue, that's not very productive.

 

2. I think it would be very important to have a detailed changelog for both channels, Dev and Canary. It's extremely difficult for us insiders to test new features or bug-fixes without knowing what changes have been made, especially in the Canary branch. It's a daily game of trial and error for most of us, so a changelog would be very helpfull.

I know this produces extra workload, but on the other hand a better and faster feedback from us testers may reduce some coding expenditure in return and speed up the development. 

 

So dear Developer Team, please think this over, you'd do us insiders a big favour with it.

 

 

1 Reply

@Neon01 We appreciate you reaching out and bringing this back to our attention.

 

To provide some insight: we definitely see that these are important to our Insiders, but there are some confounding factors. However, the good news is that we've heard your feedback, and our team is actively reviewing both requests!

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge