# We always worked in a way where the master branch is running a regular release train into our internal / beta / preview release (depending on company and audience size).
Care to elaborate how you decide if it is an internal / beta / preview release? Some kind of tagging strategy or are all generated at the same time?
Care to elaborate how you decide if it is an internal / beta / preview release? Some kind of tagging strategy or are all generated at the same time?