You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to convince my tech team to set up a production environment for DocIntel.
However, to handle integration issues and be able to set up a proper rollback strategy, some form of code release with corresponding Docker images would be required.
With the latest such image almost one year old and updates being pushed to the "latest" tag in dockerhub, rolling back becomes quite complicated.
Therefore, I am wondering if the rolling release with only a "latest" image will be the model going forward or if we could expect a more traditional model with a numbered release to be added in the near future.
The text was updated successfully, but these errors were encountered:
I am not aware of all the steps involved with pushing a new docker image but if an update is significant enough to warrant building one, maybe giving it a dedicated version tag and release would make sense.
If images are pushed at a faster rate than usual for whatever reason, a monthly wrap-up release would make sense.
First, thank you for your work.
I have been trying to convince my tech team to set up a production environment for DocIntel.
However, to handle integration issues and be able to set up a proper rollback strategy, some form of code release with corresponding Docker images would be required.
With the latest such image almost one year old and updates being pushed to the "latest" tag in dockerhub, rolling back becomes quite complicated.
Therefore, I am wondering if the rolling release with only a "latest" image will be the model going forward or if we could expect a more traditional model with a numbered release to be added in the near future.
The text was updated successfully, but these errors were encountered: