Pip availability and clear versioning in branches/tags/releases

[cryptexis]

Hi Pearl team,

thank you for all the work you have done.

The problem is I am having is the following:
while the Pearl is formulated as something to be used in production - simple procedures like versioning are not taken care of. We have developed a routine that every day an agent will be trained and deployed (and it is done in an environment such as AWS Sagemaker). What this entails is that when SM instance is spinning up, it must install the Pearl and all other important dependencies.
The way you have described in the documentation is not sufficient for the production work, when spontaneously changes are committed to the main branch. Stable versions are needed - where API, functionality and behavior are fixed for a given version.

Hope that makes sense also for you.

[rodrigodesalvobraz]

Thank you for making this point. You are absolutely right. We will prioritize this issue.

[anishpdoshi]

Plus one to availability via PyPi, that would unblock us from using this in a production system.