App Version number: best practices / guidelines

TomigsTomigs Member Posts: 83

I'd like to ask for some advice on the version number for the apps (the parameter "version" in the app.json file).

We are currently using the below convention:
- "22" for the BC major version
- "5" for the application version
- "2023" - year
- "10" - month
- "11" - day
- "7" - version within the day

Would you have any suggestion/ alternative ways of doing it?

I'm considering things like if the BC version adds much info
And if it would be beneficial to add the type of environment (ie, a different version for UAT and Production: "UAT22.5.20231011.7" for example).

Any suggestion/correction is appreciated.




  • TallyHoTallyHo Member Posts: 383
    edited 2023-11-01
    We use the same build and revision number '$(Build.BuildNumber)' from the azure devops pipeline.
    It seems to me that you are doing that too.
    22 BC major version, same here.

    we do not use "5" for the application version, we use this for addressing the sprint that we were in at the time of app building.

  • TomigsTomigs Member Posts: 83
    Thanks TallyHo for your answer.
    We are not exactly working in sprints at the moment, but maybe it makes sense to include some release information there rather than the application version, that is interesting. I'll discuss with the guys.

Sign In or Register to comment.