So there is no v3.8 version? ________________________________ 发件人: dev-boun...@lists.openshift.redhat.com <dev-boun...@lists.openshift.redhat.com> 代表 dev-requ...@lists.openshift.redhat.com <dev-requ...@lists.openshift.redhat.com> 发送时间: 2018年2月3日 1:00 收件人: dev@lists.openshift.redhat.com 主题: dev Digest, Vol 71, Issue 1
Send dev mailing list submissions to dev@lists.openshift.redhat.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.openshift.redhat.com/openshiftmm/listinfo/dev or, via email, send a message with subject or body 'help' to dev-requ...@lists.openshift.redhat.com You can reach the person managing the list at dev-ow...@lists.openshift.redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of dev digest..." Today's Topics: 1. New rolling pre-release tags for Origin v3.9 (Clayton Coleman) ---------------------------------------------------------------------- Message: 1 Date: Fri, 2 Feb 2018 01:44:07 -0500 From: Clayton Coleman <ccole...@redhat.com> To: dev <dev@lists.openshift.redhat.com> Subject: New rolling pre-release tags for Origin v3.9 Message-ID: <CAH16ShLYRMpgD6CcA94om20uwJ=cpuxwy1ywipcnlhrdjye...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openshift.redhat.com/openshift-archives/dev/attachments/20180202/66a94a90/attachment.html> ------------------------------ _______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev End of dev Digest, Vol 71, Issue 1 **********************************
_______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev