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 E9D74EB64D7 for ; Fri, 30 Jun 2023 08:55:59 +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 561912AC4E for ; Fri, 30 Jun 2023 08:55:59 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 4890B9866FA for ; Fri, 30 Jun 2023 08:55:59 +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 3C10B9866EB; Fri, 30 Jun 2023 08:55:59 +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 291759866EC for ; Fri, 30 Jun 2023 08:55:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: mSaYs6YdMwmJs4W-bsP2_g-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688115349; x=1690707349; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=jWAfKDAGqH59Tt7UHEGY3P+kz8669SVHn8ZpkYsy8uc=; b=hOz0zUxK3VHS80FKbnY4TwTvxasT3+lj8Q3bfsATnkOz/cuvN4hsuhsgE/f0uqv9wC H6l5o4qUhYqKTwRjMkD2ZouHhuWK8Wr9LUzfI3uhgDz+0CgmsBTo/LusWLzap7z724yu nwRI0VCM4hqyzgq4u30bnpiFs2UO/5uUcuYmtwhnQl91eYfWZNnCav7+NXgRTzq6kAyn tbzmZL02ybK481nl3LxUNoJSwhUVFmP55JoVlEu87+NE74Giv8foaQcImkmD1AZbcu0B cXP1qayyc9e64s7bYrgRtkk34dWPAbvr98gi6uS6HCjwWIQX7ikTYU5TP+ybMfcn6eRU tQgA== X-Gm-Message-State: ABy/qLYUo+XuRXsUeLQJeq2idX3tj/z1Ev1bvAte+x2ycASxBQabTjmo BKdIv2TOTmSt3N4uIo6uhagtXBe2Q4h11dbg7Lic8YrKCrTcciYWbrsPrJqfup5jOFW06BBvuaP CJkLCj2iA+ShciF+6Ozf0u3yUo7+R X-Received: by 2002:adf:cd07:0:b0:30f:c012:b529 with SMTP id w7-20020adfcd07000000b0030fc012b529mr2145177wrm.56.1688115349610; Fri, 30 Jun 2023 01:55:49 -0700 (PDT) X-Google-Smtp-Source: APBJJlGSgWoZIeqZLBSPg9AsI/jQEq/L3ZUeVx8I68C2Fn1W+3k0oj0tQ+V37R87xwEKiGiRHEnnKQ== X-Received: by 2002:adf:cd07:0:b0:30f:c012:b529 with SMTP id w7-20020adfcd07000000b0030fc012b529mr2145154wrm.56.1688115349274; Fri, 30 Jun 2023 01:55:49 -0700 (PDT) Date: Fri, 30 Jun 2023 04:55:45 -0400 From: "Michael S. Tsirkin" To: Cornelia Huck Cc: Parav Pandit , "virtio@lists.oasis-open.org" , "virtio-comment@lists.oasis-open.org" , "virtio-dev@lists.oasis-open.org" Message-ID: <20230630045007-mutt-send-email-mst@kernel.org> References: <87edoyqvnu.fsf@redhat.com> <20230407071926-mutt-send-email-mst@kernel.org> <87r0spjct2.fsf@redhat.com> <20230629153345-mutt-send-email-mst@kernel.org> <877crl49qy.fsf@redhat.com> MIME-Version: 1.0 In-Reply-To: <877crl49qy.fsf@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-dev] Re: [virtio-comment] [RFC] virtio 1.3 schedule On Fri, Jun 30, 2023 at 10:47:33AM +0200, Cornelia Huck wrote: > On Thu, Jun 29 2023, "Michael S. Tsirkin" wrote: > > > On Thu, Jun 29, 2023 at 05:41:34PM +0000, Parav Pandit wrote: > >> Hi Cornelia, Michael, > >> > >> > From: virtio-comment@lists.oasis-open.org >> > open.org> On Behalf Of Cornelia Huck > >> > Sent: Wednesday, April 12, 2023 12:17 PM > >> > >> > >> - July 1st 2023: enter feature freeze; all proposed changes must at > >> > >> least have an open github issue that refers to a proposal on-list > >> > >> - August 1st 2023: enter change freeze; everything needs to have been > >> > >> voted upon (i.e. we can start with preparations for a release like > >> > >> compiling the change log) > >> > >> - at the same time, fork virtio-next, which can be used for development > >> > >> while we're working on the release > >> > >> - August/September 2023: prepare draft, initiate initial voting etc. > >> > > > >> > > Hmm looks like you forgot a 30 day the public review period (or is > >> > > that included in the "etc"? ). During this period we will likely > >> > > receive review comments which we have to address. Should the changes > >> > > turn out to be material, another public review period will be required. > >> > > Let's spell it out please. > >> > > >> > Yeah, that's what I meant with "etc"... let's make this: > >> > > >> > - August 2023: prepare draft, aim to have it ready and voted upon by > >> > August 31 the latest (preferrably earlier) > >> > - September 2023: public review period (30 days) > >> > - October 2023: another public review period, if needed; otherwise, get > >> > comittee specification ready and voted upon > >> > - October (maybe November, if we're running late) 2023: virtio 1.3 > >> > released > >> > > >> > The most important dates are feature freeze on Jul 1 and change freeze on Aug > >> > 1, I guess; for the rest, we depend on whether people are out on PTO, which > >> > kind of feedback we get, etc. -- but as long as we release > >> > 1.3 in 2023, I'll be happy enough. > >> > >> We have two extension features that has gone through several reviews and are in advance stage (and also late) for 1.3. :) > >> > >> 1. inner hash v19, rolling to v20 anytime this week. 1 Patch. > >> [1] https://lists.oasis-open.org/archives/virtio-comment/202306/msg00490.html > >> > >> 2. first user of aq for legacy access at v7. > >> 2 patches. First 2 are Fixes. > >> [2] https://lists.oasis-open.org/archives/virtio-comment/202306/msg00491.html > >> > >> Both need few more days of review and vote. > >> Shall we please have few days in July for them so that it can be part of 1.3? > >> or whole July is needed to prepare the draft spec? > > > > I think it's not too bad, projects that do releases every couple of > > months can afford to be strict, we do them ones a year and a half > > it makes sense to be flexible. > > Yes, my only concern is to avoid slipping too badly -- and the "feature > freeze" period was actually intended to give us some time to wrap up > outstanding features. > > For the inner header hash, I see there's already an issue (#173), so > it's good. I have not followed the aq legacy access feature -- if > everyone agrees that we should be able to vote on it in July, we should > have an issue for it as well (I cannot find one just by looking at > titles.) > > Any other features that people are aware of? Was hoping for virtio-can but it looks like it's still in RFC stage. I am guessing the spec should be copied to people who reviewed the driver. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org