On 05/02/2018 17:57, Halil Pasic wrote: >> This is certainly not how we did it for v1.0, and not how >> oasis process works generally. Implementations are required >> to move to an oasis standard change. We are working on >> a committee standard deliverables. >> >> I don't yet plan to work on an implementation yet: it's a bit of a >> chicked and egg problem. People are reluctant to work on what's not in >> the spec. We can always make changes as long as there are no >> implementations. >> > 'We can always make changes as long as there are no implementations' > comes very surprising to me. I believed, once a committee specification > is released the requirements for changes are given, and don't depend > on known implementations. > > Does this imply that one should be reluctant about implementing > a virtio specification that still has no implementation (because it ain't > stable, and may change, because there is no implementation yet)?
I agree that this doesn't seem optimal. This is a much bigger change than anything between virtio 0.9 and in virtio 1.0, because it affects the data path directly. Paolo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
