From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9A884EB64DC for ; Mon, 3 Jul 2023 12:41:37 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id B7F8B120D44 for ; Mon, 3 Jul 2023 12:41:36 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id A1CEF986555 for ; Mon, 3 Jul 2023 12:41:36 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 8B0F098644C; Mon, 3 Jul 2023 12:41:36 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 76CEF986460 for ; Mon, 3 Jul 2023 12:41:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: hrgMTwnZMv6G1PhvSbrnPA-1 From: Cornelia Huck To: virtio@lists.oasis-open.org Cc: virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org Organization: Red Hat GmbH User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Mon, 03 Jul 2023 14:41:32 +0200 Message-ID: <874jml2mmb.fsf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: [virtio-dev] [virtio 1.3] Feature freeze has started 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