Just to make sure I'm clear on what you're saying here... the docker images
for these components will have tags that are updated as changes are made to
master. At some point, when we consider code "released", git tags will be
created, and at that point the corresponding docker image tags should
remain static. Right?
Curious, would we do this with alpha release tags as well or will those
continue to be one-shot releases? Or maybe just go away?
On Fri, Feb 2, 2018 at 1:44 AM, Clayton Coleman wrote:
> Due to much popular demand and a desire to use this for rolling updates of
> cluster components, we have started publishing vX.Y and vX.Y.Z tags for
> origin, the registry, and logging and metrics.
>
> So by end of day tomorrow you should see v3.9 and v3.9.0 tags for all
> OpenShift components. These tags are for pre-release code and are updated
> on every merge to master - we will roll them the entire release, and when
> we cut for v3.9.1 we'll immediately start tagging from master to the v3.9.1
> tag. 3.10 will start immediately after the release branch is cut for 3.9.
>
> As a user, you should only switch to a rolling tag once it's been
> "released" (a git tag exists) if you want to have a fully stable experience.
>
> oc cluster up and the image behavior will not be updated until we've had
> time to assess the impact of changing, although if you run "oc cluster up
> --version=v3.9" I would hope it would work.
>
> Stay tuned for more on autoupdating of cluster components.
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
