Package versions of libraries

chinmoy12c commented 1 year ago

[x] Currently, we have a history of multiple older versions of libraries to maintain for adapter, utils, message-rosa, and dao. We need to decide whether to maintain these versions or delete them.
[ ] We also need to follow a fixed documented convention while building releases for all these libraries. There should be different release tags based on development and production code.
[x] We may add a feature to our GitHub actions to build these versions based on which branch code is pushed to. If we push to development a staging release should be built with the corresponding tag and if we push to master a production build with the proper release tag should be built.
[ ] We need to decide whether the versions of all the libraries should remain similar to each other or they may be different based on individual code updates. If the versions are kept different we need some way to document which version of a particular library is stable with which version of another library. For example, version 1.2.0 of the adapter may be stable with version 1.2.4 utils but not with 1.2.5.

pankajjangid05 commented 1 year ago

Deployed code on stagging with below release tags and package name:

These are only for stagging deployment.

chinmoy12c commented 1 year ago

We will keep the history of those builds, but we will not support those versions and tag those as deprecated.
The libraries would all have the same version to make it easier to manage versions.

susheelvar commented 1 year ago

@RyanWalker277 to automatic build and deployment of images on development branch.

karntrehan commented 1 year ago

PR raised. Reviewed by @chinmoy12c. To be merged and tested.

geeky-abhishek commented 1 year ago

It will be closed by today @RyanWalker277

RyanWalker277 commented 1 year ago

Hey @pankajjangid05 @chinmoy12c linking the Pull Requests for the rest of the packages. Please review

samagra-comms / utils