OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [virtio] [PATCH v2 09/17] charter: update on deliverables


On Mon, Feb 08, 2021 at 10:41:57PM +0100, Halil Pasic wrote:
> On Mon, 8 Feb 2021 07:16:05 -0500
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > we don't have multiple documents.
> > we expect to deliver specifications periodically.
> > 
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >  charter.html | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/charter.html b/charter.html
> > index f3a34f3..e3c8cf6 100644
> > --- a/charter.html
> > +++ b/charter.html
> > @@ -101,7 +101,7 @@
> >          </li>
> >        </ol>
> >        <p>
> > -        We anticipate deliverables (1) and (2) to be a single work, and (3) and (4) to be separate works. The projected delivery dates are 12 to 16 months after the first meeting.
> > +        The projected delivery dates for the specifications are every 12 to 16 months.
> 
> Maybe we could explain that we disseminate all deliverable in a single
> document. I.e. how about:
> 
> All the above listed deliverables are expected to continue to
> be disseminated together as a single document called "Virtual I/O
> Device (VIRTIO)", with projected delivery period of 12 to 16
> months per release.


Don't really see a reason to nail us to a specific split up
in the charter. E.g. if we finally get around to create and
upload example code, it might make sense as a separate
file that can actually be compiled.

> >        </p>
> >      </li>
> >      <li>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]