<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 29, 2016 at 6:33 PM, Sven Kieske <span dir="ltr"><<a href="mailto:s.kieske@mittwald.de" target="_blank">s.kieske@mittwald.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 29/11/16 15:54, Martin Sivak wrote:<br>
> I actually checked the oVirt 4.0.0 and 4.0.5 release notes and I do<br>
> not see anything mentioning ovirt-cli or REST v3 deprecation. This<br>
> will (removal of RESTv3 support) affect the optimizer and quite<br>
> possibly even hosted engine setup.<br>
<br>
</span>Hi,<br>
<br>
this seems to indicate that even core ovirt devs do not<br>
know about every feature which gets deprecated.<br>
<br>
Maybe this could be solved by sandro's suggestion<br>
to at least create an BZ for each deprecation.<br></blockquote><div><br></div><div>Makes sense, even as a Tracker BZ, because there's the work to remove the code, and it might be in several components, as well as Documentation.</div><div>Y.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I would agree with that, but also like to propose<br>
an alternative way, because at the stage of bug creation<br>
the deprecation is already set in stone and can't be discussed further<br>
(I fear).<br>
<br>
So my proposal would be to mail to the devel list at least<br>
the proposal: "I/we want to get rid of feature/implementation X, use Z<br>
instead".<br>
<br>
This would give developers and users enough time to engage with the<br>
community, replacing dependencies or start a discussion if removal can't<br>
be done later.<br>
<br>
A clear deprecation guideline would also be helpful, I guess.<br>
<br>
Something like: Features will get marked as deprecated in release X.Y<br>
and removed in X.Y+2 (or whatever number you might chose).<br>
<br>
This would allow for much better preparation in the community and lead<br>
to less unpleasant surprises.<br>
<br>
HTH & keep up the good work!<br>
<br>
--<br>
Mit freundlichen Grüßen / Regards<br>
<br>
Sven Kieske<br>
<br>
Systemadministrator<br>
Mittwald CM Service GmbH & Co. KG<br>
Königsberger Straße 6<br>
32339 Espelkamp<br>
T: <a href="tel:%2B495772%20293100" value="+495772293100">+495772 293100</a><br>
F: <a href="tel:%2B495772%20293333" value="+495772293333">+495772 293333</a><br>
<a href="https://www.mittwald.de" rel="noreferrer" target="_blank">https://www.mittwald.de</a><br>
Geschäftsführer: Robert Meyer<br>
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen<br>
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen<br>
<br>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div></div>