Back to Community Threads
8
Call Version 17 Version 17
Idea shared by Patrick Jeski - 12/18/2019 at 6:03 AM
Proposed
I think it's time to go back to calling version 17 version 17. Going by just the release only causes confusion. When the beta is over, what version will the release be referred to? How will people know what release they are supported through? The current version, which even SmarterTools refers to as "Commonly known as Version 17" is version 100. 

Please end the insanity, and go back to reasonable version numbers.

3 Replies

Reply to Thread
2
Agreed. Build numbers cause confusion both verbally and online. If you post a problem and reference 'the latest build' or version 100, then when people come back and read it 6 months from now, they have no idea what code base you were talking about.

Good idea. It's much easier to deal with version numbers.
2
I thought SmarterTools was moving SM to a continuous build cycle instead of using major version releases like 15, 16, 17, the product is just "SmarterMail" now.
0
Yes, that’s what they seem to be doing, I just have no idea why. I can’t think of a single advantage to not having version numbers, especially if they are still going to have effectively major changes between builds. 
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Slow 250 response after Mail From command is issued during an SMTP session.SmarterMail > Troubleshooting
Set up Autodiscover for SmarterMailSmarterMail > Installation and Configuration
SmarterTools Licensing InformationGeneral Topics
Flex Billing for Microsoft Exchange ActiveSyncGeneral Topics
Migrate SmarterMail to a Different ServerSmarterMail > Installation and Configuration