Release Status » History » Version 8
Ward Vandewege, 02/03/2015 12:44 AM
1 | 1 | Tom Clegg | h1. Release Status |
---|---|---|---|
2 | |||
3 | 7 | Ward Vandewege | Arvados is still in beta, but can be used for day to day production use. If you are interested in helping to *design and improve* Arvados, please [[IRC and Mailing Lists|join us]] on IRC or on the mailing lists. |
4 | 1 | Tom Clegg | |
5 | 7 | Ward Vandewege | All core components have been implemented: |
6 | 1 | Tom Clegg | * REST API server |
7 | * Client-side pipeline manager |
||
8 | * Workbench web application |
||
9 | 4 | Tom Clegg | * Keep server |
10 | 8 | Ward Vandewege | * Crunch job manager |
11 | 1 | Tom Clegg | |
12 | 7 | Ward Vandewege | Some components are still in the process of being implemented. We think it's important to describe them to establish scope. We also hope to attract early feedback. |
13 | 5 | Anonymous | * Lightning |
14 | 1 | Tom Clegg | * Compact genome format |
15 | |||
16 | APIs are in active development. |
||
17 | 7 | Ward Vandewege | * REST API is getting stable but isn't at 1.0 yet |
18 | 4 | Tom Clegg | * Keep client API is stable, but system-facing API (e.g., related to garbage collection) are still in development. |
19 | 7 | Ward Vandewege | * Crunch v1 API (job task environment) is mostly stable |
20 | 1 | Tom Clegg | |
21 | SDKs are in active development. |
||
22 | 4 | Tom Clegg | * Rails SDK (an ActiveRecord-like interface) is not yet packaged separately from the Workbench app. |
23 | * Ruby SDK is stable but lacks a native Keep client. |
||
24 | * Python SDK (based on the Google API client) is stable but should gain an alternative (less verbose) calling syntax and better integration of data APIs with Collections. |
||
25 | 1 | Tom Clegg | * Command line tool should gain an alternative (less verbose, less quoting-intensive) calling syntax. |
26 | |||
27 | 4 | Tom Clegg | Documentation is in active development. |
28 | 1 | Tom Clegg | * Tutorials and examples are continuously improved as APIs improve and stabilize |
29 | * Install docs are terse but functional |
||
30 | 4 | Tom Clegg | * API docs need to be filled in (many models are currently documented only as source code in /services/api/) |
31 | * Admin docs are a placeholder |
||
32 | 7 | Ward Vandewege | |
33 | Last update: February 2015 |