@glikely glikely released this Dec 20, 2017 · 11 commits to master since this release

Assets 4
Mostly editorial changes from v0.1. Primary purpose for this release is to work
through the mechanics of cutting a release. Right now it is more labour
intensive than I would like for two reasons:

- The GitHub OAuth key must be manually changed to the person cutting the
  release. I would like it to be automatically selected based on who signed
  the release tag
- The pre-release flag needs to be manually changed between -pre/-rc and full
  releases. This also should be automatically determined based on tag pattern
  matching

Content changes include:
* Added more recommended generic node names
* Added interrupts-extended
* Additional phy times
* Filled out detail in source language chapter
* Editorial changes
* Added changebar version to release documents
Pre-release
Pre-release

@robherring robherring released this Dec 20, 2017 · 12 commits to master since this release

Assets 4
Travis-ci builds are working well, the changebar version seems to be
correct. Getting close to release state, so do the first (and hopefully
only) -rc.
Pre-release
Pre-release

@robherring robherring released this Dec 18, 2017 · 15 commits to master since this release

Assets 4
Fourth (and hopefully last) prerelease of v0.2
Pre-release

@robherring robherring released this Dec 12, 2017 · 18 commits to master since this release

Assets 3
Minor editorial changes and a repository cleanups. Still need to get
changebar version of PDF building before release.
Pre-release
Pre-release

@robherring robherring released this Dec 7, 2017 · 26 commits to master since this release

Assets 3
Prerelease in preparation for the v0.2 release before end of December 2017

@glikely glikely released this Dec 18, 2017 · 67 commits to master since this release

Assets 3

This is the first version of the specification document, released in May 2016. Tagging the release here so the binary .pdf can be added and the devicetree-specification-released repository can be removed from the github page.

Apr 29, 2016
Very first public release of new spec document. However, this is not …
…a full

release. It is merely a prerelease to solicit feedback and get contributions.
Nobody should use this for implementation.