Release History and Planning
danbri opened this issue · 2 comments
Issue #1 tracks high-level plans for schema.org. It gives entry points for release-level issues as well as broader goals that correspond to rough milestones over the next year. In practice, these goals are pretty hit-and-miss w.r.t. people actually doing the necessary work, but they are reported here as aspirations and for discussion.
See also release history and draft next release.
Release plans
- 14.0 #3017 [2022-01-xx]
- 13.0 #2884 [2021-07-07]
- 12.0 #2813 [2021-02-12]
- 11.0 #2768 [released 2020-11-30]
- 10.0 #2648 [released 2020-09-08]
- 9.0 #2634 [released 2020-07-21]
- 8.0 #2528 [released 2020-05-01]
- 7.0 #2453 [rapid releases of 7.0, 7.01 ... 7.04]
- 6.0 #2376 [expected 2019-12-01]
- 5.0 #2370 [expected 2019-11-07]
- 4.0 #2363 [release 2019-10-15]
- 3.9 #2306 [release 2019-08-01]
- 3.8 #2272 [release 2019-07-01]
- 3.7 #2239 [release 2019-06-01]
- 3.6 #2193 [release 2019-05-01]
- 3.5 #2052 [release 2019-04-01]
- 3.4 #1891 [release 2018-06-15]
- 3.3 #1569
- 3.2 sdo-callisto - detailed in #1292 - [release 2017-03-23]
- 3.1 sdo-makemake - detailed in #1212 - release 2016-08-09
- 3.0 sdo-deimos - detailed in #911 - release 2016-05-04
- 2.2 sdo-phobos - detailed in #827 - released 2015-11-05
- 2.1 sdo-ganymede - detailed in #510 - released 2015-08-07 (mail thread)
- 2.0 sdo-gozer - detailed in #418 released 2015-05-12
Issues Overview
We label issues by topic, workflow status. The most concrete milestone is the next upcoming release, which since April 2019 are monthly, officially on (and named for) the 1st of the month, but in practice released on the first working day following. Work in progress edits can be found on webschemas.org.
We try to avoid unlabelled issues. The most important labels and entry points are:
- Vocabulary issues - additions, cleanup, clarification and integration; there are various supporting labels to distinguish enhancements from bugs, cleanup and clarification, tricky problems, rough ideas etc.
- Sometimes we have enough discussion on related issues to require a shared label, e.g. the date/time, events and opening hours cluster.
- New or improved site features - software work. Mainly python coding, appengine, site navigation (css/js) etc.: all under the site tools and python code label.
- Content fixes - primarily bad examples.: we use the guidelines, docs and examples label. This covers all general and specific documentation beyond the actual term definitions.
- Workflow and documentation for Extensions - the extension model, and/or specific extension areas: all filed under extension tracking
- There are also various workflow-related issues e.g. needs review for topics where community discussion is particularly invited; for steering group attention for areas where careful oversight is most needed; standards and organizations linking schema.org to related efforts elsewhere; implementing, which is used when an issue is decided but not fully implemented.
Historical Meeting agenda and notes
- #587 2015-05-28
- #588 2015-06-11
- (July/August email only)
- #775 2015-09-03
- In Nov 2015 we agreed to stop our regular audio calls and operate in public email/github primarily.
Steering Group background
Elaborating on http://schema.org/docs/about.html -
The day to day operations of Schema.org, including decisions regarding the schema, are handled by a steering group, which includes representatives of the sponsor companies and a small number of individuals who have contributed substantially to Schema.org and related standards. The steering group typically makes decisions by consensus. All members of the steering group have the same standing. The steering group is currently chaired by R.V.Guha, who does not represent his employer in this capacity. Discussions of the steering group are public, see https://groups.google.com/forum/#!forum/schema-org-sg (very rarely used; more often CC:'d threads with the W3C Community Group public list).
Move of fibo extension proposals (PR #1300) in to pending - A candidate for 'in between releases' release.
This issue is being tagged as Stale due to inactivity.