Re: [ovirt-devel] [RFC] Communicating within the community [was Re: [ovirt-users] I wrote an oVirt thing]

[Yaniv Kaul]

On Tue, Nov 29, 2016 at 6:33 PM, Sven Kieske  wrote:

> On 29/11/16 15:54, Martin Sivak wrote:
> > I actually checked the oVirt 4.0.0 and 4.0.5 release notes and I do
> > not see anything mentioning ovirt-cli or REST v3 deprecation. This
> > will (removal of RESTv3 support) affect the optimizer and quite
> > possibly even hosted engine setup.
>
> Hi,
>
> this seems to indicate that even core ovirt devs do not
> know about every feature which gets deprecated.
>
> Maybe this could be solved by sandro's suggestion
> to at least create an BZ for each deprecation.
>

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.
Y.


> I would agree with that, but also like to propose
> an alternative way, because at the stage of bug creation
> the deprecation is already set in stone and can't be discussed further
> (I fear).
>
> So my proposal would be to mail to the devel list at least
> the proposal: "I/we want to get rid of feature/implementation X, use Z
> instead".
>
> This would give developers and users enough time to engage with the
> community, replacing dependencies or start a discussion if removal can't
> be done later.
>
> A clear deprecation guideline would also be helpful, I guess.
>
> Something like: Features will get marked as deprecated in release X.Y
> and removed in X.Y+2 (or whatever number you might chose).
>
> This would allow for much better preparation in the community and lead
> to less unpleasant surprises.
>
> HTH & keep up the good work!
>
> --
> Mit freundlichen Grüßen / Regards
>
> Sven Kieske
>
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +495772 293100
> F: +495772 29
> 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
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [RFC] Communicating within the community [was Re: [ovirt-users] I wrote an oVirt thing]

[Sven Kieske]

On 29/11/16 15:54, Martin Sivak wrote:
> I actually checked the oVirt 4.0.0 and 4.0.5 release notes and I do
> not see anything mentioning ovirt-cli or REST v3 deprecation. This
> will (removal of RESTv3 support) affect the optimizer and quite
> possibly even hosted engine setup.

Hi,

this seems to indicate that even core ovirt devs do not
know about every feature which gets deprecated.

Maybe this could be solved by sandro's suggestion
to at least create an BZ for each deprecation.

I would agree with that, but also like to propose
an alternative way, because at the stage of bug creation
the deprecation is already set in stone and can't be discussed further
(I fear).

So my proposal would be to mail to the devel list at least
the proposal: "I/we want to get rid of feature/implementation X, use Z
instead".

This would give developers and users enough time to engage with the
community, replacing dependencies or start a discussion if removal can't
be done later.

A clear deprecation guideline would also be helpful, I guess.

Something like: Features will get marked as deprecated in release X.Y
and removed in X.Y+2 (or whatever number you might chose).

This would allow for much better preparation in the community and lead
to less unpleasant surprises.

HTH & keep up the good work!

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +495772 293100
F: +495772 29
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



signature.asc
Description: OpenPGP digital signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [RFC] Communicating within the community [was Re: [ovirt-users] I wrote an oVirt thing]

[Martin Sivak]

I actually checked the oVirt 4.0.0 and 4.0.5 release notes and I do
not see anything mentioning ovirt-cli or REST v3 deprecation. This
will (removal of RESTv3 support) affect the optimizer and quite
possibly even hosted engine setup.

Martin

On Tue, Nov 29, 2016 at 3:26 PM, Sandro Bonazzola  wrote:
> Moving to devel since this needs developer attention
>
> On Tue, Nov 29, 2016 at 2:50 PM, Logan Kuhn  wrote:
>>
>> Is this something that was officially announced and I've missed?  This is
>> the first time I'm hearing about the removal of the cli
>>
>
> I tend to agree with Logan here, we have a lack of communication on what's
> going on.
> We haven't weekly status meetings anymore, the experiment on office hours
> didn't work and progress reports to mailing lists are not sent anymore.
> We need to rethink the way we propagate information.
>
> Up to now the only way we have to give info on coming deprecation is the
> release notes page which is built from bugzilla doctext so if no other way
> is used to communicate changes, at least please use a bug.
>
>
>>
>> Regards,
>> Logan
>>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [RFC] Communicating within the community [was Re: [ovirt-users] I wrote an oVirt thing]

[Sandro Bonazzola]

Moving to devel since this needs developer attention

On Tue, Nov 29, 2016 at 2:50 PM, Logan Kuhn  wrote:

> Is this something that was officially announced and I've missed?  This is
> the first time I'm hearing about the removal of the cli
>
>
I tend to agree with Logan here, we have a lack of communication on what's
going on.
We haven't weekly status meetings anymore, the experiment on office hours
didn't work and progress reports to mailing lists are not sent anymore.
We need to rethink the way we propagate information.

Up to now the only way we have to give info on coming deprecation is the
release notes page which is built from bugzilla doctext so if no other way
is used to communicate changes, at least please use a bug.



> Regards,
> Logan
>
>
-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel