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 lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (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 99492C48286 for ; Thu, 1 Feb 2024 16:57:22 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.674560.1049590 (Exim 4.92) (envelope-from ) id 1rVaNC-0003yW-7o; Thu, 01 Feb 2024 16:57:10 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 674560.1049590; Thu, 01 Feb 2024 16:57:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rVaNC-0003yP-4m; Thu, 01 Feb 2024 16:57:10 +0000 Received: by outflank-mailman (input) for mailman id 674560; Thu, 01 Feb 2024 16:57:08 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rVaNA-0003yH-Qi for xen-devel@lists.xenproject.org; Thu, 01 Feb 2024 16:57:08 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rVaN8-0005Gl-Px; Thu, 01 Feb 2024 16:57:06 +0000 Received: from [15.248.2.31] (helo=[10.24.67.35]) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1rVaN8-0003uN-HP; Thu, 01 Feb 2024 16:57:06 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID; bh=qgZJCfdLDu8JYR0LsPiclE/eQBuhsWgYjnA8lKA8aOc=; b=Zg5EhqUmnKmEqg2nTWgRTCi6UC wTGtaWHah0fwFn+1OvePB8NU//0FkGY37MzQ+VOaDMe8Mc+eZfwssbG6LaqALzzpPesRvc44gKYgV T/S2Je17Ry9N4/e3LpE19WyVFrQmAR1EqD0++8rRVao7eQLHH1tWKwl5+9KjFDyBYMeg=; Message-ID: <9e01b86e-e3d2-4eec-93ed-e8828375bb30@xen.org> Date: Thu, 1 Feb 2024 16:57:04 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Next steps for Rust guest agent Content-Language: en-GB To: George Dunlap , Yann Dirson Cc: xen-devel@lists.xenproject.org, Andrew Cooper , Jan Beulich , Stefano Stabellini , Wei Liu , Lunfan Zhang , Xihuan Yang , dpsmith@apertussolutions.com, marmarek@invisiblethingslab.com References: <1be8f6f1-f977-4743-bd26-362ada960dc6@vates.tech> From: Julien Grall In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi George, On 01/02/2024 16:55, George Dunlap wrote: > On Thu, Jan 11, 2024 at 12:27 PM Yann Dirson wrote: >>> - what should be the criteria to advertise it as official Xenproject >>> guest agent ? >> >> What do people think here? > > As we discussed at the community call, I think that we should > basically set a date at which we consider this the official Xen > Project guest agent. Anyone who wants to have input can give it > before then. Then once you guys think it's ready, we can start to > "market" it to the distros. +1 > > Shall we say 29 February, 8 weeks from now? This is 4 weeks away. I am fine with that, but checking this is the date you intended to set. Cheers, -- Julien Grall