W3C home > Mailing lists > Public > public-schemaorg@w3.org > April 2019

Re: Schema.org v3.5 release candidate for review

From: Dan Brickley <danbri@google.com>
Date: Tue, 2 Apr 2019 11:53:14 -0400
Message-ID: <CAK-qy=5ASSPZP=BTS__5VExXu9g3PF09tyDzixy0BLbw4b8nRw@mail.gmail.com>
To: "schema.org Mailing List" <public-schemaorg@w3.org>, St├ęphane Corlosquet <scorlosquet@gmail.com>, Tom Marsh <tmarsh@exchange.microsoft.com>, Vicki Tardif Holland <vtardif@google.com>, Nicolas Torzec <torzecn@oath.com>, Yuliya Tihohod <tilid@yandex-team.ru>, "R.V. Guha" <guha@google.com>
Thanks to everyone who contributed, version 3.5 is published:

(It is dated 2019-04-01 but we actually published today, to spare attentive
readers (hello Aaron...) from agonizing over which definitions might be
April Fool jokes.)

The date also reflects a goal of moving us to monthly releases. I would
like a Schema.org 3.6 release for (Wednesday) May 1st 2019. This means
giving the steering committee and wider community a rough release candidate
~10 business days prior, to ensure review and oversight. Typically we have
also made a few fixes, tweaks and modest additions after that. Maybe we can
tighten up that schedule but I think it's reasonable to aim for a good
sense of how 3.6 looks by April 15th. I have linked a fresh planning issue
from https://github.com/schemaorg/schemaorg/issues/1 for version 3.6, see


On Wed, 20 Mar 2019 at 22:27, Dan Brickley <danbri@google.com> wrote:

> Dear Schema.org Community Group, Steering Group, interested parties,
> Based on discussions here and in Github, here is a
> proposal for a new Schema.org release, version 3.5:
> http://webschemas.org/docs/releases.html#v3.5
> I'd like to aim at publishing this in the first week of April. Bugs,
> mistakes,
> typos, modeling and example improvements and other detailed review
> comments are welcome here or in the issue tracker at
> https://github.com/schemaorg/schemaorg/issues/2052
> cheers,
> Dan
> ps. as usual there are a few pieces of the release that will be put
> together
> at the end (anything involving exact release dates, dated snapshots etc.,
> plus a better release summary and hyperlinking of terms in the release
> notes).
Received on Tuesday, 2 April 2019 15:53:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:46 UTC