antoinecarme/pyaf

PyAF 5.0 Release Process

antoinecarme opened this issue · 8 comments

Time to put in a place a final path/countdown through the next PyAF release, expected 2023-07-14

A branch 5.0-Fixes is already in place and will contain the final touches. The CI process is OK.

https://github.com/antoinecarme/pyaf/tree/5.0-Fixes

Only user comments and fixes are welcome and accepted.

No additional/new feature. Early adopters feedback welcome until July.

Versioning Notes :

  1. This version is a major version as in https://semver.org/, like other annual versions (usually released on 20xx-07-14 ;).
  2. It introduces a radical change in the model selection processes (Voting, Model Complexity, MAPE -> MASE by default).
  3. It may not be backwards compatible in some places (reverting to the old behavior may need tweaking options).

Original planning :

  1. Forecasting Models based on Deep Learning Attention Mechanisms => Delayed to PyAF > 7.0
  2. Recurrent tasks : More hardware architectures, forecasting performance measures, benchmarks, bug fixes, docs and optimization/profiling. OK.
  3. User feedback and issues Ok.

Created a new release candidate 5.0-rc1.

Will become an official 5.0 on 2023-07-14 if no change until then.

Can be installed with

pip install --upgrade git+https://github.com/antoinecarme/pyaf.git@5.0-Fixes

Implemented/Processed So far (for changelog):

  1. Python 3.11 Support : #227
  2. New Hardware Support : #208
  3. New Performance Measures : #209, #221
  4. Model Selection Improvement : #212, #213 , #223, #229
  5. Signal Transformation Improvements : #235, #239
  6. Generic Modeling : #230, #231, #236, #238
  7. Plotting Functions Improvements and Bug Fixes : #216, #225, #232
  8. New Docs : #233
  9. Bug Fixes : #220
  10. PyAF "Forecast Tasks" : #211, #217
  11. Recurrent Tasks : #222, #224, #234, #237

Switched to Github Actions CI/CD. Farewell CircleCI !!!

The switch was smooth.

https://github.com/antoinecarme/pyaf/actions/runs/5501701813/jobs/10025475124

DONE.