... | @@ -38,7 +38,7 @@ Responsible for the project: |
... | @@ -38,7 +38,7 @@ Responsible for the project: |
|
| 24-05-2016 | This project was started with the aim of providing a common code-base (set of IP cores) to be integrated by all the BTrain applications.[^2] |
|
|
| 24-05-2016 | This project was started with the aim of providing a common code-base (set of IP cores) to be integrated by all the BTrain applications.[^2] |
|
|
| 26-06-2017 | Closing [presentation](/uploads/00f5fe3b752bbff1e7cd8c7292cb648f/BTrain-wrapup.pdf) for work package to prepare v1.0 (closure pending QA approval) |
|
|
| 26-06-2017 | Closing [presentation](/uploads/00f5fe3b752bbff1e7cd8c7292cb648f/BTrain-wrapup.pdf) for work package to prepare v1.0 (closure pending QA approval) |
|
|
| 26-06-2017 |[Release candidate for version v1.0 (v1.0-rc)](v1.0-rc) - it is deprecated |
|
|
| 26-06-2017 |[Release candidate for version v1.0 (v1.0-rc)](v1.0-rc) - it is deprecated |
|
|
| 18-09-2017 | v1.0 validated by long-term tests, [see a dedicated page](v1.0-long-term-tests)|
|
|
| 18-09-2017 | v1.0 validated with [long-term tests](v1.0-long-term-tests)|
|
|
| 2017-09-19 | v1.0 (current release)|
|
|
| 2017-09-19 | v1.0 (current release)|
|
|
|
|
|
|
[^2]: This makes easier the maintenance of existing systems and development of new applications. Up to this point, the integration of code commonly used by all the BTrain users had not been formalized.
|
|
[^2]: This makes easier the maintenance of existing systems and development of new applications. Up to this point, the integration of code commonly used by all the BTrain users had not been formalized.
|
... | | ... | |