search

canonical / kubeflow-rocks

Rocks for Kubeflow components
Apache License 2.0
0 stars 11 forks source link

rocks versioning patterns are inconsistent #23

Closed ca-scribner closed 1 year ago

ca-scribner commented 1 year ago

Nominally, it looks like all rocks say they version with version format: <KF-upstream-version>_<Charmed-KF-version>, but there's disagreement on what <Charmed-KF-version> is. For example:

In my head, I'd also have expected the initial release of Charmed Kubeflow for 1.7 would have been _0 rather than _1, but I don't know if that's something I've seen us use or just something I made up. Might just be my expectation because much of the things we interact with are 0-indexed

i-chvets commented 1 year ago

This issue is from initial ROCKs development workshop. Versioninig has been stadartized and defined in corresponding spec. Closing.