Hide Forgot
Description of problem: Currently, Oz requires an update any time a new OS minor version is released. Perhaps instead of enabling each release individually, the ones that need a special case should be handled as needed? And handle the others with sane defaults? I think that would make for less (unnecessary) updates to Oz, and allow testing to occur easily ahead of time to find out if something does indeed need to be a special case. Version-Release number of selected component (if applicable): oz-0.8.0-4.el6.noarch How reproducible: Always Steps to Reproduce: 1. As of now, try to install RHEL 5.8. It fails.
With the exception of EC2 which requires an errata update to the jeos image rpms. We need to be able to qualify upcoming releases of RHEL as a client in cloud forms. So we're hoping that private providers like vsphere and rhevm can build upcoming releases. Thanks
moving version to 1.0.0 . version = found in version
Ian, can you comment please? Wes is suggesting that an errata should only be required to build RHEL for public providers. If this is easy, please dev-ack and fix; if not please move to 1.1.0.
Moving to 1.1.0.
Moving to 2.0.0? for consideration.
I agree that having to update Oz for every minor release isn't ideal. The reason we have to update Oz for every Fedora release is that anaconda frequently makes backwards-incompatible changes that require code changes. For RHEL, this is much less of a worry. In fact, as it currently stands I have no known cases of RHEL breaking anaconda within a stable release series. I would certainly accept patches that made this "just work" for RHEL, without any further Oz updates. Chris