I'm currently working on an online app that includes many fairly new (for the company) features and they fall outside my expertise area by far, which means the edges may not be really well rounded yet. My boss wants it to be released in a somehow continuous manner, publishing features one at a time. All of these features are new, the interface might not be definitive, and the style is definitely not, so everything is somehow left hanging. That's why we are only telling about this software to a bunch of users (although it's publicly available to everyone).
This continuous delivery method allowed him to decide to release quickly and without a deep testing or understanding on what other issues could be raised by imaginative users.
I decided to be honest and tell the users we're on a Beta phase, ensuring people understand what that means and allowing them to contact us through email in case they find any issue.
However, my boss told me to remove the Beta warning and test while it's online already, even removing the access to the contact email.
I guess this is to hide premature hurry (well... according to his words, to hide hesitation), but isn't it a backfire, if a blocking problem lets people out for too long, or the interface changes from one day to another? Wouldn't this make the software look unstable and untrustable?
How to convince my boss it would be better to show users the software they use is far from finished and may present problems?