IMO, it is extremely confusing to have multiple releases with the exact same version number. How are your users supposed to know when there is a new version if they can't see that the version number has been incremented in some way? 2.2 => 2.3, or 2.2 => 2.2b, or 2.2 => 2.2.1
Are we supposed to keep downloading it and checking the date?
company policy cannot be discussed or changed right now
Of course it can be discussed and changed. We are discussing it right now. And your CEO can change it instantly. It is a policy that is most unusual in the software industry and most unhelpful to your customers.
No kidding, you shold use the minor versioning system, or at least put a "latest build date mm/dd/yy/" with the ***** fixes on your main page! If I rely on the software and my job could be on the line for it, I wouldn't even let my mother tell me "these fixes are nothing major" without knowing what was different. I agree, your CEO needs to change this ridiculous policy because it looks like it has no real purpose other than to give a nice big "screw you!" to your customers.
What if all your customers developed a policy where we would not buy a product that sneaks revisions in without documenting them and refuses to detail them?