[ovirt-users] qemu-kvm-rhev on EL machines for oVirt 3.4.z ?

[Sven Kieske]

On 11/09/14 14:02, Dan Kenigsberg wrote:
> The purpose of this thread is to solicit objections to
> apossibly-distruptive change in a stable branch, not to disparage
> non-conventional deployments.

well you already did disparage non-conventional deployments in the past
e.g. users using json over rest api in 3.3.z need to adjust stuff
because during 3.4.z cycle it was communicated that the 3.3.z json api
was not "officially" released at the time and therefore was
altered in 3.4. (somehow it was forgotten to announce this during the
3.3. cycle..)

> If no one raises a serious objection, we can require qemu-kvm-rhev right
> after ovirt-3.4.4 is out.

so this is really strange:

for some stuff, you support or want to support deployments which where
never supported (the install guides are quite verbose about how to
install, and they all use the ovirt repos, none uses local install)
and on the other hand, you break compatibility with a previous release
when it was never documented that this feature was _not_ officially
released.


Again: How many deployments do you think would suffer from a new qemu
package shipped by ovirt repo?

This was also altered in the past, e.g. with epel, gluster and
jpackage repo added during the releases.

Furthermore there are regression bugs which sat there for a while
until the release was not supported anymore, fortunately this bug
was not found in the next release, so no one fixed it, e.g.:

https://bugzilla.redhat.com/show_bug.cgi?id=1120267


To make this clear: I don't need qemu-kvm-rhev myself

I just think the project needs to make a clear guideline
what gets changed at what point in the release process and then
follow this rules _always_ .

I still have evidence (see above) that this is not always the case.
So I hope you will strive for a more consistent release process (I know
you do).
The last document from Sandro regarding the new release process looks
promising.

I appreciate you took this topic to the mailing list
and I hope my opinion doesn't sound to harsh. If there are errors
above, please feel free to correct me. :)

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen