Forum Discussion
Solved
Teams Release Management
Hello Community, My profession is Cloud Application Release Management. I've found release management for Teams to be difficult to track (From a release management perspective). I've been unable to...
- Hi AaronThorne
In short, there is no unified site or app with which to monitor changes for Microsoft Teams across all versions, all clients, or all servicing channels (TAP, Public Preview, GA). There is no authoritative source in the difference between clients and client versions (I.e. Desktop/IoS/IPadOS/Android/VDI). Most of us use a mix which includes, but which is not an authoritative list, the M365 Roadmap, Message Centre, Docs.com, Tech Community, the Microsoft Teams Blog and Teams Uservoice. In terms of Teams updates Microsoft provides this on docs.com
https://docs.microsoft.com/en-us/microsoftteams/teams-client-update#:~:text=Teams%20desktop%20client%20updates%20are%20released%20every%20two,release%20the%20update%20as%20soon%20as%20it%E2%80%99s%20available.
I don't know if any groups to discuss service release management exist. There are some great groups around that may be interested. I run Teams Nation along with Adam Deltinger, Vesa Nopanen and Chris Webb who would be interested if you wanted to run a session. Teams ACM Europe with Karoliina Kettukari and Alexander Eggers would probably be interested too. But since Teams is such a broad overarching application very few I know are specifically focussed on release cadence. So I would find Teams usergroups, two of which I have named, join them and get going on a session about the challenges of release management
Hope that helps and answers your question
Best, Chris
AaronThorne absolutely a total pain in the.. Well you know. Also the VDI version does not match the cloud version. Makes for frustrated customers.
- We've found for VDI news and updates, it's best to reach out to Citrix directly.
- Yes, this is a vast recurring subject not only in this community. Seen tons of comments about the Teams desktop client updates, and a couple similar posts here as of today. And I totally agree. Much to be done in this space. Ranging from more specific and detailed update process info (I’ve seen the docs) to version release history, the client updates, the backend updates, the new features minimum client version etc.
