search

ItzLevvie / MicrosoftTeams-msinternal

This project was created from PowerShell which allows people to download the latest internal build of Microsoft Teams.
486 stars 30 forks source link

How to read the 2.0 and 2.1 version number #37

Closed X-15 closed 7 months ago

X-15 commented 1 year ago

Hi! I tried to figure it out, but couldn't really. I can't find a pattern on my own, so I am asking: For example this 2.1 version: 23095.300.1995.3049 <- how does one read that?

ItzLevvie commented 7 months ago

We use the YYDDD.XXXX.XXXX.XXXX version format for Teams 2.0 and Teams 2.1.

Here is an example: Microsoft Teams version `24041.300.2689.9173` is broken down into the following: - `24` (YY) is the year of the build. - `041` (DDD) is the day number of that year. - `041` represents Saturday, February 10, 2024. - `040` represents Friday, February 9, 2024. - `039` represents Thursday, February 8, 2024. - `300` (XXXX) is automatically generated by Azure DevOps. - `2689` (XXXX) is the amount of builds we have created excluding servicing builds. - `9173` (XXXX) is automatically generated by Azure DevOps.

We use the 1.X.00.DDDXX version format for Teams 1.0.

Here is an example: Microsoft Teams version `1.7.00.4065` is broken down into the following: - `7` (X) is the year of the build. - `7` represents 2024. - `6` represents 2023. - `5` represents 2022. - `4` represents 2021. - `3` represents 2020. - `2` represents 2019. - `1` represents 2018. - `0` represents 2017. - `40` (DDD) is the day number of that year. - `40` represents Friday, February 9, 2024. - `39` represents Thursday, February 8, 2024. - `38` represents Wednesday, February 7, 2024. - `65` (XX) is automatically generated by Azure DevOps. We have two build flavors for Teams 1.0: - Stable (S) = Any build version ending with `51` to `99` is a stable build. - Experimental (E) = Any build version ending from `1` to `49` is an experimental build.