There has been some discussion recently about changing the release numbers of Origin so that they line up with the "actual" OpenShift release history. When we reset the numbers to 1.0 for OpenShift 3 on top of Kubernetes, we did so to ensure we clearly identified for the open source community which Kube release we were pairing with.
Now that Kube is more stable and we are taking some of the first steps upstream to ensure OpenShift can run on top of Kube (vs embedding it), a few of us have discussed how we can simplify the release process for OpenShift to reduce "pointless" inefficiencies. One of the suggestions has been to align the Origin release numbers (currently 1.5) with the OpenShift Container Platform numbering (currently 3.5), which mirrors the full lifecycle of OpenShift (going back to 2011). This would: * simplify packaging and tagging (one spec file and process) * reduce complexity in Ansible (we do quite a bit of version trickery) * simplify the tagging process * get Origin documentation aligned and reduce confusion when we describe openshift 2 vs 3 * better testing of issues that apply to version numbers * prevent needless confusion converting units (don't want to crash into mars) * avoid any future overlap in numbers The various release team members from the PaaS SiG and the Origin team agree this would be a good long term step, but I wanted to get feedback from the community first. The change would be that OpenShift Origin 1.5 would be immediately followed by OpenShift Origin 3.6. We would also likely alter the CentOS RPM repos so they align with the versioned structure we use in OCP (https://centos.org/.../release-1.5, release-3.6) which will also help simplify testing packages in Ansible. Other version numbers would align. Is there anyone using Origin that thinks they might be impacted by this, in terms of release packaging, automation, or tooling? Any concerns? Enthusiasm? Fear? Total satisfaction? _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
