[Feature/Addition] Have a process for maintaining stable vs experimental parsons docker images

[sharinetmc]

Stable and experimental parsons docker images

Detailed Description

We're hoping to develop a process for having at least two separate Parsons docker images (one that's considered "experimental", which pulls directly from the main branch, and another "stable" one that only contains changes that we can consider "stable")

Context

The differentiation between the two is important for users needing to use different images for development vs. production. For example, if users need to build dependable pipelines based off of parsons, they need an image that they can be confident won't be introducing breaking changes to their code. However, due to the fact that parsons has a pretty small usage base and not many maintainers, it will be a slight challenge to know when a change is considered "stable"

Possible Implementation

Priority

Interested People

@salice, @mxleader, @sharinetmc

[matthewkrausse]

How are we building and pushing the image right now? I don't see it in a workflow anywhere...

Probably just as simple as having the experimental image being based on main and then the stable version based on the most recent version in pypi.