All geek questions in one place

When to remove the beta tag?

My team will launch the web application in beta soon. At what point should the beta tag go?

Google seems to be holding onto the beta tag for a long time, while others have been doing it for a month or so. Is there any rule of thumb, like all known errors fixed for subsequent ones, or a time frame, or some other technique for this?

Of course, when Beta is gone, money can be made in the way development is related to the importance of the beta period for management?

I want to know what / are the criteria that should be used to fully label the beta. Not when we are ready, but when the application is ready.

+3
source share
5 answers

, "" , , , - - , , , - , , , ​​ , -.

+1

"" , . - , " " ( , API ,... ).

, , , , "". , , .

+4

- , . -, , . , , .

+1

: , , , . Alpha , . , . , , , . , , .

- "".

+1

/ (1.2.3 alpha-beta-RC ..) . , , "" - , - .

Tags like beta versions can signal the quality of your product in a business environment of reliability, availability, security, etc. After removing the beta tag, you can say that you are ensuring that the user interface, DOM model, document export format, or open API are not going to change. Or you can remove the beta tag when you decide what SLA to provide.

+1
source

Source: https://habr.com/ru/post/1735299/

More articles:


All Articles