* [virtio-comment] [virtio 1.3] Feature freeze has started
@ 2023-07-03 12:41 ` Cornelia Huck
0 siblings, 0 replies; 6+ messages in thread
From: Cornelia Huck @ 2023-07-03 12:41 UTC (permalink / raw)
To: virtio; +Cc: virtio-comment, virtio-dev
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
as part of the release process for the 1.3 version of the virtio spec,
we have now entered feature freeze. This means:
***
By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
to have at least a github issue open that is pointing to a patch (set)
on the list.
***
AFAICS, the list of features matching these criteria is the following:
https://github.com/oasis-tcs/virtio-spec/issues/173 ("virtio-net:
support inner header hash")
* this looks very close, with voting likely to start in the next
couple of days
https://github.com/oasis-tcs/virtio-spec/issues/167 ("Support
transitional device for PCIe VF")
* I have not followed that one in detail, but it has been stated that
this one should also be ready soon -- can people please confirm that
this will be ready for inclusion in July?
https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
negotiated.")
* Can someone please check the status of this? Looks like a patch is
available, but no progress for a long time? Is this maybe interacting
with the inner header hash feature?
Any others that I have missed?
I'd like to wrap this up in July; not a real problem if we spill over
a couple of days into August, but I'd really like to avoid delaying the
process for too much (it will take long enough already.)
virtio 1.3 timeline:
Development
July 3rd: feature freeze (github issue <-- we are here
and change on list)
August 1st: change freeze (all voted
upon)
virtio-next development branch opens
August: prepare draft
August 31st (latest): draft voted upon by TC
September: public review period
October: addtl public review period, if needed
October (November): 1.3 released
merge virtio-next development branch
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
^ permalink raw reply [flat|nested] 6+ messages in thread
* [virtio-dev] [virtio 1.3] Feature freeze has started
@ 2023-07-03 12:41 ` Cornelia Huck
0 siblings, 0 replies; 6+ messages in thread
From: Cornelia Huck @ 2023-07-03 12:41 UTC (permalink / raw)
To: virtio; +Cc: virtio-comment, virtio-dev
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
as part of the release process for the 1.3 version of the virtio spec,
we have now entered feature freeze. This means:
***
By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
to have at least a github issue open that is pointing to a patch (set)
on the list.
***
AFAICS, the list of features matching these criteria is the following:
https://github.com/oasis-tcs/virtio-spec/issues/173 ("virtio-net:
support inner header hash")
* this looks very close, with voting likely to start in the next
couple of days
https://github.com/oasis-tcs/virtio-spec/issues/167 ("Support
transitional device for PCIe VF")
* I have not followed that one in detail, but it has been stated that
this one should also be ready soon -- can people please confirm that
this will be ready for inclusion in July?
https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
negotiated.")
* Can someone please check the status of this? Looks like a patch is
available, but no progress for a long time? Is this maybe interacting
with the inner header hash feature?
Any others that I have missed?
I'd like to wrap this up in July; not a real problem if we spill over
a couple of days into August, but I'd really like to avoid delaying the
process for too much (it will take long enough already.)
virtio 1.3 timeline:
Development
July 3rd: feature freeze (github issue <-- we are here
and change on list)
August 1st: change freeze (all voted
upon)
virtio-next development branch opens
August: prepare draft
August 31st (latest): draft voted upon by TC
September: public review period
October: addtl public review period, if needed
October (November): 1.3 released
merge virtio-next development branch
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* [virtio-comment] Re: [virtio-dev] [virtio 1.3] Feature freeze has started
2023-07-03 12:41 ` [virtio-dev] " Cornelia Huck
@ 2023-07-21 13:08 ` Cornelia Huck
-1 siblings, 0 replies; 6+ messages in thread
From: Cornelia Huck @ 2023-07-21 13:08 UTC (permalink / raw)
To: virtio; +Cc: virtio-comment, virtio-dev
On Mon, Jul 03 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> As outlined in
> https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
> as part of the release process for the 1.3 version of the virtio spec,
> we have now entered feature freeze. This means:
>
> ***
> By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
> to have at least a github issue open that is pointing to a patch (set)
> on the list.
> ***
>
> AFAICS, the list of features matching these criteria is the following:
>
> https://github.com/oasis-tcs/virtio-spec/issues/173 ("virtio-net:
> support inner header hash")
> * this looks very close, with voting likely to start in the next
> couple of days
>
> https://github.com/oasis-tcs/virtio-spec/issues/167 ("Support
> transitional device for PCIe VF")
> * I have not followed that one in detail, but it has been stated that
> this one should also be ready soon -- can people please confirm that
> this will be ready for inclusion in July?
>
> https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
> virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
> negotiated.")
> * Can someone please check the status of this? Looks like a patch is
> available, but no progress for a long time? Is this maybe interacting
> with the inner header hash feature?
>
> Any others that I have missed?
Last call for 1.3. The first two are done now, the third one has not
seen any action, so if anything, it's going to be post-1.3.
I think we're good (and can start preparing for the next steps).
>
> I'd like to wrap this up in July; not a real problem if we spill over
> a couple of days into August, but I'd really like to avoid delaying the
> process for too much (it will take long enough already.)
>
> virtio 1.3 timeline:
>
> Development
>
> July 3rd: feature freeze (github issue <-- we are here
> and change on list)
>
> August 1st: change freeze (all voted
> upon)
>
> virtio-next development branch opens
>
> August: prepare draft
>
> August 31st (latest): draft voted upon by TC
>
> September: public review period
>
> October: addtl public review period, if needed
>
> October (November): 1.3 released
>
> merge virtio-next development branch
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [virtio-dev] [virtio 1.3] Feature freeze has started
@ 2023-07-21 13:08 ` Cornelia Huck
0 siblings, 0 replies; 6+ messages in thread
From: Cornelia Huck @ 2023-07-21 13:08 UTC (permalink / raw)
To: virtio; +Cc: virtio-comment, virtio-dev
On Mon, Jul 03 2023, Cornelia Huck <cohuck@redhat.com> wrote:
> As outlined in
> https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
> as part of the release process for the 1.3 version of the virtio spec,
> we have now entered feature freeze. This means:
>
> ***
> By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
> to have at least a github issue open that is pointing to a patch (set)
> on the list.
> ***
>
> AFAICS, the list of features matching these criteria is the following:
>
> https://github.com/oasis-tcs/virtio-spec/issues/173 ("virtio-net:
> support inner header hash")
> * this looks very close, with voting likely to start in the next
> couple of days
>
> https://github.com/oasis-tcs/virtio-spec/issues/167 ("Support
> transitional device for PCIe VF")
> * I have not followed that one in detail, but it has been stated that
> this one should also be ready soon -- can people please confirm that
> this will be ready for inclusion in July?
>
> https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
> virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
> negotiated.")
> * Can someone please check the status of this? Looks like a patch is
> available, but no progress for a long time? Is this maybe interacting
> with the inner header hash feature?
>
> Any others that I have missed?
Last call for 1.3. The first two are done now, the third one has not
seen any action, so if anything, it's going to be post-1.3.
I think we're good (and can start preparing for the next steps).
>
> I'd like to wrap this up in July; not a real problem if we spill over
> a couple of days into August, but I'd really like to avoid delaying the
> process for too much (it will take long enough already.)
>
> virtio 1.3 timeline:
>
> Development
>
> July 3rd: feature freeze (github issue <-- we are here
> and change on list)
>
> August 1st: change freeze (all voted
> upon)
>
> virtio-next development branch opens
>
> August: prepare draft
>
> August 31st (latest): draft voted upon by TC
>
> September: public review period
>
> October: addtl public review period, if needed
>
> October (November): 1.3 released
>
> merge virtio-next development branch
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: [virtio-comment] Re: [virtio-dev] [virtio 1.3] Feature freeze has started
2023-07-21 13:08 ` Cornelia Huck
@ 2023-07-21 14:21 ` Parav Pandit
-1 siblings, 0 replies; 6+ messages in thread
From: Parav Pandit @ 2023-07-21 14:21 UTC (permalink / raw)
To: Cornelia Huck, virtio@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Cornelia Huck
> Sent: Friday, July 21, 2023 9:09 AM
> > https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
> > virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
> > negotiated.")
> > * Can someone please check the status of this? Looks like a patch is
> > available, but no progress for a long time? Is this maybe interacting
> > with the inner header hash feature?
> >
> > Any others that I have missed?
>
> Last call for 1.3. The first two are done now, the third one has not seen any
> action, so if anything, it's going to be post-1.3.
>
> I think we're good (and can start preparing for the next steps).
>
Yes, we can do post 1.3.
The fix needs more words than what was posted. I will post one when the branch opens.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
^ permalink raw reply [flat|nested] 6+ messages in thread
* [virtio-dev] RE: [virtio-comment] Re: [virtio-dev] [virtio 1.3] Feature freeze has started
@ 2023-07-21 14:21 ` Parav Pandit
0 siblings, 0 replies; 6+ messages in thread
From: Parav Pandit @ 2023-07-21 14:21 UTC (permalink / raw)
To: Cornelia Huck, virtio@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Cornelia Huck
> Sent: Friday, July 21, 2023 9:09 AM
> > https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
> > virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
> > negotiated.")
> > * Can someone please check the status of this? Looks like a patch is
> > available, but no progress for a long time? Is this maybe interacting
> > with the inner header hash feature?
> >
> > Any others that I have missed?
>
> Last call for 1.3. The first two are done now, the third one has not seen any
> action, so if anything, it's going to be post-1.3.
>
> I think we're good (and can start preparing for the next steps).
>
Yes, we can do post 1.3.
The fix needs more words than what was posted. I will post one when the branch opens.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-21 14:21 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-07-03 12:41 [virtio-comment] [virtio 1.3] Feature freeze has started Cornelia Huck
2023-07-03 12:41 ` [virtio-dev] " Cornelia Huck
2023-07-21 13:08 ` [virtio-comment] " Cornelia Huck
2023-07-21 13:08 ` Cornelia Huck
2023-07-21 14:21 ` [virtio-comment] " Parav Pandit
2023-07-21 14:21 ` [virtio-dev] " Parav Pandit
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.