Forum | Documentation | Website | Blog

Skip to content
Snippets Groups Projects
Jason Kridner's avatar
Jason Kridner authored
* I believe our next release should be considered 1.0. Only major
  releases should make incompatible URLs and I believe we should be free
  to do that for our next "release". This means we can be free to make a
  0.1 stable release if we want that remains URL compatible. I don't
  know why right now. I just feel we should be working towards 1.0,
  not 0.1 when we already have a release. Please feel free to reject.
* For non-tagged updates, I'm thinking the extra-version should be
  something like "wip" to show that it isn't published to the main
  documents site yet.
* I think we should pull the major/minor/extra from the tag, instead of
  branch, and expect it to be used appropriately.
* I know it isn't the prettiest thing, but having a date for the
  patchlevel is super easy to automate and super easy to understand. I
  trust Robert's experience on this.
* I don't know the real purpose of VERSION_TWEAK, but it will be updated
  in case of more than one commit in a day.
78a5c328

docs.beagleboard.io

Build Status

This project seeks to document the design and usage of BeagleBoard.org boards.

Priority is given to the out-of-box Debian Linux software images, but additional well-maintained software projects supporting these boards are welcome to be documented here as well.

This project seeks to provide a more authoritative and easy to consume set of documentation than is available through wiki pages, but still encourages community contributions. Issues and pull requests will be reviewed for accuracy.

The project will have release versions and archive those specific versions for future reference. The stable release versions will be published at https://docs.beagleboard.org. The latest output is hosted at https://docs.beagleboard.io and source is maintained at https://git.beagleboard.org/docs/docs.beagleboard.io.