Arvados

In addition to the continuous integration/build/release/deploy for bleeding edge uses, it could be useful to have "official" (known working / stable) releases that use semantic versioning (http://semver.org/)

This came up today at the Arvados London User Group meeting today - several people requested it, and mentioned that having a version number to point to would make it easier to make the case for using Arvados to managers (apparently some people just like knowing what version something is).

I'm not sure what the appropriate schedule for versioned releases would be - I could imagine it being as often as every sprint or as infrequently as once or twice a year.