Which turns to be a good strategy and allowed us to address some backward compatibility issues with API group addition to 3.6.
-- Michal Fojtik -----Original Message----- From: Clayton Coleman <[email protected]> Reply: Clayton Coleman <[email protected]> Date: April 13, 2017 at 15:13:31 To: Colin Walters <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: Why are most openshift/origin releases on github tagged pre-release? > Just because we waited a bit longer for 1.5 to stabilize. > > > On Apr 13, 2017, at 9:05 AM, Colin Walters wrote: > > > > Under https://github.com/openshift/origin/releases > > it looks like there was never a "non-prerelease" 1.5. Now we're > > on the train to 3.6 (which makes sense to me). > > > > Currently in Fedora, all versions are 1.4: > > https://bodhi.fedoraproject.org/updates/?packages=origin > > The CentOS PaaS SIG built 1.5rc: > > http://cbs.centos.org/koji/buildinfo?buildID=16916 > > > > I'd like to update Fedora at least since I really want a lot > > of the enhancements in `oc cluster up` lately. But what > > should I update it to? I guess we should at least match > > the PaaS SIG version, but I'm wondering whether Fedora > > should just start tracking the 3.6 alphas? > > > > _______________________________________________ > > dev mailing list > > [email protected] > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
