Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 309 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
App Version number: best practices / guidelines
Tomigs
Member Posts: 86
Hi,
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.5.20231011.7
Being:
- "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.
Thanks,
Tomas
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.5.20231011.7
Being:
- "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.
Thanks,
Tomas
0
Answers
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.
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.
Tomas