[Feature] Revamp version management

[daw3rd]

Search before asking

• I searched the issues and found no similar issues.

Component

Other

Feature

We would like to allow transforms to manage their micro version numbers independently of the core libraries. With this in mind, we have the following:

Guiding principals/goals

1. github "releases" will be published to a new minor (not micro) version number. For example, 0.3.0
2. when there is a github release, we will publish pypi wheels and images
3. transforms can increment the micro version independently of the core library version and formal github release
4. We will (for now) keep the dev suffix, until we decide we can live w/o it.
5. It is ok and expected to republish a transform at a new minor version that may be the same functionally as the previous version (i.e 0.3.0 and 0.2.9)
6. Transforms can define dependencies on DPK in pypi or in the repo source (choice is already supported today via USE_REPO_LIB_SRC in .make.defaults)

TODOs:

1. Transform version numbers need to be pushed down from .make.versions to a transform-specific location (i.e. transforms/noop/version)
2. make set-versions neeeds to still work through the repo to reset to a new minor version (i.e. 0.3.0) (and be extended to work on transform's version file)
3. Update release-branch.sh script to bump minor version numbers instead of micro.
4. Update RELEASE.md to capture these goals and changes.

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[daw3rd]

Closing as duplicate of #639