Skip to content

Milestones

List view

  • **Version 0.2.0** will have all the functions from **0.1.0** but with the addition of **hyperparameters optimization** in the strategies. This milestone encompass all tickets required for release.This can be: - QA checks - Package version registration - Communications on features added - Individual tickets that reflect the status of feature developent (maximum of 1 per large feature).

    No due date
    0/2 issues closed
  • This milestone encompass the design of the package, how it is structured and how people should interact with it at all levels of engagement. This includes. - Design of version release steps and communications - Design of unit test criterias - Design of third party tools used in the CICD and displayed in the Readme - Activities regarding support and compatibility of the package with different julia version and the package ecosystem that is likely to interact with. - Determination of best practices for fellow developers contributing to the project **Unless particular circumstances this milestone should not have a due date, is a *Kaizen* milestone** > **[Kaizen](https://www.techtarget.com/searcherp/definition/kaizen-or-continuous-improvement#:~:text=Kaizen%20is%20an%20approach%20to,down%20changes%20to%20achieve%20transformation.)** is an approach to creating continuous improvement based on the idea that small, ongoing positive changes can reap significant improvements.

    No due date
    12/13 issues closed
  • This are complementary features for backtesting. That are a great addition to an already working backtesting feature.

    No due date
    4/4 issues closed
  • This milestone encompass all tickets required solely for release. This can be QA, package registration, etc. It should be started only when the package features are ready for release.

    No due date
    3/6 issues closed
  • Improvements on ETL Pipeline. - Additional Data Sources - Additional Data Formats **Most likely targets for ETL Pipeline V3** It would be great to be able to link our package with the API's of brokers, in order to allow fetching of data and more importantly a seamless transition between the backtesting strategies into their implementation on the broker side. This may also imply the generation of a server running in the background (see Uvicorn, which is a server program that FastAPI uses in python, it can be mounted in a docker container and be let run, this would be a gigantic feat on the capabilities of this software)

    No due date
    7/7 issues closed
  • Deeper and more realistic description for Portfolios, Assets, Accounts, Currencies. In addition add Options, Futures, Positions, Portfolio performance calculations.

    No due date
    8/8 issues closed