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

Github issue tracker - wrapping up for sdo-gozer release

From: Dan Brickley <danbri@google.com>
Date: Tue, 21 Apr 2015 21:56:07 +0100
Message-ID: <CAK-qy=4k_VsrAUwvC5_b7V51WqH+dAF0Ad4nXpanJvFmZxM+Gw@mail.gmail.com>
To: public-schemaorg@w3.org
Checking https://lists.w3.org/Archives/Public/public-schemaorg it is
clear that most of the activities towards our next schema.org release
are (as planned!) happening over in Github and the Community Group
list discussion here so far has focussed on other topics. So I thought
I ought to send a quick update here (as well as a reminder that a
Github.com account is very useful for participating more fully in

The next release is code-named sdo-gozer ("sdo" stands for
schema.org). We use these (Ghostbusters-inspired) names for Git(hub)
work-in-progress branches and for test versions of the site published
on appspot.com.

For info, https://github.com/schemaorg/schemaorg/issues/418 is a
meta-bug with a l reasonable annotated listing of gozer-related
issues. See also Vicki's doc about possible renamings of terms that
have very generic or confusing names,
https://github.com/schemaorg/schemaorg/issues/417 (the specific list
there was intended a conversation starter).

The build of the site visible on sdo-gozer.appspot.com is based on the
work-in-progress sdo-gozer branch within Github, i.e. this will become
the candidate next release soon. A good entry point is the draft new
version of the /docs/releases.html page, i.e.

You can filter Github by milestone and label. At this time filtering
on Gozer release and 'schema.org vocab' provides a useful status


This currently reveals 24 open issues, which need analysis, agreement
and closure (or postponing to a future release). Do please take a look
at the discussions and jump in with any observations and proposals
that you think can help progress things. While there are also some
software fixes in progress (sdo-scripts branch), we are optimistic
that this next release can be wrapped up within days rather than
weeks. If comments in Github can be made in the spirit of resolving
(or resolving to postpone) issues rather than opening, broadening or
prolonging discussion that would be super helpful!


Received on Tuesday, 21 April 2015 20:56:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 April 2015 20:56:35 UTC