From: Julien Grall <julien@xen.org>
To: George Dunlap <george.dunlap@cloud.com>,
Yann Dirson <yann.dirson@vates.tech>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Lunfan Zhang <Lunfan.Zhang@citrix.com>,
Xihuan Yang <xihuan.yang@citrix.com>,
dpsmith@apertussolutions.com, marmarek@invisiblethingslab.com
Subject: Re: Next steps for Rust guest agent
Date: Thu, 1 Feb 2024 16:57:04 +0000 [thread overview]
Message-ID: <9e01b86e-e3d2-4eec-93ed-e8828375bb30@xen.org> (raw)
In-Reply-To: <CA+zSX=Yu_Epi6fge71iQNkecYOn92XO4KzwRtQNfrchtMaCxzw@mail.gmail.com>
Hi George,
On 01/02/2024 16:55, George Dunlap wrote:
> On Thu, Jan 11, 2024 at 12:27 PM Yann Dirson <yann.dirson@vates.tech> 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
next prev parent reply other threads:[~2024-02-01 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 9:38 Next steps for Rust guest agent Yann Dirson
2024-01-11 12:27 ` Yann Dirson
2024-02-01 16:55 ` George Dunlap
2024-02-01 16:57 ` Julien Grall [this message]
2024-02-01 17:01 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e01b86e-e3d2-4eec-93ed-e8828375bb30@xen.org \
--to=julien@xen.org \
--cc=Lunfan.Zhang@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=george.dunlap@cloud.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xihuan.yang@citrix.com \
--cc=yann.dirson@vates.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.