This is a meta-issue for the upcoming sdo-ganymede release. This is the followup release to sdo-gozer (v2.0). See v2 release notes for details. As of May 15 2015 sdo-ganymede is our default Github branch, and a test release is available

See #1 for general planning overview.

Planning overview

v2 was a large release, and a number of smaller issues (cleanup and vocabulary) were postponed and will need attention. Everything that didn't get done for sdo-gozer milestone is now tagged with sdo-ganymede milestone

The most substantive additional work is to release at least one official hosted Extension. The extension tracking label gives a useful overview. Specifically bib: , auto: are on target for completion during May 2015. We also have a substantive medical/health update that was proposed in 2014, and which seems likely to be reworked as a hosted extension.

Also: @danbri is working on a cleanup to the issue tracker and a "how we work" document, designed to support the new Community Group + Steering Group structure.

Release Date

As usual "we're done when we're done". But roughly it would be good to get back onto an approximately monthly release cycle. We could/should also push out some software-only fixes and minor bugfixes without making a formal release.

Rough candidate: mid-June (~15th)

Other topics

Please use this issue to propose/debate other issues for inclusion or prioritization against this milestone.

In the absence of other factors, issues will be closed and merged as and when we reach something approximating consensus in the relevant issue page.

Possible special topic clusters for this release (or a subsequent one):

• #458 (food, nutrition, recipes)
• Time/date/event, opening hour issues share a common label
  • Add Event Series support #446 Add EventSeries as subclass of Series #447 (event series), Draft for advanced EventTypes #406 (advanced event types); #481 (timezones); applicability of Event to online events e.g. consider Webinar subtype #298 (online events); #242 (uncertain times); Schema.org should say something about repeating events #240 (repeating events)
  • schema.org has two ways to represent openingHours - need unified documentation and cornercase tweak #245 (opening hours dual model) and Meta bug for expressivity and syntax issues around opening/closing hours #186 (missing opening hours expressivity); +1 ClosingDaysSpecification Type #372 (closing days/hours);