Helm has no existing tracks and the versioning scheme is different from that of k8s so it seems prudent to do this as a new track request and allow for some time for reviewers to request information and cast votes.
I’m also not sure what the release cadence is or whether it is tied to Kubernetes updates. Can you provide some info about this? (if there’s a document with Helm release schedule and versioning, I’m happy to go in for a read).
Hi @roadmr It isn’t tied to k8s releases and I don’t think there is a set cadence. However, with major release 3, this is now really important to get out as releasing Helm 3 to the snap store will break everyone.
I could only find isolated tidbits about Helm versioning and cadence:
Also, Helm 2.14 was released on May 15, 2.15 on October 18th, 2.16 on November 3rd, and 3.0.0 tagged on Nov 13th; the docs state that “Minor releases are for new feature additions that do not break backwards compatibility”; definitely looks like a somewhat in-flux development process which I’m not sure lends itself well to tracks (2.x and 3.x would).
That said, if you’re saying people have experienced problems upgrading, that’s usually a criteria for which we do grant tracks, so I’m reluctantly +1 to grant this request.
We still need at least one more vote from @reviewers on this request.
Indeed: the point of tracks is to serve your needs, not mine; which is why I do agree to have all the tracks to requested even if the release model seems a bit inconsistent. No worries, let’s just wait a few days to see what other reviewers have to say.